UpdateXpress firmware update scripts for BladeCenter Version 2.0 File Name: readme.txt ****************************************************************** | | | IBM(R) UpdateXpress Firmware Update Scripts for BladeCenter, | | Version 2.0 | | | | (C) Copyright International Business Machines Corporation, | | 2004, 2005. 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 27 January 2005 | | | ****************************************************************** Contents --------- 1.0 About this README file 1.1 Abbreviations and terminology 1.2 Overview 1.3 Minimum requirements 1.4 Supporting operating system 2.0 Change History 2.1 UXBC Version 2.0 2.2 UXBC Version 1.0 3.0 Getting Started 3.1 Obtaining the product 3.2 Unzip the zip file 3.3 Obtaining the firmware updates for use with the UXBC tool 4.0 Run BladeScanner to create response file 4.1 Running BladeScanner in "scan" mode 4.2 Running BladeScanner in "edit" mode 4.3 BladeScanner and Blade IP Address discovery 5.0 Starting the update process 5.1 Specifying a default response file 5.2 Displaying the version 5.3 Viewing help 5.4 Viewing verbose information 6.0 Return Codes 7.0 Limitations 7.1 BladeScanner in "scan" mode requires MM firmware version 53C or higher 7.2 Management modules 7.3 IBM ESM configuration 7.4 Multiple instances of ChassisUpdate 7.5 Cross-Platform Issues 7.6 gnome-terminal Issues 7.7 remoteux and Reiser FS on xSeries systems 7.8 remoteux requires compat-libstdc++-7.2-2.95.3.77 7.9 Firmware updates on JS20 forces a reboot 7.10 Do not change media tray when remotely updating Linux Blades 7.11 remoteux does not update the Broadcom firmware on the JS20 7.12 remoteux requires Perl on the target systems 7.13 remoteux does not update the Broadcom firmware on the BladeCenter(8843) Blade 8.0 Web Sites and Support 9.0 Notices and Trademarks 10.0 Disclaimer 1.0 About this Readme file ----------------------------- This readme file provides information about IBM UpdateXpress firmware update scripts for BladeCenter Version 2.00 1.1 Abbreviations and terminology ----------------------------------- The following abbreviations are used in this readme file: UXBC UpdateXpress firmware update scripts for BladeCenter (this product) Administrative System The system where UXBC is launched. Target System The BladeCenter chassis and all of its components, including the management module, I/O Modules, and blades. 1.2 Overview ----------------- UpdateXpress firmware update scripts for BladeCenter (UXBC) is a tool to remotely and unattendedly update firmware in a BladeCenter chassis. The update tools consists of a detection program (BladeScanner) and Python scripts which perform the actual updates. BladeScanner is used to create the response file that the Python scripts require. The response file primarily consists of the username/password of the components being updated, and the location of the update images. UXBC is launched from the "Administrative system". There are two distinct UXBC images, one is for Windows and the other is for Linux "Administrative systems". Blades running Windows can only be updated from a Windows Administrative system. Blades running Linux can only be updated from a Linux Administrative system. The non Blade components, such as Management Module and IO Modules can be updated from either a Windows or a Linux Administrative system. The following components can be updated from an Administrative system: o Management modules (one or two) o IBM BladeCenter 4-Port Gb Ethernet Switch Module o Nortel Layer 2-7 Gigabit Ethernet Switch Module o Cisco Systems Intelligent Gigabit Ethernet Switch Module o IBM BladeCenter 2-port Fibre Channel Switch Module (Q-Logic) Switch Module o QLogic Enterprise 6-port Fibre Channel Switch Module for IBM eServer BladeCenter o Brocade Enterprise and Entry SAN Switch Module for IBM eServer o IBM eServer BladeCenter OPM (Optical Pass- thru Module (OPM)) o IBM eServer BladeCenter CPM (Copper Pass- thru Module (CPM)) The following Blades can be updated from a Windows "Administrative system": o HS20 (8678) Blade (Windows) o HS20 (8832) Blade (Windows) o HS40 (8839) Blade (Windows) o HS20 (8843) Blade (Windows) The following Blades can be updated from a Linux "Administrative system": o HS20 (8678) Blade (Linux) o HS20 (8832) Blade (Linux) o HS40 (8839) Blade (Linux) o HS20 (8843) Blade (Linux) o JS20 (8842) Blade (Linux) 1.3 Minimum Hardware Requirements ---------------------------------- The following hardware is required to run UXBC on an Administrative System: o 1 GHZ or faster CPU o 512 MB memory o 100 Megabit of faster Ethernet network card o 1GB available disk space - 160MB for UXBC update tool - 640MB for UX-CD1 - 200MB for UX-CD2 (if using JS20) o Do not run the Administrative system on a Blade that is in a BladeCenter that is being updated. It is recommended that the UXBC scripts be run on a LAN behind a firewall. All media and transmission types that reliably support TCP/IP and FTP in a LAN environment are supported. 1.4 Supporting operating systems -------------------------------- UXBC can be launched from the following operating systems installed on the administrative system: o Windows 2000 (all versions) o Windows XP o Windows 2003 (all versions) o RHEL AS/WS/ES 2.1 o RHEL AS/WS/ES 3.0 o SLES 8 o SLES 9 1.4.1 Software requirements --------------------------- 1.4.1.1 Python Version 2.3 or later ----------------------------------- The Python update scripts that perform the update require that the Python interpreter (Version 2.3 or later) is installed on the administrative system. You can download the Python interpreter for your operating system from the Web: www.python.org 1.4.1.2 TFTP server ------------------- A TFTP server is required to host the firmware updates for the following I/O modules: o IBM BladeCenter 4-Port Gb Ethernet Switch Module o Nortel Layer 2-7 Gigabit Ethernet Switch Module o Cisco Systems Intelligent Gigabit Ethernet Switch Module If you are using one of the above I/O modules you will need an TFTP server installed on your network that is accessible from the I/O Modules being updated. 1.4.1.2 FTP server ------------------ An FTP server is required to host the firmware updates for the following I/O modules: o IBM BladeCenter 2-port Fibre Channel Switch Module (Q-Logic) Switch Module o QLogic Enterprise 6-port Fibre Channel Switch Module o Brocade Enterprise and Entry SAN Switch Module If you are using one of the above I/O modules you will need an FTP server installed on your network that is accessible from the I/O Modules being updated. 2.0 CHANGE HISTORY ------------------- 2.1 UXBC Version 2.0 - Added BladeScanner utility to maintain response files - Added support for Brocade, QLogic, Nortel and Cisco switches - Added support for OPM, CPM pass through modules - Added Blade firmware update support - Added RemoteUX for Linux 2.2 UXBC Version 1.0 - Initial Release - Python script support for Management Module, IBM ESM I/O switch and Nortel switch (73P9044) 3.0 GETTING STARTED ---------------------- 3.1 Obtaining the product ------------------------- Download the UXBC zipped files from this update tool's URL: www-1.ibm.com/servers/eserver/xseries/systems_management/sys_migration/uxs.html Or search for it at the IBM support Web site: www.ibm.com/pc/support/ There are two zip files, one is for Windows and the other is for Linux. 3.2 Unzip the zip file ----------------------- Extract the contents of the zipped file. On Linux make sure that the unzip process preserves the case and file attributes. When the UXBC file is unzipped, the following directories are created: (example unzips package to Windows c: drive) c:BladeCenterUpdates (root of the package) c:BladeCenterUpdates\Common - Common functions/definitions c:BladeCenterUpdates\IOModules - Scripts for I/O Modules such as switches c:BladeCenterUpdates\MM - Scripts pertaining to Management module(s) Important: Do not assign the Adminstration System to a blade that is in the BladeCenter chassis that you are updating. Because firmware updates are performed on components that are part of the support structure of the BladeCenter system, the firmware update process must be run from a completely independent system. 3.3 Obtaining the firmware updates for use with the UXBC tool ------------------------------------------------------------- Complete the following steps to obtain the firmware updates used with UXBC: Step 1. Obtain Management Module firmware update files a) Download the latest firmware update for the management modules from the IBM Support Web site. This update file is a zipped file. Do not unzip this update file in the \BladeCenterUpdates directory or you will end up replacing the UXBC readme file with the management module package readme file. b) Unzip the management module package to a temporary directory and copy the files with extension .PKT to the UXBC tool's default directory (\BladeCenterUpdates). This tool only requires the files with extension of .PKT. If you place the .PKT files in an alternate location, make a note of the path; you will need this information when you run BladeScanner to create the response file. Step 2. Obtain I/O Module firmware updates a) Download the latest firmware updates for the I/O modules. See "1.2 Overview" for the I/O modules that UXBC supports. You can obtain the firmware for the I/O modules from the IBM Support Web site. b) Copy the firmware update to the correct location. The location to place the firmware varies depending on the I/O module. For each case record the following information: o The path to the unzipped firmware files. o The names of the I/O module firmware files. Copy the firmware update to the TFTP server for the following I/O modules: o IBM BladeCenter 4-Port Gb Ethernet Switch Module o Nortel Layer 2-7 Gigabit Ethernet Switch Module o Cisco Systems Intelligent Gigabit Ethernet Switch Module Copy the firmware update to the FTP server for the following I/O modules: o IBM BladeCenter 2-port Fibre Channel Switch Module (Q-Logic) o QLogic Enterprise 6-port Fibre Channel Switch Module for IBM eServer BladeCenter o Brocade Enterprise and Entry SAN Switch Module for IBM eServer Copy the firmware update to the same location as the management module firmware update, as performed in step 1.b above, for the following I/O pass through modules: o IBM eServer BladeCenter OPM (Optical Pass- thru Module (OPM)) o IBM eServer BladeCenter CPM (Copper Pass- thru Module (CPM)) Step 3. Obtain version 3.06 of the UpdateXpress CDs (UX-CD 1 and UX-CD 2). If you don't already have the CDs, the ISO images can be downloaded by clicking on the link to the latest version in URL : http://www-1.ibm.com/servers/eserver/xseries/systems_management/sys_migration/xpress.html If you are updating a JS20 Blade you need UX-CD 2, all other Blades require UX-CD 1. Copy the UpdateXpress CD(s) and their contents to a directory on the Administrative system, and make a note of this directory. You will need this directory later when running the BladeScanner utility. If both CDs are needed, first copy CD 1, then copy CD 2 to the same directory allowing the copy to overwrite any existing files. Note: If you copy the UpdateXpress CDs to the tools default directory (BladeCenterUpdates) the README will be overwritten. 4.0 Use BladeScanner to create the Response file ------------------------------------------------ A significant amount of information is required to perform the firmware updates of a BladeCenter chassis. The UXBC software obtains the parameters that are needed to perform the updates by using the information from a response file. This response file is created and edited by BladeScanner utility. The default name of this response file is BladeCenterUpdates.rsp. BladeScanner is an ascii text based menu driven application that prompts with online help as you attempt to update each field. 4.1 Running BladeScanner in "scan" mode ----------------------------------------------------------- Note: If the Management Module firmware is version 52A or lower do not run the BladeScanner program in "scan" mode. Please see section 7.1 for details. Perform the following steps to create your response file: Step 1. Run BladeScanner in "scan" mode (-s parameter) Syntax: BladeScanner -s -r response_file -t ip_address [-y start_rng -z end_rng] [-u user -p pwd] (Note: "[-u user -p pwd]" is continued on the next line only because of line length limitations) where "response_file" is the name of the response file. "ip_address" is the IP address of the Managmement Module "start_rng" is the start range of the IP addresses to start the scan for Blade servers. "end_rng" is the end range of the IP addresses to end the scan for Blade servers. "user" is the username to use to authenicate with the Management Module. "pwd" is the password to use to authenicate with the Management Module. BladeScanner will connect to the Management Module and discover and report the Management Module(s), the I/O Modules and the Blades present in the BladeCenter. Specifying the optional Blade IP address range (-y and -z paramaters) causes BladeScanner to attempt to find Blades in the given address range. Without specifying a Blade IP address range, each Blade is identified by the Bay number. This IP address range option helps to identify individual blades that are present by discovering their IP address in each Blade menu page. BladeScanner can only discover IP addresses from like O/Ses. That is running BladeScanner from Windows can only discover IP addresses of Blades running Windows, and similarily running BladeScanner from Linux will only discover IP addresses of Blades running Linux. Example 1 : bladescanner -s -r resp.rsp -t 192.1.1.5 Create the response file "resp.rsp" and scan the BladeCenter which has a Management Module with an IP address of 192.1.1.5 The user will be prompted for the Management Modules username and password. The Blades are not scanned for IP addresses (no -y and -z option), instead the user will have to manually add these values. Example 2: bladescanner -s -r resp.rsp -t 192.1.1.5 -y 192.1.1.10 -z 192.1.1.20 Same as example 1, plus the BladeScanner will attempt to detect Blades that have IP addresses in the range 192.1.1.10 to 192.1.1.20 and will automatically populate the IP address of those Blades that it can detect. Step 2. Complete fields in each of the BladeScanner Menus while in "scan" mode. Some of the more important fields are highlighted in this section. Step 2.1 Complete "Management Module" menu "Auto continue:" - This option specifies that if the Management Module is configured via DHCP, flashing of the I/O modules should occur automatically even if it is not possible to FLASH the Management Module. "Management Module Updates:" - Enable or disable updates for the Management Module. "Management Module Reboot:" - Some management applications may cause the 6090 TCP port of the Management Module to remain in a locked state and inaccessible by applications, such as this update tool. If you enable this field you will permit the update scripts to reboot the Management Module and release this port. Step 2.2 Complete "I/O Modules" menu(s) "Flash File 1:" - Path and filename of the I/O module flash file from the root of the TFTP/FTP server. If this is a Nortel switch, the OS image must be flash file 1. "Flash File 2:" - Path and filename of the I/O module flash file from the root of the TFTP/FTP server. If this is a Nortel switch, the boot image must be flash file 2. This field is not set if the I/O module only requires one update file. "I/O Module Updates:" - Enable or disable updates for this I/O module. Changing this value will cause this field in the "Update and Reboot Options" menu to be set to "Modified in I/O Module menu". Step 2.3 Complete "Blades" menu(s) "Blade Updates:" - Enable or disable updates for this Blade. Changing this value will cause this field in the "Update and Reboot Options" menu to be set to "Modified in Blade menu". "Force Blade Reboot:" - Enable or disable updates for this Blade. Changing this value will cause this field in the "Update and Reboot Options" menu to be set to "Modified in Blade menu". RemoteUX schedules firmware updates to run the next time the Blades are rebooted. This option forces the Blades to reboot immediately after RemoteUX schedules the firmware updates on the target Blades. This corresponds to the "-a -r" RemoteUX option. Step 2.4 Complete "File Options" menu "TFTP IP Address:" - The dotted IP address of the TFTP server which contains the update images for : o IBM BladeCenter 4-Port Gb Ethernet Switch Module o Nortel Layer 2-7 Gigabit Ethernet Switch Module o Cisco Systems Intelligent Gigabit Ethernet Switch Module "FTP IP Address:" - The dotted IP address of the FTP server which contains the update images for : o IBM BladeCenter 2-port Fibre Channel Switch Module (Q-Logic) o QLogic Enterprise 6-port Fibre Channel Switch Module o Brocade Enterprise and Entry SAN Switch Module "Local File Location:" - Path to the directory containing the updates for the Managment Module and the OPM and CPM Pass-thru I/O Modules. "Blade Updates Location:" - Path to the directory where the UpdateXpress CDs were copied. This is used by remoteux. Step 2.5 Complete "Update and Reboot Options" menu "Management Module Updates:" - Enable or disable updates for the Management Module. This is the same as the "Management Module Updates:" field in the "Management Module" menu. "Management Module Reboot:" - This is the same as the "Management Module Reboot:" field in the "Management Module" menu. "I/O Module Updates:" - Enable or disable updates for ALL I/O modules. Setting this field will overwrite any settings in the individual I/O Module submenus. "Blade Updates:" - Enable or disable updates for ALL Blades. Setting this field will overwrite any settings in the individual Blade submenus. "Force Blade Reboot:" - Changing this will change this field for ALL Blades and will overwrite any settings in the individual Blade submenus. Step 3. Save and Exit the BladeScanner Save the response file and exit the BladeScanner application. When the response file is completed, you can run the main script (ChassisUpdate.py). The update process uses the information in the response file as input to the script. Note that after the initial response file is created for any BladeCenter chassis, future firmware update processes using the same response file might require modifications if information such as IP addresses or firmware file names has changed. 4.2 Running BladeScanner in "edit" mode ---------------------------------------- Run BladeScanner in "edit" mode (-e parameter) if you wish to edit an existing response file that you already created with BladeScanner. Follow steps 2 to 3 in section 4.1 above. BladeScanner creates a response file from scratch if the supplied response file does not already exist. When creating a new response file in edit mode you will have to manually enter all of the fields in the menus. Syntax: bladescanner -e -r response-file where "response-file" is the name of the response file to edit Example 1 : bladescanner -e -r resp.rsp Edit the response file "resp.rsp". 4.3 BladeScanner and Blade IP Address discovery ----------------------------------------------- In scan mode, BladeScanner communicates with the BladeChassis' Management Module to automatically discover how the Bays in the BladeChassis are populated. The Management Module does not report the IP address(es) of the Blades, but it does report the MAC addresses of the Blades' network adapters. This means that BladeScanner cannot automatically populate the IP address for the user. However if the user supplies a scan range (-y and -z options) BladeScanner will ping this IP address range. If it gets a response with the Network Adapter's MAC Address it can determine the Blade that a particular IP address is associated with. What this means is that BladeScanner can discover the Blades' IP addresses if BladeScanner is executing from a system on the same subnet as the Blades. 5.0 Starting the update process --------------------------------- When you have completed all the steps described in "3.0 Getting started," and "4.0 Use BladeScanner to create the Response file" you can start the UXBC firmware update process. To start the UXBC process, start the main script, ChassisUpdate.py. To run the ChassisUpdate script, call the main script directly or call the main script through the Python interpreter. From the command prompt, type one of the following commands and press Enter. These commands are case-sensitive. To call the main script, type ChassisUpdate.py [options] To call the main script through the Python interpreter, type python ChassisUpdate.py [options] options: -r FILE, --responseFile=FILE The path and name of the response file. -h, --help, -? Display the help message. -v, --verbose Verbose or debug message output. -V, --version Display the version number and exit. Example: python ChassisUpdate.py -r resp.rsp where resp.rsp is the response file to use for the update 5.1 Updating Blades that are running both Linux and Windows ----------------------------------------------------------- Blades running Windows can only be updated from a Windows Administrative system. Similarily, Blades running Linux can only be updated from a Linux Administrative system. If you wish to update Blades that are running a dissimilar O/S than your UXBC Administrative system, you will need to run UXBC from a system with the same O/S type as the target Blades. Follow the steps you already performed in sections 3 and 4, but this time choose a similar O/S as the target Blades. i.e. if the target Blades are running Linux, choose a Linux Administrative system. Or if the target Blades are running Windows, choose a Windows Administrative system. In the following example the BladeCenter consists of Blades running Windows and Linux. UXBC was initially installed on a Administrative system running Windows. A response file was created using BladeScanner (scan mode) and ChassisUpdate was performed using this response file. Follow the following steps to update the remaining Windows Blades: Step 1. Install UXBC on a Linux system Step 2.0 Copy the existing response file to the UXBC Linux system Step 2.1 Run BladeScanner in "edit" mode. Disable updates on the MM and I/O modules ("Update and Reboot Options" menu) Change the "Blade Updates Location" field as appropriate Complete the Linux Blade information ("Blades" menu) Or instead of steps 2.0 - 2.1 Step 3.0 Run BladeScanner in "scan" mode, supplying the MM authentication information, and the Blade IP address range. Disable updates on the MM and I/O modules ("Update and Reboot Options" menu) Change the "Blade Updates Location" field as appropriate Complete the Linux Blade information ("Blades" menu) Step 4. Run ChassisUpdate to update the Linux Blades. Since disable updates for MM and I/O Modules was selected, these ChassisUpdate will not update these components again. 5.2 Blade updates and Interaction with remoteux ----------------------------------------------- UX-BC uses remoteux to update firmware on Blades. remoteux for Windows is available on UX-CD 1 and UX-BC will automatically invoke it as part of the Blade update. remoteux for Linux is not available on the UX-CDs, but is present in UX-BC tool. The arguments passed to remoteux are controlled by the response file that bladescanner generates. The following arguments to remoteux are controlable from bladescanner : RemoteUX (Windows) remoteux (Linux) bladescanner field ================== ================= ================== -u:user -u user "Blades"menu -> "User Name" -p:password -p password "Blades"menu -> "Password" -a -r -a -r "Blades"menu -> "Blade Reboot" (For a specific Blade) -r:location -r location "File Options"menu -> "Blades Update Location" -a -r -a -r "File Options"menu -> "Force Blades Reboots" (For all Blades) 6.0 Return codes ----------------- All information about the firmware update process is logged to the BladeCenterUpdates.log file. The log file is opened when the first error or message occurs and is closed when the update process is completed. Log file entries are in the format - . The time and date of the first entry indicates when the log file was opened, and the time and date of the last entry indicates when the update process was completed. The update process has the following return codes: 0 - The update was successfully completed. 1 - An invalid IP address was given for the specified Telnet connection. 2 - There was a socket error when attempting to start a Telnet session. 3 - An invalid response was received from the Telnet session. 4 - An invalid login name or password was specified for the Telnet session. 5 - An invalid IP address was given for the management module. 6 - There was a socket error when attempting to connect to the management module. 7 - There was an unknown error when attempting to connect to the management module. 8 - The encryption keys returned from the management module are invalid. 9 - An invalid login name or password was specified for the management module. 10 - An invalid response was received from the management module. 11 - The limit of three retries was exceeded when sending a command to the management module. 12 - An unknown command type for the management module was specified. 13 - The length of the management module command and the response do not match. 14 - The command sent and the command received from the management module do not match. 15 - There was an error sending data to the management module. 16 - An invalid slot number for the BladeCenter chassis was specified. 17 - An invalid code level to query was specified. 18 - The specified management module packet file was not found. 19 - An invalid packet file was specified. 20 - The packet file contains an invalid header. 21 - The TFTP download timed out. 22 - The TFTP server was not found. 23 - The connection with the TFTP server was lost. 24 - TFTP server IP address is invalid. 25 - Connection to the I/O module failed. 26 - An update image file was not found. 27 - The image file is invalid. -1 - General update failure. 7.0 LIMITATIONS --------------- 7.1 BladeScanner in "scan" mode requires MM firmware version 53C or higher ------------------------------------------------------------------------------ The BladeScanner utility running in "scan" mode (-s) requires Management Module firmware version 53C or higher. If the management module firmware is less than 53C, the BladeScanner utility will return this error message: ERROR 523: Unable to collect BladeCenter chassis model type information. Note: On some Linux systems this error message does not properly reset the terminal. To restore the terminal you will need to issue the "reset" command. The suggested solution is to run BladeScanner in "edit" mode (-e), to fill in the appropriate fields manually, and then run ChassisUpdate.py to update the BladeCenter components. Similarly, if for any reason BladeScanner fails to run in "scan" mode, run BladeScanner in "edit" mode and manually complete the fields. 7.2 Management modules ---------------------- If there are redundant management modules and the IP addresses are obtained through DHCP, it is not possible to update the management modules if the existing firmware version is earlier than version 57K. Depending on the code levels detected the management module may restart during the update process. It is not possible to downlevel the firmware of the management modules via the UXBC tool. In environments where IBM Director is being run, it is possible that Director will connect to the management module's administrative port (6090) when a global Director scan is initiated. This could potentially impact the ability to connect to the management module with the UXBC tool. If so, ensure that the management module's username and password are NOT set to the manufacturer defaults. Changing the username and password of the management module and rebooting should resolve this issue. It is not possible to run the BladeScanner utility in "Scan" mode (-s) if the management module firmware version is earlier than version 53C. The suggested solution is to run BladeScanner in "Edit" mode (-e), to fill in the appropriate fields manually, and then run ChassisUpdate.py to update the BladeCenter components. This solution is also suggested for any other limitations experienced while running the BladeScanner utility in "Scan" mode. 7.3 IBM Ethernet Switch Module configuration -------------------------------------------- ESM switch configuration settings can be reset when updating from a firmware version earlier than .081 (version 1.04) to a firmware version at or later than .081. Link aggregation settings are lost during this firmware update and are reset to the default values. If link aggregation settings or port trunking are configured to be different default settings, do not use UXBC, unless you can manually reconfigure the switch afterward. In a small percentage of cases the UXBC tool may not be able to confirm that the firmware update for the ESM switch completed. In this case the BladeCenterUpdates.log file will have a warning stating that "Update completion could not be verified". In every test that was conducted where the UXBC tool was not able to verify that the flashing completed, the ESM switch had successfullybeen updated. However, you should manually verify that the ESM switch is at the correct version. 7.4 Multiple instances of ChassisUpdate --------------------------------------- Running multiple instances of the ChassisUpdate script to more than one BladeCenter chassis at a time from an administrative system can produce undesireable results and is not supported. 7.5 Cross-Platform Issues -------------------------- When copying a response file from one platform to another (i.e. Windows to Linux or vice versa), it is recommended that the bladescanner tool for the target platform be run in edit mode, and the non-TFTP File Location and Blade Updates Location options under the File Options menu be updated to reflect the proper paths for that particular platform. 7.6 gnome-terminal Issues -------------------------- gnome-terminal does not always clear or redraw the screen correctly when using bladescanner application. If you experience a problem use a different terminal program such as xterm. 7.7 remoteux and Reiser FS on xSeries systems --------------------------------------------- remoteux uses PowerQuest Virtual Boot Environment (PQ-VBE) to remotely update firmware on xSeries systems. PQ-VBE does not support Reiser FS, which means that the remote directory (-r) specified in remoteux must be a non Reiser FS, such as FAT32, or Ext2 or Ext3. This is not a limitation on JS20 Blades, because the update process on JS20 does not use PQ-VBE. This means that the UXBC tool cannot be used to update Linux Blades that are only using Reiser FS. 7.8 remoteux requires compat-libstdc++-7.2-2.95.3.77 ---------------------------------------------------- Remoteux requires that compat-libstdc++-7.2-2.95.3.77 module is installed on both the Administrative system and the Target system when running RHEL 3.0, SLES 8 and SLES 9. If this compatability module is not installed you will get a return code of 127 in the /uxlog/ux.log file on the target system. The log entry will look similar to: Tue Jan 18 21:47:57 EST 2005, Schedule Update=RemoteUX , New=, Status=Failed, ReturnCode=127 The /uxlog/output.log file will complain about the current standard c++ libraries and will contain messages similar to the following: ./vfile: error while loading shared libraries: libstdc++-libc6.2-2.so.3: \ cannot open shared object file: No such file or directory ./vfile: error while loading shared libraries: libstdc++-libc6.2-2.so.3: \ cannot open shared object file: No such file or directory vdinstlx: error while loading shared libraries: libstdc++-libc6.2-2.so.3: \ cannot open shared object file: No such file or directory 7.9 Firmware updates on JS20 forces a reboot -------------------------------------------- Updating the CEC on the JS20 forces a reboot of the Target system. 7.10 Do not change media tray when remotely updating Linux Blades ---------------------------------------------------------------- Do not change media tray (CD and Floppy) selection when remotely updating xSeries Linux Blades with remoteux. If a Linux Blade boots with the media tray selected, then the media must remain selected when remotely updating the Blade. Similarily, if the media tray was not selected at boot time it must remain unselected when remotely updating the Blade. Changing the media tray will prevent the update running and will produce error 24. The /uxlog/ux.log file will contain an error similar to : Tue Jan 18 21:39:28 EST 2005, Schedule Update=RemoteUX , New=, Status=Failed, ReturnCode=24 The /uxlog/output.log file will contain an error similar to: Processing file /tmp/vfrmbtlx/VDisk.vfd Using PQEngine to get file cluster list FileSize = 98304000 Unable to get engine cluster list for file /tmp/vfrmbtlx/VDisk.vfd. [DeleteVolumeExtentList] Destroying extent entry 0 Error: Unable to generate sector map for file '/tmp/vfrmbtlx/VDisk.vfd'. 7.11 remoteux does not update the Broadcom firmware on the JS20 --------------------------------------------------------------- Remoteux for Linux does not update the Broadcom firmware on the JS20. It just updates the CEC and the QLogic firmware. For this reason the UXBC tool cannot be used to update that component. 7.12 remoteux requires Perl on the target systems ------------------------------------------------ Remoteux for Linux requires Perl is installed on the target system. 7.13 remoteux does not the Broadcom firmware on the BladeCenter(8843) Blade --------------------------------------------------------------------------- RemoteUX does not update the Broadcom firmware on the BladeCenter(8843) Blade, because of this the UXBC tool cannot be used to update that component. 8.0 Web Sites and Support -------------------------- 8.1 IBM Support Web Site: http://www.pc.ibm.com/support 8.2 IBM Support Web Site with link to downloads and drivers: http://www-307.ibm.com/pc/support/site.wss/ 9.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. The following terms are trademarks of the IBM Corporation in the United States, other countries, or both: the e-business logo BladeCenter eServer IBM ServerProven xSeries Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Red Hat, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. 10.0 Disclaimer ---------------- 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.