Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(44)EX and Later
Available Languages
Table Of Contents
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(44)EX 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
Updates to the Cisco IE 3000 Switch Getting Started Guide
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco IE 3000 Switch, Cisco IOS Release 12.2(44)EX and Later
Revised July 31, 2008
Cisco IOS Release 12.2(44)EX and later runs on all Cisco IE 3000 switches.
These release notes include important information about Cisco IOS Release 12.2(44)EX and later, and any limitations, restrictions, and caveats that apply to the releases. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
For the complete list of Cisco IE 3000 switch documentation, see the "Related Documentation" section.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
This software release is part of a special release of Cisco IOS software that is not released on the same 8-week 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
This information is in the release notes:
•
•
System Requirements
The system requirements are described in these sections:
•
Hardware Supported
This section lists the hardware and SFP modules that the switch supports.
Switches and Modules
Table 1 lists the hardware supported on this release.
.
SFP Modules
These are the SFP modules that the switch supports:
.
Device Manager System Requirements
These sections describes the hardware and software requirements for using the device manager:
Hardware Requirements
Table 3 lists the minimum hardware requirements for running the device manager.
Table 3 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software Requirements
Table 4 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS 12.2(44)EX and later is only compatible with Cisco Network Assistant (CNA) 5.4 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.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the compact flash memory card.
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 5 lists the filenames for this software release.
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 to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:
Upgrading a Switch by Using the Device Manager or Network Assistant
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note
Upgrading a Switch by Using the CLI
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
Note
To download software, follow these steps:
Step 1
Step 2
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
To download the image for a Cisco IE 3000 switch, click Cisco IE 3000 software. To obtain authorization and to download the cryptographic software files, click Cisco IE 3000 3DES Cryptographic Software.
Step 3
For more information, see the Cisco IE 3000 Switch Software Configuration Guide.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/ies-lanbase-tar.122-44.EX.tarYou can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Recovering from a Software Failure
For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
•
New Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
New Hardware Features
For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
This release is the first software release for the Cisco IE 3000 switches. For a detailed list of key features for this software release, see the Cisco IE 3000 Switch Software Configuration Guide.
Limitations and Restrictions
You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
This section contains these limitations:
Cisco IOS Limitations
These limitations apply to the Cisco IE 3000 switches:
•
•
•
Configuration
These are the configuration limitations:
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
Use one of these workarounds:
–
–
–
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
Ethernet
These is the Ethernet limitation:
Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC.
If this happens, uneven traffic distribution will happen on EtherChannel ports.
Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:
•
•
•
•
For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)
IP
This is the IP limitation:
When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console. The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)
Multicasting
These are the multicasting limitations:
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)
After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.
Use one of these workarounds:
–
–
•
The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)
QoS
These are the quality of service (QoS) limitations:
•
•
SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
Trunking
These are the trunking limitations:
•
•
•
VLAN
These are the VLAN limitations:
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
Device Manager Limitations
This is the device manager limitation:
When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
This section describe the important notes related to this software release for the Cisco IE 3000 switches.
Device Manager Notes
These notes apply to the device manager:
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
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.
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:
Open Caveats
This section describes the open caveats in this software release:
•
The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.
Examples:
Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9
Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4
Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315: .Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9
Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912CThere is no workaround.
•
When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, some interface level configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, become unavailable.
The workaround is to enable the dot1x system-auth-control global configuration command before attempting to configure interface level IEEE 802.1x parameters.
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
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.
•
The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.
These are the workarounds. (You only need to do one of these.)
–
–
•
A switch configured for Link Layer Discovery Protocol (LLDP) might not correctly report the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes. System capabilities appear correctly, but the enabled capabilities are not identified if the switch is configured only as a Layer 2 switch.
There is no workaround.
•
When you successfully upgrade an image by using device manager and click No when prompted to reload the image, device manager becomes unusable.
The workaround is to manually reload the switch.
•
When an unsuccessful forward open request message is returned on the switch, the response does not contain the connection serial number, vendor ID, or vendor serial number information. Only the general and extended error codes are returned.
This problem only applies to unsuccessful forward open response messages.
The workaround is to enable the CIP debug command to determine the cause of the forward open failure.
•
When a 100FX-FE SFP module is connected to the switch, and you change the media-type from SFP to copper, the copper link does not come up. This problem only occurs when two IE3000 switches are connected with both copper and fiber connections on the same port.
These are the workarounds:
–
–
•
When configuring a switch management VLAN to be another VLAN during Express Setup, the PC loses the network connection to the switch if it remains connected to the same port.
These are the workarounds:
–
–
•
When a diagnostic or port mirroring role is defined on an interface and you change it to another port role, the port role icon in device manager shows as Unknown.
The workaround is to configure the port role on the interface to none before you configure the other port roles.
•
If you remove the secure MAC address from an interface through CIP (Common Industrial Protocol), the switchport port-security violation restrict CLI configuration remains on the interface.
The workaround is to use the CLI to remove any settings remaining on the port.
•
The show cip object tcp/ip interface privileged EXEC command displays an old value for the domain name after it has been unconfigured with the no ip domain-name global configuration command.
The workaround is to ignore the domain name output of the show cip object tcp/ip interface privileged EXEC command.
Resolved Caveats
These are the caveats resolved in Cisco IOS Release 12.2(44)EX1:
•
When you disable switch ports over CIP through the output assembly, the switch no longer fails to disable switch ports.
•
This version of the software contains the latest version of the EDS (Electronic Data Sheet) files.
•
The redundant power status in the CIP switch parameter is now consistent with the output from the show facility-alarm status user EXEC command.
•
During the ODVA (Open DeviceNet Vendors Association) encapsulation test, the switch no longer fails at the maximum-size NOP packet test. The switch no longer replies to the UnRegister session message.
The ODVA File object test no longer fails when the file size is a multiple of the transfer buffer size. After loading the EDS file, the EDS file now correctly changes to the FileLoaded state.
•
The switch no longer returns a success response for a request to set an invalid interface configuration attribute value at the CIP TCP/IP interface object.
•
The autonegotiation status is now set in the CIP InterfaceFlag attribute of the Ethernet link object.
•
The CIP get and set services no longer return invalid data or cause the switch to fail for invalid Ethernet link instances. Instead, the invalid destination error is returned.
The CIP response that is returned after you set the file type attribute is now formatted correctly.
When you use the CIP set service on read-only attributes, you now receive an error response. When you set read-only attributes of the vlan and config file instances you now receive correct error code.
When a CIP file download transfer is aborted, the file object now returns to the fileEmpty state.
•
The CIP Ethernet link object no longer returns a blank MAC address for the physical address attribute of instance 27. Instance 27 is the switch virtual interface over which CIP traffic passes.
Documentation Updates
These sections provide updates to the product documentation:
•
Updates to the Cisco IE 3000 Switch Getting Started Guide
These corrections were made to the English version of the Cisco IE 3000 Switch Getting Started Guide on Cisco.com.
Warning Statment 1067
This warning statement has been removed from the Cisco IE 3000 Switch Getting Started Guide on Cisco.com.
Grounding the Switch
Step 6: Use a ratcheting torque screwdriver to tighten the ground screw and ring terminal lug to the switch front panel to 8.5 in-lb, the maximum recommended torque.
Wiring the DC Power Source
Step 6: Use a ratcheting torque flathead screwdriver to torque the power and relay connector captive screws (above the installed wire leads) to 2 in-lb, the maximum recommended torque.
Resetting the Switch
Follow these steps to return your switch to the factory default settings. These are reasons why you might want to reset the switch:
•
•
•
Caution
To reset the password on the switch:
1.
2.
3.
After the switch restarts, continue to run Express Setup.
Documentation Updates to the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch
This information in the "Regulatory Standards Compliance' section has been revised in the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch on Cisco.com.
Warning Statment 1067
Warning statement 1067 has been removed from the Regulatory Compliance and Safety Information for the Cisco IE 3000 Switch on Cisco.com.
Compliance Label
The compliance labels for the switch are shown in Figure 1 and Figure 2.
Figure 1 Compliance Label for the Cisco IE 3000 Switch
Figure 2 Compliance Label for the Cisco IE 3000 Switch Extension Module
Related Documentation
These documents provide complete information about the Cisco IE 3000 switches and are available at Cisco.com:
http://www.cisco.com/en/US/products/ps9703/tsd_products_support_series_home.html
•
•
•
•
•
For other information about related products, see these documents:
•
•
•
These SFP module installation notes are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html
•
•
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
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.CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)