Table Of Contents
Release Notes for Catalyst 2360 Switch, Cisco IOS Release 12.2(58)SE1 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
Caveats Resolved in Cisco IOS Release 12.2(58)SE2
Caveats Resolved in Cisco IOS Release 12.2(58)SE1
Updates to the Software Configuration Guide
Updates to the System Message Guide
Obtaining Documentation and Submitting a Service Request
Release Notes for Catalyst 2360 Switch, Cisco IOS Release 12.2(58)SE1 and Later
Revised July 27, 2011
Note
Cisco IOS Release 12.2(58)SE images for all platforms were removed from Cisco.com because of a severe defect, CSCto62631. The solution for the defect is in Cisco IOS Release 12.2(58)SE1.
Cisco IOS Release 12.2(58)SE1 runs on all Catalyst 2360 switches.
These release notes include important information about Cisco IOS Release 12.2(58)SE1 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
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.
Contents
•
•
•
•
•
•
•
•
System Requirements
•
•
Supported Hardware
Table 1 Supported Hardware
Catalyst 2360-48TD-S
48 10/100/1000 ports and four 10-Gigabit SFP+1 module slots.
Cisco IOS Release 12.2(53)EY
Dual FRU Power Supplies
Cisco IOS Release 12.2(53)EY
SFP Modules
GE SFP, LC connector LX/LH transceiver
GE SFP, LC connector SX transceiverCisco IOS Release 12.2(53)EY
SFP+ Modules
GBASE-LR SFP+ Module
10GBASE-SR SFP+ Module
10GBASE-LRM SFP+Module
10GBASE-LRM SFP+ Module for single mode
10GBASE-CX1 SFP+ ModuleCisco IOS Release 12.2(53)EY
C2360-PWR-135WAC
135-W AC-power-supply module
Cisco IOS Release 12.2(53)EY
C2360-FAN
60 CFM Fan Module
Cisco IOS Release 12.2(53)EY
1 SFP+ = 10 Gigabit fiber uplink.
Device Manager System Requirements
Hardware
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software
•
•
The device manager verifies the browser version when starting a session does not require a plug-in.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. Use the command-line interface (CLI).
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Support
Cisco Network Assistant 5.4 and earlier does not provide specific device support for the Catalyst 2360 switch. For more information about Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
•
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Table 3 Cisco IOS Software Image Files
c2360-universalk9-tar.122-58.se1.tar
Catalyst 2360 image file and device manager files. This image has both Layer 2 and SSH features.
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current
Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/prod_command_reference_list.html
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an new image file and replace or keep the current image.
Step 1
Step 2
http://www.cisco.com/cisco/web/download/index.html
a.
b.
c.
d.
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and a default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c2360-univeresalk9-tarThis example shows how to download an image from a TFTP server and keep the current image by replacing the /overwrite option with the /leave-old-sw option:
Switch# archive download-sw /leave-old-sw tftp://198.30.20.19/c2360-univeresalk9-tar
Recovering from a Software Failure
For recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
New Software Features
There are no new features in this release.
Configuration Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
Cisco IOS Limitations
None.
Important Notes
These sections describe the important notes related to this software release for the Catalyst 2360 switches:
•
Cisco IOS Notes
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.
Device Manager Notes
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
•
Open Caveats
•
When you make port security changes on an interface, such as configuring aging time, violations, or aging type, error messages and tracebacks might appear.
There is no workaround.
•
When a switch 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.
There is no workaround.
•
Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.
The workaround is to disable IPv6 MLD snooping on the switch.
Resolved Caveats
•
•
Caveats Resolved in Cisco IOS Release 12.2(58)SE2
•
When you configure a port to be in a dynamic VLAN by entering the switchport access vlan dynamic interface configuration command on it, the switch might reload when it processes ARP requests on the port.
The workaround is to configure static VLANs for these ports.
Caveats Resolved in Cisco IOS Release 12.2(58)SE1
•
When ports in an EtherChannel are linking up, the message EC-5-CANNOT_BUNDLE2 might appear. This condition is often self-correcting, indicated by the appearance of EC-5-COMPATIBLE message following the first message. On occasion, the issue does not self-correct, and the ports may remain unbundled.
The workaround is to reload the switch or to restore the EtherChannel bundle by shutting down and then enabling the member ports and the EtherChannel in this order:
–
–
–
–
•
Dynamic ARP inspection CLI is not functional.
No workaround.
•
Shaped Round Robin (SRR) commands are unavailable on the interface.
No workaround.
•
The config.text.backup file is present after the switch is restored to the factory defaults.
There is no workaround.
•
When you enter the ipv6 traffic-filter interface configuration command, it might not filter traffic as expected, and it might allow traffic to pass through.
There is no workaround.
•
When you disconnect the spanning tree protocol (STP) peer link, the STP port path cost configuration changes.
There is no workaround.
•
When a spanning-tree bridge protocol data unit (BPDU) is received on an 802.1Q trunk port and has a VLAN ID is greater than or equal to 4095, the spanning-tree lookup process fails.
There is no workaround.
•
When you enter the default interface, switchport, or no switchport interface configuration command on the switch, this message appears: EMAC phy access error, port 0, retrying......
There is no workaround.
•
The CPU usage on a standalone switch varies as the switch updates the running configuration.
There is no workaround.
•
When 802.1x MAC authentication bypass with multidomain authentication and critical VLAN are enabled on an interface on a switch running Cisco IOS Release 12.2(53)SE or later, if the switch loses connectivity with the AAA server, the switch might experience high CPU usage and show these messages:
AUTH-EVENT (Gi0/15) Received clear security violationAUTH-EVENT (Gi0/15) dot1x_is_mab_interested_in_mac: Still waiting for a MAC on port GigabitEthernet0/15There is no workaround.
•
A switch running Cisco IOS Release 12.2(58)SE might reload if:
–
–
Use one of these workarounds:
–
–
–
Documentation Updates
Updates to the Software Configuration Guide
The "Supported MIBs" appendix is no longer in the software configuration guide. To locate and download MIBs for a specific Cisco product and release, use the Cisco MIB Locator:
http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.Updates to the System Message Guide
New System Messages
Error Message IP-3-SBINIT: Error initializing [chars] subblock data structure. [chars]Explanation The subblock data structure was not initialized. [chars] is the structure identifier.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ARP: vlan [dec] (port [chars]) denied arp ip [inet] -> [inet], [dec] packet[chars]Explanation A packet from the virtual LAN (VLAN) that matches the VLAN access-map (VLMAP) log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-L4: vlan [dec] (port [chars]) denied [chars] [inet]([dec]) -> [inet]([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [chars] is the protocol, the first [inet] is the source IP address, the second [dec] is the source port, the second [inet] is the destination IP address, the third [dec] is the destination port, the fourth [dec] denotes the number of packets, and the third [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IGMP: vlan [dec] (port [chars]) denied igmp [inet] -> [inet] ([dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Group Management Protocol (IGMP) message type, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-ICMP: vlan [dec] (port [chars]) denied icmp [inet] -> [inet] ([dec]/[dec]), [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Control Message Protocol (ICMP) message type, the third [dec] is the ICMP message code, the fourth [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message VLMAPLOG-6-IP: vlan [dec] (port [chars]) denied ip protocol=[dec] [inet] -> [inet], [dec] packet[chars]Explanation A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [dec] is the protocol number, the first [inet] is the source IP address, the second [inet] is the destination IP address, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.
Recommended Action No action is required.
Error Message HARDWARE-2-PSU_THERMAL_WARNING: PSU [chars] temperature has reached warning thresholdExplanation The switch power supply unit (PSU) temperature sensor value has reached the warning level. The external temperature is high. [chars] is the power supply.
Recommended Action Reduce the temperature in the room. (The switch functions normally until the temperature reaches the critical level.)
Error Message HARDWARE-1-PSU_THERMAL_CRITICAL: PSU [chars] temperature has reached critical thresholdExplanation The switch PSU temperature sensor value has reached the critical level, and the switch cannot function normally. The external temperature is very high. [chars] is the power supply.
Recommended Action Immediately reduce the room temperature.
Error Message HARDWARE-5-PSU_THERMAL_NORMAL: PSU [chars] Temperature is within the acceptable limitExplanation The switch PSU temperature sensor value is within normal limits. [chars] is the power supply.
Recommended Action No action is required.
Error Message HARDWARE-2-THERMAL_WARNING: Temperature has reached warning thresholdExplanation The switch temperature sensor value has reached the warning level. The external temperature is high.
Recommended Action Reduce the room temperature. (The switch functions normally until the temperature reaches the critical level.)
Error Message AUTHMGR-7-STOPPING: Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars]Explanation The authentication process has been stopped. The first [chars] is the authentication method, [enet] is the Ethernet address of the host, the second [chars] is the interface for the host, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation All available authentication methods have been tried. The first [chars] is the client identifier, the second [chars]s is the interface for the client, and the third [chars] is the session ID.
Recommended Action No action is required.
Related Documentation
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
These documents provide complete information about the Catalyst 2360 switch and are available on Cisco.com:
http://www.cisco.com/en/US/products/ps10920/tsd_products_support_series_home.html
•
•
•
•
•
•
•
•
For more information about the Network Admission Control (NAC) features, see the Network Admission Control Software Configuration Guide.
•
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
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.
