IBM eServer BladeCenter HS40 Firmware Flash Disk Version 1.44, Build ID: SBJT44A Installation README File System Supported: 8839 CONTENTS ________ 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 Disclaimer 1.0 Overview 1.1 This README file contains the latest information about installing the IBM eServer BladeCenter HS40 Firmware. 1.2 Limitations - NA 1.3 Enhancements - NA 1.4 Level of Recommendations and Prerequisites for the Update: - This update is recommended. 1.5 Dependencies 2.0 Change History Version 1.11 - March 19, 2004 ---------------------- - Initial release Version 1.23 - April 28, 2004 ---------------------- - Fixes added to correct NIC ordering/enumeration - Fixed problem associated with system restarting following a remote shutdown request using Remote Deployment Manager - Changes to enable serial ports with SOL enabled Version 1.32 - June 24, 2004 ---------------------- - Fixed problem with wrong BIOS default boot sequence being displayed when IDE harddrive is installed - Fixed problem with network boot option not being displayed in BIOS boot sequence after loading defaults - Fixed problem with MAC address in MM web interface does not match MAC address displayed in BIOS menus Version 1.44 - August 11, 2004 ---------------------- - Fixed problems associated with Remote Deployment Manager - Enhanced error detection algorithm for processors 3.0 Installation and Setup Instructions *Note: If installing from an update package, see additional instructions, in Appendix A. The procedure to update the POST/BIOS is as follows: Note: Before starting, insure you have both BIOS diskettes 1 and 2 3.1 Insert the "IBM eServer BladeCenter HS40 POST/BIOS Flash Disk1" into drive A. 3.2 Start up or restart your IBM eServer BladeCenter HS40 server. 3.3 The system will boot off of the disk and present a window which allows you the option to flash various options. Choose "1 - Update POST/BIOS". 3.4 You will be prompted "Enter file name:" Type 'SBX44.001' 3.5 You will be asked if you would like to move the current POST/BIOS image to the backup ROM location. If you select 'Yes', the current code will be flashed in to the backup bank immediately. 3.6 You will be shown the current Serial Number of the blade and provided an option to change it. Select 'Yes' to change, select 'No' to continue the flash update. 3.7 You will be shown the current Machine Type/Model of the blade and provided an option to change it. Select 'Yes' to change, Select 'No' to continue the flash update. 3.8 If the current system POST/BIOS supports the Asset Tag feature, you will be asked if you would like to change it. If you select 'Yes', you will be able to enter a new number. 3.9 You will then be asked if you would like to save the current code to a disk. If you select 'Yes', you need to have a formatted disk already available, or specify a fully qualified path and file name. 3.10 Next you will be prompted "Update POST/BIOS". Enter 'Yes' to proceed with the flash update. 3.11 At this point, the image will be loaded from disk1 and the system will start to update the flash ROM with the new code. This is a 2 disk process. When disk1 has completed you will see the message "Press any key when this file "SBX44.002" is in the drive. 3.12 Insert "IBM eServer BladeCenter HS40 POST/BIOS Flash Disk2" into drive A. Press any key to continue. When this is completed the following message is displayed, "Request completed successfully" "OK" Press 'Enter' to continue. 3.13 You will be prompted "Would you like to Reboot". Select 'Yes' to restart your blade. 4.0 Configuration Information 5.0 Web Sites and Support Phone Number 5.1 IBM Support Web Site: http://www.pc.ibm.com/support 5.2 IBM Marketing Web Site: http://www.pc.ibm.com/ww/eserver/xseries/ 5.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QLY.html. 6.0 Trademarks and Notices 6.1 IBM and the e(logo) are registered trademarks of International Business Machines Corporation. 6.2 U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. IBM web site pages may contain other proprietary notices and copyright information which should be observed. 7.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.  Appendix A: Package Specific Installation Instruction This update is packaged as a self-extracting PackageForTheWeb (PFTW) executable file. To unpack, this update requires that your TEMP environment variable be set to a path with read/write access. You must be logged in as an administrator. The package update log, ux.log, is created on the system drive. To locate the log file go to: %SystemDrive%\uxlog\ux.log The command-line syntax for PackageForTheWeb firmware update package is: Package.exe [-s] [-a [-s] | [-r] | [-c] | [-x directory] | [-xd] | [-w] | [-?] ] [-s] This command installs the Package-For-The-Web software silently and does not prompt if files are to be over-written in the %temp% directory. [-a] This command passes all subsequent commands to the PFTW software to install the update package. [-s] This command runs a silent and unattended update. For firmware updates, the update is scheduled to run on the next reboot. An immediate reboot can be forced with the -r option. [-r] This command schedules the update and reboot immediately. It can be used with or without the -s command. [-c] This command cancels any scheduled firmware update and records results of this operation in the log file. Only one firmware package can be scheduled at a time, if a firmware update needs to be applied instead of the currently scheduled firmware update package, cancel the current (run with the -c option on any firmware package) package. Then, run the applicable firmware package. [-x directory] This command is used with firmware updates to extract the update to the directory named directory. The PackageForTheWeb executable extracts itself to a subdirectory in the %TEMP% directory, a relative directory will be relative to that location. You must specify an absolute directory if you do not want to use the default directory. [-xd] This command is used with firmware updates to extract to a floppy diskette. The floppy diskette can then be used to boot from and apply the update. This option is not available for all firmware updates, such as tape drive and hard-disk drive updates. [-w] PowerQuest Virtual Boot Environment requires that there are 2 free sectors on the first track before it can schedule a firmware update. Use this option only if scheduling an update failed because 2 free sectors were not available on the first track. This option clears the non-boot and the non-partition information sectors on the first track. Typically, these sectors are not used. Before clearing the sectors a copy of the complete first track is saved in the %temp% directory from which the update runs. [-?] This command displays information about the command line switches. The command line switches -s, -r -c and -e are unnattended. Other command line options such as display help (-?) might require that you hit any key to continue. If Windows packages are run without any command line options, a GUI is displayed. This GUI offers all of the options that are available using the command line.