HP BladeSystem Firmware Deployment Tool User Guide Part Number 572124-001 October 2009 (First Edition)
© Copyright 2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software.
Contents Introduction .................................................................................................................................. 4 Overview ................................................................................................................................................. 4 Obtaining the Firmware Deployment Tool..................................................................................................... 5 Using the Firmware Deployment Tool ......................
Introduction Overview HP BladeSystem Firmware Deployment Tool is an ISO image containing a collection of HP Smart Update Manager (HP SUM) and firmware smart components that have been tested together to ensure compatibility. The tool is designed for users who do not have an installed operating system on their blades or who want an unattended, automated method of deploying firmware in an offline environment.
Obtaining the Firmware Deployment Tool The BladeSystem Firmware Deployment Tool can be downloaded from the HP BladeSystem Firmware Maintenance website (http://www.hp.com/go/bladesystemupdates).
Using the Firmware Deployment Tool Updating the firmware on a server Updating an individual server locally To update an individual server using the FDT, use the c-Class SUV cable. This cable connects to the front of a blade and allows a USB CD or DVD drive to connect to a server. In this local installation, the FDT ISO image must be burned to a physical CD and placed in the USB CD or DVD drive.
NOTE: Do not close the virtual media web page, or it might disconnect the ISO image. 9. Return to the iLO2 web page. 10. Click the Power Management tab. 11. Using the Momentary Press button, power up the server. NOTE: If the server is powered up, click the Momentary Press button to shut down the server, and then click the Momentary Press button again to power it back up. 12. Click OK when prompted to power up the server. 13.
11. o If the UID light is off, the update process is complete and the server OS can be installed or the server restarted to its previous operating system. o If the UID light is on solid, a firmware update failure has occurred. You must either plug in the KVM dongle or use iLO Remote Console support to browse into the affected server to determine the cause of failure. The FDT loads the error log into a vi editor window for review.
Updating multiple enclosures simultaneously RIBCL scripts RIBCL enables you to write XML scripts to configure and manage iLO 2 configuration settings, user accounts, directory settings, server settings, and HP Systems Insight Manager SSO settings. You can create your own scripts using RIBCL. IMPORTANT: To run RIBCL scripts, you must have the iLO Advanced license. To run the RIBCL scripts, ensure that the following prerequisites are met: 1. Apply the latest Windows PSPs to the local host. 2.
contains two lines, one of which has been commented out. Comment in or out the line for the desired mode of operation. After you have flashed the server blades, you can use the BB2.sh script to disconnect the Virtual Media by passing it the Eject_Virtual_Media.xml file as the RIBCL script to execute or Eject_Virtual_Media.sh script based on the state of the commented out lines.
then echo "removing ${TMP}/${hostfile}" rm -f ${TMP}/${hostfile} fi echo Retrieving Blade ips from OA # # get list of iLO ips in enclosure from OA # #/usr/bin/ssh $user@$host "show server list"|grep OK |awk '{print $3}' >> ${TMP}/${hostfile} # or do /usr/bin/ssh $user@$host "show server list"|grep OK >> ${TMP}/${hostfile} # # The for loop will loop thru the results of the above command. # You can then invoke a RIBCL script on each ip via a wrapper shell script.
• If the UID light is solid, a firmware update failure has occurred. You must either plug in the KVM dongle or use iLO Remote Console support to browse into the affected server to determine the cause of failure. The FDT loads the error log into a vi editor window for review. HP recommends resolving the issue before installing or restarting the operating system. For more information on how to handle various firmware update failure scenarios, see the Troubleshooting (on page 13) section.
Troubleshooting Troubleshooting issues • If a failure occurs, use the console keyword at the boot prompt to drop into a debug console. To manually execute the HP BladeSystem Firmware Deployment Tool, run ./hpsum -s. • Before using the ISO, validate the MD5 checksum against the value on the download page to ensure a good image has been downloaded correctly. • Servers with equal or greater than 64 GB if memory might stop responding while booting SmartStart 8.25 or earlier, Firmware Maintenance CD 8.
Technical support Reference documentation To download the ProLiant Firmware Maintenance and other CDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads). For general information on management products, refer to the ProLiant Essentials website (http://www.hp.com/servers/proliantessentials).
Acronyms and abbreviations FDT Firmware Deployment Tool ISO International Organization for Standardization KVM keyboard, video, and mouse NIC network interface controller OA Onboard Administrator OS operating system POST Power-On Self Test PSP ProLiant Support Pack RIBCL Remote Insight Board Command Language ROM read-only memory SAS serial attached SCSI SATA serial ATA Acronyms and abbreviations 15
SSO single sign-on SUV serial, USB, video UID unit identification VM Virtual Machine XML extensible markup language Acronyms and abbreviations 16
