File name: readme_21_0_1_10.txt **************************************************************** | | | Nortel Networks Layer 2-7 GbE Switch Module (GbESM) for | | IBM eServer BladeCenter Firmware Update | | | | Revision/Build ID: 21.0.1.10 | | | | (C) Copyright International Business Machines Corporation | | July, 2006. 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 in "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated <31 October 2006> | **************************************************************** CONTENTS ________ 1.0 About this README file 2.0 Change history 3.0 Installation and setup instructions 3.1 Software update procedure 3.1.1 Using Telnet 3.1.2 Using BBI 3.2 How to check the firmware version 4.0 Configuration information 5.0 Unattended Mode 6.0 Web information and support phone number 6.1 Web sites 6.2 Software service and support 6.3 Hardware service and support 7.0 Notices and trademarks 8.0 Disclaimer 8.1 Document provision 8.2 Note to government users 1.0 ABOUT THIS README FILE __________________________ This file is intended for network administrators responsible for upgrading the firmware for the Nortel Networks Layer 2-7 Gigabit Ethernet Switch Module (GbESM). For a summary of GbESM features, supplemental information and known issues associated with the 21.0 release, please refer to the "Release Notes: Layer 2-7 GbE Switch Module for IBM BladeCenter", available via web sites indicated in section 6.1. 2.0 CHANGE HISTORY __________________ Version 21.0.1.10 (Released October 2006) Enhancements: - Health Check based on Session Initiation Protocol (SIP) register request. For SIP register health check, the switch sends a SIP REGISTER request to the configured server(s). It looks for response message type "1xx", "2xx", "3xx", or "4xx" to determine if the server is UP. If the switch receives a response message type "2xx", "3xx" or "4xx" the server(s) are declared as UP. If switch receives a type "5xx" or "6xx" response the switch will declare the server(s) as DOWN. - The restriction for a users to configure two Proxy IP addresses (PIPs) when using the PIP feature has been removed. Some customers may need only one PIP while others may need two PIPs. This changes provides flexibility for the use of the Proxy IP function. Fixes: - A possibility of a Panic caused by two SNMP (Simple Network Management Protocol) threads attempting to grab same semaphore was eliminated. (fix number 7092) - Corrected a condition where Cisco tagged BPDUs (Bridge Protocol Data Units) were being transmitted on an untagged switch port. (fix number 8653) - Corrected a condition where the IBM Management Module (MM) may receive duplicate acknowledgements to the push of an IP address on the reboot of the switch. The second response was intrepreted by the MM as an unsolicited IP change, thus causing the MM to clear the switch IP resulting in a drop of the connection to the switch. This fix checks the extended control register on the switch module (IPCfgFromVPD) before signaling the MM that the switch POST is complete, and switch is ready to receive the IP address. This fix may lengthen the diagnostic completion time for the switch. (fix number 8964) - Initial packet across trunk is duplicated, that is Broadcast packets were being sent out of all ports in a trunk. (fix number 9084) - The BladeCenter Management Module (MM) console does not display a valid Released date for a Nortel Layer 2-7 GbESM (Gigabit Ethernet Switch Module) with version 21.0.1.1 firmware installed. (reference RETAIN tip: H187301) For the CLI (command line interface) correct information is reported by the MM after the switch reset following the firmware update. The BBI and the SNMP interface however required a different code fix. If the BBI (browser based interface) and SNMP interface must be used, and correct "Build ID" and "Released" date information in MM VPD (Vital Product Data) is required, the user must install the OS file, GbESM-AOS-21.0.1.10_os.img,twice. Specifically, with the BBI or SNMP interface the user must: a. download the OS image, b. make the Next Boot Image Selection be the 21.0.1.10 OS image, and reset the switch, booting with this image. c. load the OS file, GbESM-AOS-21.0.1.10_os.img, a second time. d. load the Boot file, GbESM-AOS-21.0.1.10-Boot.img, and reset. The reason for requirement for the user to repeat the update procedure, when using the BBI or SNMP switch interface follows: For updating VPD information - the switch needs two things: a. The image downloaded to the switch must have the "Born On" string appended to the image. This information was missing in 21.0.1.1. b. The booted image which downloads a new image to the switch has to extract the "Born On" string from the new image and write it to the VPD. The BBI/SNMP TFTP/FTP get image code was not saving the extracted "Born On" string from the image to the VPD in 21.x code other than 21.0.1.8 & later. The CLI get image was not having this problem. So if you booted with 21.0.1.1 and use BBI/SNMP TFTP/FTP get image to download 21.0.1.10 the VPD information will not be updated (as the code to update the VPD was missing in 21.0.1.1). However if you now reboot into 21.0.1.10 you will be able to update the VPD if you re-download a 21.0.1.10 image (or any other image which has the "Born On" string). Version 21.0.1.1 (Released April 2006) Changes: - Spanning Tree Group is off by default on ports MGT1 and MGT2 - Preemption feature is supported for both Virtual Router and Virtual Router Groups. It can be disabled with both modes, Active-Active and Hot-Standby. The CLI commands for Preemption feature are: On Virtual Router: /c/l3/vrrp/vr x/preem ena(dis) On Virtual Router Group: /c/l3/vrrp/group/preem ena(dis) Fixes: - Fixed TCP retransmission issue with sequence number when HTTP load is configured (Q01073886) - Enabled configure TCP rate limiting feature in BBI (Q01089450) Enhancements: - Major features in 21.0 are: TSLB (Terminal Server Load Balancing) GSLB (Global Server Load Balancing) SIP Load Balancing Smart Failover (VLAN based failover) Support for OSPF equal cost routing Static Multicast Routing eWLM Trunking on internal ports SSH V2 SNMP V3 250 IP Interfaces Strong Password Support - Please refer to the 21.0 Release Notes, the updated Application Guide and the updated Command Reference for details of the new software features included with this release. Version 20.2.2.7 (Released November 2005) Changes: - MGT port configuration fixed at 100 Mbps Full Duplex Fixes: - Infrequent loss of Management Module link - Switch resets after 512 IP address saves Enhancements: - LDAP Health Check now compatible with Microsoft LDAP server Version 20.2.2.6 (Released June 2005) Fixes: - Retransmitted packets may get erroneously dropped when Layer 7 is enabled - VRRP Hot-Standby failover timing improvements - Incorrect VRRP errors are logged when VR is disabled Enhancements: - Added test to Extended/Full diagnostics Version 20.2.2.2 (Released March 2005) Fixes: - Fragmented packets get dropped when Filters are enabled - RDM 4.20 - Multicast is extremely slow when using IP fragmentation - Unable to configure server processing via BBI - Cannot enable 32-bit IP Interface within a subnet of an existing 24-bit IP Interface - Switch doesn't forward any DHCP client request to BOOTP server - Link to HS40 is sometimes down when blade is in slot 7/8 and GbESM is in Bay 2 of a Telco chassis - MIB File cleanup - Corrected VRRP/L2 Trunking error messages Version 20.2.1.1 [Released November 2004]: Changes: - Default STP setting on INT Ports is now disabled for all STGs Fixes: - Disabling Tagging on ports INT1 and INT2 may hang telnet session - The MM webui "External Ports=Disabled" setting does NOT prevent enabling an external port - When OSPF is configured, the VSR/VIP does not get withdrawn from the route table when VSR goes down - Any new OSPF adjacencies fail after the routing table is full - Specific trunk configuration sequence may cause port EXT1 to enter a BLOCKING state - When VLAN 1 is disabled, the BBI displays a PVID of 2 and shows VLAN 1 as enabled - Cannot upgrade GbESM BOOT Code via SNMP Enhancements: - BladeCenter-T Support - 32bit Minmisses Server Load Balancing metric - Server Processing on EXT ports - L2 Trunk Failover with VRRP - TACACS+ - IGMP Snooping - Secondary NTP Server - Fast Uplink Convergence support Version 20.1.2.3 [Released August 2004]: Fixes: - Network boot on a JS20 Blade from a Network Installation Manager (NIM) Server does not complete successfully. Version 20.1.2.2 [Released July 2004]: Fixes: - When a SAVE is performed via BBI on a Factory Default GbESM, it does not change the 'Next Boot Configuration Block Selection' to Active. - SNMP MIB walk fails - general error is displayed. - When Management Processor is stressed over an extended period the GbESM may reboot. - When VLAN is disabled, it is not saved through a reset. - When telneting from the GbESM to another device, the characters are repeated. - When restarting the switch using Full POST (diagnostics), intermittent 0x1d, 0x41, 0x43 and 0x45 test failures may occur. - When telneting from the GbESM to another device, the password is displayed in clear text. - When factory defaulted, the default IP address of the GbESM does not reflect the slot in which the switch is installed. - If the uplink trunk with L2 Trunk Failover enabled consists of 3 or 4 ports and all links are dropped simultaneously, then the GbESM may not disable the INT ports as expected. Enhancements: - Link state changes during boot process are minimized. - New CLI message reminds the user that VLAN 4095 traffic cannot be mirrored to any external port. - Radius Authentication enhanced to interoperate with CiscoSecure ACS 3.2 for Solaris Version 20.1.1.0 [Released April 2004]: Changes: - Default INT Port configuration changed - ports have tagging enabled and are members of VLAN 1 and 4095 - Default MGT Port configuration changed - ports have tagging enabled - Link failover optimization for link aggregation Fixes: - When configured, the OSPF default route is not used - When a default gateway for IP IF 128 is configured, server blade traffic may utilize the wrong gateway - When 4 gateways are configured, the GbESM may only use two of them - Hashing algorithm for server load balancing metric hash does not balance the traffic correctly Enhancements: - Four GbESM support - L2 Trunk Failover (network adapter teaming support) - VRRP Hot-Standby (network adapter teaming support) - Serial-over-LAN support - Link Aggregation Control Protocol (LACP) - Configurable Trunk Hash algorithm - Port Fast Forwarding Version 20.0.1.3: [Released October 2003] Fixes: - TCP session may timeout if a single link of a trunk group is disconnected Version 20.0.1.2 [Released September 2003] Fixes: - Default STP configuration changed - Default STP setting for internal ports (INT1-INT14) is OFF - IBM Remote Deployment Manager and PowerQuest DeployCenter do not complete successfully 3.0 INSTALLATION AND SETUP INSTRUCTIONS _______________________________________ The GbESM firmware is comprised of two (2) code images. The boot code and a switch operating system. The GbE switch module ships with this firmware pre-installed. However, new versions of the firmware are periodically released and can be used to update the features and function of the switch. 3.1 Software update procedure ----------------------------- Update the switch software using a TFTP or FTP server application. Typically, this application is installed on a machine that is reachable from the switch through the external ports or the management module. NOTES: - The following steps reflect the use of a TFTP server. A FTP server can also be used. - Upgrades can also be performed using external ports. Please see "Externally managing the GbE switch module" in the GbESM Installation Guide. 1) Download the GbESM software package (zip file) to the machine where the TFTP server resides. 2) Extract the Boot and OS image files into a directory. Enable the server and set its default directory to the one where the image files reside. 3) Establish a connection between the ethernet port of the BladeCenter Management Module and the TFTP Server. 4) Using the Management Module web interface (GUI), configure the IP Addr/Mask of the Management Module External (eth0) and Internal (eth1) interfaces, the GbESM switch and the TFTP server so that they all reside on the same subnet. For example, Management Module (eth0) => 192.168.70.125 / 255.255.255.0 Management Module (eth1) => 192.168.70.126 / 255.255.255.0 GbESM Current IP Config => 192.168.70.127 / 255.255.255.0 TFTP Server => 192.168.70.254 / 255.255.255.0 NOTE: Although configured as such, for this example, the TFTP Server does not have to be on the same subnet as long as a proper gateway address is configured in the switch. 3.1.1 Using Telnet ------------------ 1) Using the Management Module GUI, navigate to: I/O Module Tasks -> Management -> Bay X -> Advanced Management -> Start Telnet session When the telnet session is established, you will begin using the Command Line Interface (CLI) of the GbE switch. 2) Enter "admin" for the password. The GbE switch provides storage for two (2) OS images and one (1) Boot image. What you are about to do consists of the following sequence: - load the new OS image into one of the image banks - reset the switch - load the Boot image - reset the switch NOTE: When you reset the switch it boots using the 'selected' image (1 or 2). Please ensure that you are booting from the upgraded image (execute /boot/cur to determine). 3) Upgrade the OS image by entering the following commands: a) /boot/gtimg X TADDR GbESM-AOS-21.0.1.10-OS.img WHERE: ------ X => 1 or 2 (depends which image bank you want to use) TADDR => IP Address of the TFTP Server NOTE: It is recommended that you retain the previous OS version by loading the upgrade into the other image bank and then reset the switch using the new image. (use /boot/image command to select preferred image) Answer 'Y' to the confirmation question, then wait for the upgrade to complete successfully. b) /boot/reset NOTE: You MUST Reset the switch to activate the new image. Resetting the switch kicks you out of the CLI, so Steps 1 and 2 need to be executed again before proceeding to the next step. A switch reset completes in approximately 60 seconds. 4) Upgrade the Boot image by entering the following commands: a) /boot/gtimg boot TADDR GbESM-AOS-21.0.1.10-Boot.img Answer 'Y' to the confirmation question, then wait for the upgrade to complete successfully. b) /boot/reset 3.1.2 Using BBI --------------- 1) Using the Management Module GUI, navigate to: I/O Module Tasks -> Management -> Bay X -> Advanced Management -> Start Web session 2) Enter "admin" for the username and 'admin' for the password. 3) Click the CONFIGURE button (near top of page) 4) In the frame on the left, click on the "Nortel Networks Layer 2-7 GbE" folder icon and navigate to: System -> Config/Image Control The GbE switch provides storage for two (2) OS images and one (1) Boot image. What you are about to do consists of the following sequence: - load the new OS image into one of the image banks - reset the switch - load the Boot image - reset the switch NOTE: When you reset the switch it boots using the 'selected' image (1 or 2). Please ensure that you are booting from the upgraded image (see "Next Boot Image Selection" field). 5) Upgrade the OS image as follows: a) Fill in the following three (3) fields on the lower half of the page: Hostname or IP Address of FTP/TFTP server => Image Filename => GbESM-AOS-21.0.1.10-OS.img Image for Transfer => 1 or 2 (i.e. the preferred image bank) NOTE: It is recommended that you retain the previous OS version by loading the upgrade into the other image bank and then reset the switch using the new image. (use the "Next Boot Image Selection" field to select the preferred image). b) Click the "Get Image" button. Wait for the upgrade to complete successfully. c) Click the "REBOOT!" button to reset the switch. NOTE: You MUST Reset the switch to activate the new image. Resetting the switch kicks you out of the BBI, so Steps 1-4 need to be executed again before proceeding to the next step. A switch reset completes in approximately 60 seconds. 6) Upgrade the Boot image as follows: a) Fill in the following three (3) fields on the lower half of the page: Hostname or IP Address of FTP/TFTP server => Image Filename => GbESM-AOS-21.0.1.10-Boot.img Image for Transfer => boot b) Click the "Get Image" button. Wait for the upgrade to complete successfully. c) Click the "REBOOT!" button to reset the switch. 3.2 How to check the firmware version ------------------------------------- To check the version of the firmware images installed on the GbESM, use either of the following methods: a) From the CLI, execute the command: /boot/cur This command displays (for example): Currently set to boot software image1, active config block. Current FLASH software: image1: version 21.0.1.10, downloaded 0:08:48 Tues Sep 30, 2006 image2: version 21.0.1.1, downloaded 0:08:48 Thu Apr 1, 2006 boot kernel: version 21.0.1.10 b) Using the Management Module GUI, navigate to: Monitors -> Firmware VPD Scroll down to view the VPD info for the appropriate GbE Switch. You should see the following entries: FIRMWARE TYPE BUILD ID RELEASED REVISION ------------- -------- -------- -------- Boot ROM WM01010 10/26/2006 2100 Main Application 1(or 2) WM01010 10/26/2006 2100 The four digits comprising the version (e.g. 21.0.1.0) correlate to the REVISION/BUILD ID as follows: - Revision => 21 00 ... the first 2 digits of the version - Build ID => 01 001 ... the last 2 digits of the version 4.0 Configuration information _____________________________ For detailed switch configuration, please refer to, "Command Reference - Layer 2-7 GbE Switch Module for IBM eServer BladeCenter", available at the web sites indicated in section 6.1. 5.0 Unattended mode ___________________ Unattended Mode is not supported for updating the Nortel Switch Module firmware. 6.0 Web information and support phone number _______________________________ Information and assistance is available through the IBM Web site and by phone. World wide Help Center Telephone Numbers and URL's can be found at: http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html 6.1 Web sites ------------- IBM Support Web Site: http://www.ibm.com/pc/support/ or http://www.ibm.com/support/ IBM eServer Web site, for model information and literature: http://www.ibm.com/eserver/xseries/ 6.2 Software service and support -------------------------------- Through the 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/ For support telephone numbers go to http://www.ibm.com/planetwide/ 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. For support telephone numbers go to http://www.ibm.com/planetwide/ 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 __________________________ The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: e-business logo eServer IBM xseries BladeCenter The following terms are trademarks of Nortel Networks in the United States, other countries, or both: Nortel Nortel Networks 8.0 DISCLAIMER ______________ 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. 8.1 Document provision ---------------------- 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 ---------------------------- 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. e. 8.1 Document provision ---------------------- 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 ---------------------------- 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.