Release Notes for Catalyst 3750-X and 3560-X Switches, Cisco IOS Release 12.2(53)SE2
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
Cisco Transceiver Modules and SFP Modules
Stacking (only Catalyst 3750-X Switch Stack)
Stack Power (Catalyst 3750-X only)
Obtaining Documentation and Submitting a Service Request
Cisco IOS Release 12.2(53)SE2 runs on Catalyst 3750-X and Catalyst 3560-X switches.
The Catalyst 3750-X switches support stacking through Cisco StackWise Plus technology and StackPower. The Catalyst 3560-X switches 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 12.2(53)SE2 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
For the complete list of Catalyst 3750-X and Catalyst 3560-X switch documentation, see the “Related Documentation” section.
This information is in the release notes:
The system requirements are described in these sections:
These model numbers are referenced in the documentation but are not available:
24 10/100/1000 Ethernet ports, StackWise Plus, 1 network module1 slot, 350 W power supply; LAN Base feature set |
|
48 10/100/1000 Ethernet ports, StackWise Plus, one network module1 slot, 350 W power supply; LAN Base feature set |
|
24 10/100/1000 PoE+ 1 slot, 715 W power supply; LAN Base feature set |
|
48 10/100/1000 PoE+ 2 ports, StackWise Plus, one network module1 slot, 715 W power supply; LAN Base feature set |
|
48 10/100/1000 PoE+ 2 ports, StackWise Plus, 1 network module1 slot, 1100 W power supply; LAN Base feature set |
|
24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module 1 slot, 350 W power supply; IP Base feature set3 |
|
48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module 1 slot, 350 W power supply; IP Base feature set3 |
|
24 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module 1 slot, 715 W power supply; IP Base feature set3 |
|
48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module 1 slot, 715 W power supply; IP Base feature set3 |
|
48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module 1 slot, 1100 W power supply; IP Base feature set3 |
|
24 10/100/1000 Ethernet ports, 1 network module 1 slot, 350 W power supply; LAN Base feature set |
|
48 10/100/1000 Ethernet ports, 1 network module1 slot, 350 W power supply; LAN Base feature set |
|
24 10/100/1000 PoE+2 ports, 1 network module 1 slot, 715 W power supply; LAN Base feature set |
|
48 10/100/1000 PoE+2 ports, 1 network module1 slot, 715 W power supply; LAN Base feature set |
|
48 10/100/1000 PoE+2 ports, 1 network module 1 slot, 1100 W power supply; LAN Base feature set |
|
24 10/100/1000 Ethernet ports, 1 network module 1 slot, 350 W power supply; IP Base feature set3 |
|
48 10/100/1000 Ethernet ports, 1 network module 1 slot, 350 W power supply; IP Base feature set3 |
|
24 10/100/1000 PoE+2 ports, 1 network module 1 slot, 715 W power supply; IP Base feature set3 |
|
48 10/100/1000 PoE+2 ports, 1 network module 1 slot, 715 W power supply; IP Base feature set3 |
|
48 10/100/1000 PoE+2 ports, 1 network module 1 slot, 1100 W power supply; IP Base feature set3 |
|
100FX-SFP 1000BASE-LX/LH Note For a complete list of supported SFP modules, see the hardware installation guide or the data sheets at: http://www.cisco.com/en/US/products/ps10745/products_data_sheets_list.html |
|
SFP-10G-SR |
|
Only version 02 (or later) of the CX16 cables are supported: |
|
SFP module patch cable7 |
|
C3KX-PWR-1100WAC Note For power supply module descriptions and configurations supported on switch models, see the hardware installation guide. |
1.Available network modules: 10-Gigabit Ethernet network module; 1-Gigabit Ethernet network module; blank module |
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(53)SE2 will be supported in a future release of the Cisco Network Assistant. 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.
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.
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. 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. 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
Switches running payload-encryption images can encrypt management and data traffic. Switches running nonpayload-encryption images can encrypt only management traffic, such as a SSH management session.
For more information about software licenses and images available for the Catalyst 3750-X and Catalyst 3560-X switches, see the Cisco IOS Software Installation Document on the Catalyst 3750-X or Catalyst 3560-X documentation page on Cisco.com.
Layer 2 and basic Layer 3 features, SSH10, SSL11, and SNMPv312, and Kerberos |
||
Layer 2 and basic Layer 3 features, SSH, SSL, SNMPv3, Kerberos, and MACsec13 |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 |
||
All the supported universal image features, Kerberos, SSH, SSL, SNMPv3, and MACsec |
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/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-X switch, click Catalyst 3750-X software.
To download the universal software image files for a Catalyst 3560-X switch, click Catalyst 3560-X 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.
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-X and 3560-X switches.
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)
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))
– 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)
There is no workaround. (CSCec74610) (Catalyst 3750-X 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-X switches)
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)
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)
– 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)
There is no workaround. This is a hardware limitation. (CSCei10129)
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)
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 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)
These sections describe the important notes related to this software release for the Catalyst 3750-X and 3560-X switches:
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 both the Catalyst 3750-X and 3560-X switches:
When a switch stack is running 802.1x single host mode authentication and has filter-ID or per-user policy maps applied to an interface, these policies are removed if a master switchover occurs. Even though the output from the show ip access-list privileged EXEC command includes these ACLs, the policies are not applied.
The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface.
On a 48-port PoE switch with many ports connected to PoE devices, most of which are Cisco + IEEE powered devices, when you apply an Auto Smartport (ASP) global macro to the switch and enter the interface range gigabitethernet 1-48 interface command followed by the shutdown and no shutdown interface commands, the switch remains in a retry loop and fails to bring up all of the PoE devices. The high CPU usage caused by frequently applying and removing ASP macros causes some of the PoE timers to expire during the retry cycle, creating a convergence problem.
– Reduce the number of Cisco + IEEE powered devices in the system.
– Do not use Auto Smartport global macro processing when the system has a significant number of Cisco + IEEE powered devices.
– Do not use the interface range interface configuration command with the shutdown and no shutdown interface commands for all 48 ports at the same time when all ports are connected to PoE devices and ASP global macro configuration is applied. Use the interface range command in stages with fewer ports in each range.
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.
When you remove a switch from a power stack, another switch in the stack might incorrectly report a power stack error. For example, in a stack of four switches, where switches 1 to 3 each have two power supplies and switch 4 has a single power supply, if you remove switch 4 from the power stack, switch 1 might incorrectly report an unbalanced power stack error.
The workaround is to toggle the stack power ports (off and on) on the switch that is reporting the error by entering these commands:
On a Catalyst 3750-X or 3560-X switch running the LAN base feature set, the Auto Smartports macro commands are accepted, but do not work or have any effect.
The workaround is to upgrade to the IP base or IP services feature set if you want to use Auto Smartports.
Documents with complete information about the switch are available from these Cisco.com sites:
http://www.cisco.com/en/US/products/ps10745/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps10744/tsd_products_support_series_home.html
These documents provide complete information about the switches:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html
SFP compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list
.html
For other information about related products, see these documents:
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.