Readme updated 03 January 2006 **************************************************************** | | | Cisco IOS Release 12.1(22)EA6a | | Build ID: cigesm-i6q4l2-tar.121-22.EA6a.tar normal | | cigesm-i6k2l2q4-tar.121-22.EA6a.tar crypto | | Revision: EA6 | | | | (C) Copyright International Business Machines Corporation | | May, 2004. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated 03 January 2006 | **************************************************************** CONTENTS 1.0 About this readme file 2.0 Change history 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web sites and phone support 6.1 Web sites 6.2 Software service and support 6.3 Hardware service and support 7.0 Notices and trademarks 8.0 Disclaimer 1.0 ABOUT THIS README FILE -------------------------- This release contains software for both the Cisco Intelligent Gigabit Ethernet Switch Module (CIGESM) and the Cisco Intelligent Fiber Gigabit Ethernet Switch Module. Both normal and cryptographic versions are included in this release. Also included in this release are the Maintenance Information Base (MIB) files for the CIGESM. There have been no changes to the MIBs since the release of Cisco software Version 12.1(14)AY4. They are included on this web site for completeness. 2.0 CHANGE HISTORY ------------------ 03 January 2006 Version 12.1(22)EA6a - cigesm-i6q4l2-tar.121-22.EA6a.tar This release resolves the firmware revision contents displayed by the management module. The management module incorrectly displays the version number of version 12.1(22)AY instead of the correct version of 12.1(22)EA6. This new level of firmware corrects this problem. This release resolves the following DDTS issues: CSCsc73761 Description of resolved issues: CSCsc73761 If the CIGEMS has more than one VLAN interface defined, then one of the physical interfaces could be placed into the shutdown state. This problem occurs when the switch is in VTP client or VTP server mode and when the management interface has been changed to a VLAN ID other than the default VLAN ID = 1. If a reboot is done the physical interface matching the managemenet VLAN ID is placed in the shutdown state. For example, it the management VLAN ID = 7, when a reboot is done, the internal physical port 7 goes into the shutdown state and traffic stops. 03 November 2005 Version 12.1(22)EA6 - cigesm-i6q4l2-tar.121-22.EA6.tar This version of the software includes the updates based on the normally scheduled maintenance release for the entire line of Cisco switch products. Enhancements to the BladeCenter Cisco Intelligent Gigabit Ethernet Switch Module are: 1. Default VLAN of 4095 for Serial over LAN (SOL) traffic 2. Multiple management VLANs 3. IEEE 802.1x with wake on LAN This release also resolves the following DDTS issues: CSCei76358 CSCeg15130 CSCeg53741 CSCeg52581 CSCeg57925 CSCeg05952 CSCeg09791 CSCeg12120 CSCeh28757 CSCeh58797 CSCeh77474 CSCei13927 CSCei77627 CSCei22387 CSCsb79318 Description of resolved issues: CSCei76358 Through normal software maintenance processes, Cisco is removing deprecated functionality from the OS boot routine. These changes have no impact on system operation or feature availability. CSCeg15130 If multiple switches are configured in a multicast television application with Multicast VLAN Registration (MVR) is enabled and MVR ports statically configured, IGMP leave messages are no longer sent to the router, and the multicast stream to the set-top boxes is not disrupted. CSCeg53741 If frame sizes larger than 1518 bytes are received and the system MTU is configured as 1530 bytes, the counters no longer display the packets as giants. CSCeg52581 If you start a session on a switch cluster member by using the rcommand user EXEC command, the allowable commands that you enter in the rcommand session now depend on the respective authorization status. CSCeg57925 The switch no longer stops if a port that is assigned to the management VLAN does not have a corresponding access VLAN. CSCeg58877 If a switch uses rapid per-VLAN spanning tree plus (rapid PVST+), a loop no longer occurs when you reconfigure the allowed VLANs on a trunk and remove VLAN 1 from the trunk. CSCeg05952 When the destination-MAC address for data packets is statically configured in a logical EtherChannel port group, the egress traffic on the EtherChannel group no longer uses the default port instead of following the configured load-balancing scheme. CSCeg09791 When you configure an interface for trust CoS and CoS-to-DSCP mapping, the DSCP values of the untagged IP packets received on the interface are now modified as expected. CSCeg12120 When packets matching the permitted UDP fields are attached on an ingress interface, Layer 4 ACLs no longer fail, and Ethernet packets matching the UDP fields are not dropped. CSCeh28757 CiscoView can now distinguish between the switch deployed in the BladeCenter and the BladeCenter T-type chassis. CSCeh58797 If you connect a router FE port to the external port of the switch and set the router FE port to fixed 100 M and half-duplex, the switch negotiates a link to auto-100 M and auto-half duplex. CSCeh77474 On the external Ethernet interfaces of the switch (Gi0/17 - Gi0/20), the LED no longer remains on when the switch has put the Ethernet interface in a shutdown state. CSCei13927 When the management VLAN for the switch is greater than 255, IP communication is nolonger lost. This only effects the IP communication to the switch, not the Ethernet data being switched from data port to data port. This will occur when the VLAN ID of the management VLAN is changed from some number less than 256 to a number greater than 255. CSCei77627 Server Blades no longer fail to detect an Ethernet link-down event from the switch. This was on the internal Ethernet interfaces (Gi0/1 to Gi0/14). When the switch brings down the Ethernet interface to the Server Blade, the Server Blade can adequately detect this, and keeps the link as Ethernet link-up. CSCei22387 CDP and VTP protocols no longer fail when trunk ports are not members of VLAN 1. CSCsb79318 if the re-authentication timer and re-authentication action is downloaded from the RADIUS server using the Session-Timeout and Termination-Action RADIUS attributes, the switch performs the termination action even when the port is not configured with the dot1x timeout reauth server global configuration command and uses the Termination-Action downloaded from a RADIUS server as part of IEEE 802.1x authorization. 3 April 2005 Version 12.1(22)AY1 - Build ID cigesm-i6q4l2-tar.121-22.AY1.tar This is the GA-version for the Cisco Intelligent Fiber Ethernet Switch Module. It is also an update to the CIGESM software. This version of the software includes the updates based on the normally scheduled maintenance release for the entire line of Cisco switch products. Enhancements to the BladeCenter Cisco Intelligent Gigabit Ethernet Switch Module are: 1. Jumbo frame support for Ethernet frames up to 9162 bytes 2. Ability to force link on the from the Cisco Switch Module to the internal blades as specified in the Retain tip H183647 3. Common image for both the CIGESM and the Cisco Intelligent Fiber Gigabit Ethernet Switch Module. The following Cisco DDTS problems were corrected by this release: CSCeh10012 Multicast flooding within VLAN when no receiver joins Two or more physical port can be combined together to form one EtherChannel. The EtherChannel is treated as one logical port with multiple physical ports to increase bandwidth and provide redundancy. For multicast traffic to the logical EtherChannel port, only one port should transmit the traffic. However, the same multicast traffic is flooded on all the ports, and the other side ends up with multiple copies of the same packet. CSCeh34702 Stop u-multicast packet going to the CPU when no mrouter configured IGMP snooping prevents unnecessary broadcast of multicast traffic if the switch detects (or statically told) the location of a multicast driver in the network. If a multicast router is present, any multicast data stream coming to the switch, switch learns the multicast mac address, and configures a hardware port table so that the packet goes to appropriate port connected to the mrouter. The packet floods for a short time taken for snooping program to learn and program the multicast mac address. Once learned the flooding should stop until this entry aged out. However, the multicase packet flooding never stopped. 3 January 2005 Version 12.1(14)AY4 - Build ID cigesm-i6q4l2-tar.121-14.AY4.tar No DDTS problems have been corrected in this release. This version adds the following features to the Cisco IOS software: 1. Link state tracking to mirror the state of the external ports on the internal BaldeCenter Ethernet links. This allows the Cisco switch to bring down internal link groups if all the external links in the group are inoperative. With the appropriate NIC driver software on the processor blade, the processor blade traffic fails-over to an operational external link on a separate Cisco Ethernet switch. 2. Source IP/Destination IP (SIP/DIP) address routing balances traffic loads across links in an EtherChannel connection based on either the source IP address, destination IP address, or both IP addresses. This mode of operation applies to all EtherChannels configured on the Cisco Ethernet switch. 3. Includes feature for re-establishment of configured default gateway by issuing an icmp ping packet when a chassis Management Module switchover is detected. 17 November 2004 Version 12.1(14)AY3 - Build ID cigesm-i6q4l2-tar.121-14.AY3.tar This version corrects the following Cisco software problems from those noted in the June version of the Cisco Release Notes Version AY1. No additional features are included with this release. The Release Notes will not be updated for this version of software. CSCef46191 CSCin67568 CSCdz32659 CSCed40563 CSCec25430 CSCef85910  CSCeg16833   Problem descriptions CSCef46191   A specifically crafted Transmission Control Protocol (TCP) connection to a telnet or reverse telnet port of a Cisco device running Internetwork Operating System (IOS) may block further telnet, reverse telnet, Remote Shell (RSH), Secure Shell (SSH), and in some cases Hypertext Transport Protocol (HTTP) access to the Cisco device. Telnet, reverse telnet, RSH and SSH sessions established prior to exploitation are not affected. All other device services will operate normally. Services such as packet forwarding, routing protocols and all other communication to and through the device are not affected. CSCin67568   Symptoms: A Cisco device experiences a memory leak in the CDP process. Conditions: The device sending CDP packets sends a hostname that is 256 or more characters. There are no problems with a hostname of 255 or fewer characters. CSCdz32659   Symptoms: Many memory allocation failure (MALLOCFAIL) messages may occur for a Cisco Discovery Protocol (CDP) process: %SYS-2-MALLOCFAIL: Memory allocation of -1732547824 bytes failed from x605111F0, pool Processor, alignment 0 -Process= "CDP Protocol", ipl= 0, pid= 42 -Traceback= 602D5DF4 602D78A0 605111F8 60511078 6050EC88 6050E684 602D0E2C 602D0E18 CSCed40563   Symptoms: Depending upon configuration, issuing The show cdp entry * protocol command may cause a reload of the device. Conditions: This symptom occurs on Cisco products that are speaking CDP with configurable interface MTU. CSCec25430   Symptoms: A Cisco device reloads on receipt of a corrupt CDP packet. One possible scenario is: Reloading a faulty Cisco IP conference station 7935 or 7936 may cause a connected Cisco switch or router to reload. A CDP message may appear on the terminal, such as the following one: %CDP-4-DUPLEX_MISMATCH duplex mismatch discovered on FastEthernet5/1 (not half duplex), with SEP00e0752447b2 port 1 (half duplex). CSCef85910 Symptoms: Originally all external ports default to VLAN 1 in access mode unless they are connected to an external Cisco switch which implements the Cisco proprietary trunking protocol. The configuration allowed the user the ease of managing and configuring the CIGESM "on-site" with an external laptop. However, if the ports are connected to an external Cisco switch, the ports are reconfigured to VLAN 2 in trunk mode. This mode of operation did not allow for the Cisco switch to be "plug-and-play" because the processor blades are on VLAN 1. In other words an external client could not establish a connection with a BladeCenter processor blade because of the VLAN mismatch. With this new software load, all ports default to VLAN 2. Any external client can be "plug-and-play" with the BladeCenter processor blades. On-site configuration can now be done over the serial interface. CSCeg16833   Symptoms: After 49.7 days, the internal BladeCenter processor blades will drop link any time a processor blade is restarted for any reason. A 32-bit counter took 49.7 days to reach its maximum value. After this time, the software compare did not work properly. This problem manifested itself whenever any processor blade was restarted for any reason. No DDTS number assigned Duplicate UUID On some switches a UUID assigned to one CIGESM was inadvertently assigned to another CIGESM during the manufacturing process. This software performs a check on the UUID to ensure that it is unique. 16 July 2004 Version 12.1(14)AY1 - Build ID cigesm-i6q4l2-tar.121-14.ay1.tar This version corrects four Cisco software problems as noted in the June version of the Cisco Release Notes. CSCee42900 CSCee53625 CSCee22478 CSCee34374 CSCee42900 When the external ports of the switch are forced into a non-autonegotiation mode, this can sometimes cause data flow to cease. It is a problem with the receive path on the CIGESM. The external port of the switch will not receive packets. The workaround is to put the port into auto-negotiation mode. CSCee53625 Configuring RSPAN on the IGESM can cause it to create a data storm for both unicast and multicast traffic similar in behavior to a broadcast storm. When this occurs, the Ethernet traffic of the port being analyzed is duplicated by the configured reflector port and simultaneously transmitted on the RSPAN VLAN causing a continuous loop. This traffic floods the VLAN of both the RSPAN port, and the port being analyzed. All other VLANs are unaffected. This condition does not occur every time RSPAN is configured. It occurs whenever the reflector port is changed while an RSPAN session is already active. The workaround is to disable the RSPAN session as soon as possible after this error occurs. If the IGESM cannot be contacted, disable the ports on the upstream switch connection to the IGESM. Another alternative is to use a local SPAN to analyze the port. CSCee24478  If the user has already configured the administrative mode to dynamic and is trying to trunk desirable, he won't be able to make that change. Also if the user has configured the mode to be trunk desirable then he won't be able to change it to dynamic. However if the user has configured the mode to be static acces, then there is no issue in changing the mode. The workaround is to change the administrative mode to static access first. Apply the configuration and then change again to other desired mode. Note that changing the vlan configuration may result in loss of connectivity to the switch. If you are changing the configuration on a link through which you are connected to the ESM, then make sure you have alternate connection to the switch, otherwisee you may lose the connectivity. CSCee34374 The unique product identifier MIBs for the IGESM are not correct in the original software release - Version 12.1(14)AY. The following MIBs are in error: CISCO-PRODUCT-MIB.my (should be 592) CISCO-ENTITY-VENDORTYP-OID-MIB.my (should be 446) OLD-CISCO-CHASSIS-MIB.my (should be 422) There is no workaround. Go to the IBM web site for the latest level of software which corrects these MIBs. 14 June 2004 Version 12.1(14)AY - Build ID cigesm-i6q4l2-tar.121-14.ay.tar This is the GA-level of the Cisco Switch Module firmware 3.0 Installation and Setup Instructions ----------------------------------------- Ensure that the firmware is on a server that is accessible by the Cisco Switch Module Start a tftp server on the server that contains the firmware. When the tftp application starts, it displays an IP address in the form . Note this IP address for use later. change the tftp server directory to the directory that contains the firmware. On your server get to a DOS prompt. (In a Windows operating system, hit the start button, type "cmd", and then press .) Type: Telnet bbb.ccc.ddd.eee where bbb.ccc.ddd.eee is the IP address of the Cisco Switch Module. You should see the following prompt when the telnet session starts: Switch> Type in "en" and press enter. If the system asks for a UserID and Password, provide those. These can be obtained from your system administrator. After this, you should see the prompt below: Switch# Type archive download tftp:/// ( is the IP address of the server containing the firmware image as previously noted. is the firmware image you just downloaded from the web site.) cigesm-i6q4l2-tar.121-22.EA6a.tar is the standard image. cigesm-i6k2l2q4-tar.121-22.EA6a.tar is the cryptographic image. Hit Note that the old image will be erased before the software image is downloaded. This process is automatic. During this time of approximately 30 seconds, there are no updates to the view on the monitor. When the firmware load is complete type: write memory reload This now has the new OS image. You can verify the level from the Management Module or by typing: Show ver 4.0 Configuration Information ------------------------------- No special configuration is required. 5.0 Unattended Mode ------------------------------- Unattended Mode is not supported for updating the Cisco Switch Module firmware. 6.0 WEB SITES AND PHONE SUPPORT --------------------------- Information and assistance is available through the IBM Web site and by phone. 6.1 Web sites IBM Support Web Site: http://www.ibm.com/pc/support/ 6.2 Software service and support -------------------------------- Through IBM Support Line, you can get telephone assistance, for a fee, with usage, configuration, and software problems with xSeries servers, IntelliStation workstations, and appliances. For information about which products are supported by Support Line in your country or region, go to http://www.ibm.com/services/sl/products/. For more information about Support Line and other IBM services, go to http://www.ibm.com/services/, or go to http://www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). 6.3 Hardware service and support -------------------------------- You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. Go to http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the U.K., these services are available Monday through Friday, from 9 a.m. to 6 p.m. 7.0 NOTICES AND TRADEMARKS -------------------------- INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM, the e-business logo, eServer, IntelliStation, xxx, and xxx are trademarks of the IBM Corporation in the United States, other countries, or both. ****************************************************************** The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: e-business logo eServer IBM The following terms are trademarks of Cisco Systems in the United States, other countries, or both: Cisco Cisco Systems ****************************************************************** Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 8.0 Disclaimer (Required) ---------------------------- 8.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 8.2 Note to Government Users Include the following note after the disclaimer paragraph. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.