HP ProLiant BL660c HP ProLiant and Integrity Firmware Management Best Practice
HP ProLiant BL660c Manual
View all HP ProLiant BL660c manuals
Add to My Manuals
Save this manual to your list of manuals |
HP ProLiant BL660c manual content summary:
- HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 1
HP ProLiant and Integrity Firmware Management Best Practices Implementer Guide Abstract This document describes the best practices for performing a firmware and software update for your server environment. This document is intended for individuals who perform updates and understand the configuration - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 2
L.P. Confidential computer software. Valid license from HP required for possession, use or copying. 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 - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 3
5 HP firmware overview...5 Explanation of guides...5 2 Firmware deployment scenarios 7 3 Deploying firmware 8 Deployment modes...8 Updating firmware overview...8 Downloading the updates...9 Installation scenarios...9 Updating one or more servers in a single location 9 Updating firmware enclosures - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 4
connection errors 47 Collecting trace directories...48 Troubleshooting failed iLO firmware updates 49 7 Support and other resources 51 Information to collect before contacting HP 51 How to contact HP...51 Subscription service...51 Related information...51 Typographic conventions...52 - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 5
components in your environment. HP firmware overview When updating HP servers, you might need to update the following firmware: • OA firmware • VC firmware • Blade server, Integrity BL8xxc i2/rx28xx i2/Superdome 2, and ProLiant ML/DL/SL server system ROM • Blade server, Integrity BL8xxc i2/rx28xx - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 6
You can find these guides on the HP Smart Update Manager Information Library at http:// www.hp.com/go/hpsum/documentation. 6 Introduction - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 7
the OA firmware using • HP SPP • HP Integrity Smart Update Firmware bundles Recommended deployment tool: • HP SUM • Use the OA web interface (HP ProLiant servers only) Updating the VC firmware using • HP SPP • HP Integrity Smart Update Firmware bundles Updating enclosures or blades that have - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 8
ProLiant and Integrity Firmware Management Best Practices Planning Guide, available on the HP Smart Update Manager Information Library at http://www.hp.com/go/hpsum/documentation. 7. Update one server or your lab environment or test server. Allow this to run for 72 hours to verify that no problems - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 9
your servers (HP ProLiant servers only). For more information, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. 10. Verify that all updates installed correctly. Use the Gather Logs utility after exiting HP SUM. 11. If needed, troubleshoot problems. Downloading the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 10
Use HP SUM to generate a report of the current firmware. Use this as a record of what you installed. If there are problems after generated earlier to determine what you updated. Updating firmware for distributed corporate environments 1. Download your updates. For more information, see "Downloading - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 11
update the server separately. • Use PXE boot to move the HP SPP over the network. Updating firmware for large enterprises If the targets are in a c-Class enclosure, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. To download the guide, see the HP SUM Information - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 12
to use OA and VC versions supported by both ProLiant and Integrity servers. For more information, see the HP BladeSystem Release Sets for Mixed ProLiant and Integrity website at http://h18004.www1.hp.com/products/servers/firmware/ mixed-release-sets.html. 2. Download the latest HP SPP version and - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 13
case the firmware update fails. • Always reboot the server after server-based driver or firmware upgrades. This allows the server to activate new firmware. 5. Run HP SPP to perform your updates. For more information, see the HP Service Pack for ProLiant User Guide, available on the HP Smart Update - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 14
the SUV cable attached to the physical blade that you want to update, if the blade server supports the SUV cable connection. For Windows, use a USB key. For more information, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. For more information on creating a USB - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 15
location to begin the update. For more information, see "Using HP SUM" (page 21). Updating firmware offline (HP ProLiant servers only) 1. Download the HP SPP. For more information, see "Downloading the updates" (page 9). 2. To extract the HP SPP ISO image, open Windows Explorer, double-click on the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 16
SPP ISO to a USB key. For more information about creating a USB key, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. 4. Begin the update using HP SUM. For more information, see "Using HP SUM" (page 21). Ensure the target device IP address or DNS name is in the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 17
module 1.31 or earlier. • Install a valid HP VC firmware package. Download the firmware from the HP VC firmware website at http://h18004.www1.hp.com/products/blades/components/ethernet/vcem/ index.html. Click Download software, and then log in to the HP Passport website. • Do not close the console - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 18
the VCEM to manage your VC domains, you must place them in Maintenance mode or Firmware Mode before using the VCSU utility. 4. Download the HP SPP. For more information, see "Downloading the updates" (page 9). 5. To extract the HP SPP ISO, double-click the spp..zip file and extract the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 19
scenario uses HP SPP through HP SUM to update the OA firmware, the VCSU to update the VC firmware, and the HP SPP to update all server blade firmware. For information on the correct order for updating OA and VC firmware, see "OA Installation order" (page 34). NOTE: The following instructions focus - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 20
TFTP within XINETD. • Change disable=yes to disable=no in /etc/xinet.d/tftp • Restart XINETD 4. Set up the PXE server to use a static IP: a. Create the file /etc/sysconfig/network-scripts/ifcfg-eth0.static b. Set the contents to the , a file name would be 01-00-01-02-03-04-05. 20 Deploying firmware - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 21
options and their usage see Using HP SUM in Scripted or Silent Mode in the HP Smart Update Manager User Guide. Input files HP SUM provides the ability to script the update of multiple, individual targets or groups of targets (HP ProLiant and Integrity servers and options) within a single operation - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 22
use the SILENT=YES option causes the GUI mode to be used, but the information provided enables the scripts are working without deploying the firmware updates that might be required on each HP Smart Update Manager User Guide, available on the HP Smart Update Manager Information Library at http://www.hp - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 23
in hpsum_execution_log__.raw. HP SUM special considerations Disabling BitLocker to permit firmware updates The TPM, when used with any remote server selected as a target, for some newer models of ProLiant servers, HP SUM utilities for HP iLO, Smart Array, NIC, and BIOS warn users prior - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 24
firmware update process. This requires setting the /tpmbypass parameter for HP SUM or the firmware update is blocked. To temporarily disable BitLocker support to allow firmware and any firmware updated must be applied to the server. No warning appears. A new log file is generated (%systemdrive%\ - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 25
web service. NOTE: For security reasons, HP does not recommend changing the main port from port 443. Table 3 HP server uses first available port in the range of 60000-63005. This support allows updates of the iLO and VC firmware without the need to access the host server. It also allows the servers - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 26
Deploy→Deploy Drivers, Firmware and Agents→Install Software and Firmware. Using VMware ESXi 5.0 and later Use the following instructions to enable VMware ESXi 5.0 and later on servers to work with HP SUM 5.1.0 and later. NOTE: Currently, VMware ESXi 5.0 and later only supports generating reports - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 27
the links to select your server model. 4. Click View and download all available drivers, software, and firmware for this product. 5. Verify that the correct server model is selected, and then click on the link. 6. Click VMware ESXi 5.0. 7. Click the Download button for the HP ESXi Offline Bundle for - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 28
version>.vib Example: esxcli software vib install -v hp-smx-provider-500.02.10.70.51-434156.vib 14. Type reboot to reboot the server to enable the WBEM Providers. 15. Launch the VSphere Client, and then log into the server to deploy the updates to the server you want to update. 28 Deploying firmware - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 29
the VMware documentation. Using Onboard Adminstrator (HP ProLiant servers only) Use the following instructions to update an HP Blade System enclosure through the OA. Updating servers in a c-Class enclosure using HP SUM 1. Download the HP SPP. For more information, see "Downloading the updates" (page - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 30
to update an OA using EFM: • OA 3.50 or later, and HP ProLiant G5 or later servers blades. • Disable TPM. IMPORTANT: After you begin an EFM update, you have to allow the update to finish. NOTE: EFM updates support OA modules reported as BladeSystem c7000 DDR2 Onboard Administrator with KVM OA - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 31
. The server does not need to be rebooted to activate the iLO firmware. iLO firmware can be updated in either online or offline mode. NIC firmware To update NIC firmware, use the HP SPP or HP Integrity Smart Update Firmware bundle. The corresponding operating system-specific NIC driver must be - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 32
you do not use iLO 2 firmware 1.70 on any blade server. For G6 servers that support Power Management Controller updates, use version 3.4 (D). For G7 servers, use version 1.6 or 1.7, depending on the server model. Download both versions of the driver, and HP SUM will automatically choose the correct - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 33
the HP Smart Update Firmware DVD 9.20. NOTE: Gen8 servers require HP SUM 5.1.0 or later. • The HP SPP, or HP SPP-related hot fixes, and HP Integrity bundles provide non-Smart Array controller components that HP SUM supports. Tape firmware Load an appropriate driver for the controller the Tape Blade - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 34
ProLiant Gen8 servers require OA firmware 3.50 or later, and VC firmware 3.51 or later. • HP Integrity servers require OA firmware 3.11 or later and VC firmware 3.15 or later. NOTE: If you have installed HP SPP 2012.01.0 or later, you can update Fibre Channel HBA and CNA firmware online in supported - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 35
mode, rescan the VC module in HP SUM and continue with the update. IMPORTANT: If the VC configuration is not redundant or if the VC firmware version is earlier than version 1.34, a network fabric downtime of up to 10 minutes can occur while the firmware is being activated. This affects all servers - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 36
following table lists the firmware types and known driver dependencies. Table 5 Driver dependency considerations Firmware types System ROM iLO 2 firmware Known driver dependencies For ProLiant G7 servers, starting with versions released in May 2011, and all ProLiant Gen8 servers, you must have the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 37
5.0 earlier than 5.3. The hp_ilo RPM must also be used for SUSE Linux Enterprise Server 10. Broadcom NIC firmware Power PIC firmware Windows One of the following drivers must be installed and running for Broadcom NIC firmware to be updated in Windows. • Any version of one of the following Windows - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 38
newer Smart Array controllers. The version listed is the minimum needed to support firmware updates. The driver listed will need to be matched to the type of Smart Array or SATA controller in the server. The drivers provided by the Linux distributions can also be used in place of the RPM if desired - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 39
VCSU. HP releases firmware updates as part of the HP SPP and HP Integrity Smart Update Firmware bundles 2 Why must I always upgrade to the latest individual firmware and driver components? • HP SPP You do not have to update your server environment with every HP SPP release. HP supports the HP SPP - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 40
works in their environment. VCRM servers can still be leveraged, but are not required to support this new version control infrastructure. 4 Where do I obtain the HP Smart Update Manager User Guide? You can find the HP Smart Update Manager User Guide on the HP Smart Update Manager Information Library - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 41
in effect, the enclosure and all of its contents? • Must I always manually add the host OS IP address that upgrades the blade server BIOS because the OA cannot identify what it is? HP SUM updates all server firmware in online mode. HP SUM updates the OA through the OA interface, not through the NIC - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 42
the latest updates. 11 How does the firmware version affect our support status with HP? Typically, HP supports each SPP version for 12 months. In some cases, HP may extend the support period beyond a year, so always consult the HP Service Pack for ProLiant Release Notes. For more information, see - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 43
Key 1. Insert a USB key containing the SPP ISO image created. If the blade server supports the SUV cable, use the HP USB Key Creator for Windows utility in the SUV cable attached to the blade that is selected for update. 2. For Windows, download the HP USB Key Creator for Windows utility from the - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 44
in the CD mount point and the USB mount point to move the Firmware CD files to the USB key. ./usbcreator.sh /cd_mount_point /usbkey 10. the /hp/swpackages (Linux) or the \hp\swpackages (Windows) directory and HP SUM picks them up automatically if the HP SUM version being used can support the type - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 45
6 Troubleshooting Troubleshooting HP SUM When using HP SUM, the logs files are located at the following locations: • Windows (for both firmware and drivers): %SYSTEMDRIVE%\cpqsystem\hp\log\\hpsum_detail_log.txt • Linux: /var/hp/log//hpsum_detail_log.txt NOTE: If you run HP - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 46
image, use the following settings for the new firewall rules on your system. 10. Click OK to ensure new firewall rules have been implemented. 46 Troubleshooting - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 47
connection errors Use these tips to troubleshoot HP SUM connection errors: • Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP address. If it does, it prevents HP SUM from connecting to the remote server's share because Windows only allows one - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 48
problems. For more information, see "Collecting trace directories" (page 48). • Ensure the server has a valid serial number. Collecting trace directories HP SUM generates . Provides general settings information of HP SUM such as Force downgrade or upgrade for specific target. 48 Troubleshooting - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 49
USB Key, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. 4. After the first blade server. When too many servers request the maxed-out value, the OA becomes over-allocated and prevents some blades from powering up. Even after Troubleshooting failed iLO firmware - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 50
Enable System Maintenance Mode. 8. Re-insert blade into enclosure. 9. Allow blade to power up, and start HP SPP to flash the iLO firmware. 10. Power-off the blade after the firmware updates are complete. 11. Remove blade from enclosure. 12. Disable System Maintenance Mode on your server. 13. Remove - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 51
of product enhancements, new driver versions, firmware updates, and other product resources. Related information Documents http://www.hp.com/go/spp/documentation • HP Service Pack for ProLiant Release Notes • HP Service Pack for ProLiant Server Support Guide Information to collect before contacting - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 52
Installation and User Guide ◦ HP Systems Insight Manager Help Guide • HP Insight Control Management Software http://www.hp.com/servers/rdp • HP ProLiant server operating system support matrices http://www.hp.com/go/supportos • HP Modular Smart Arrays support matrix website http://www.hp.com/go/msa - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 53
bodily harm or death. CAUTION: Indicates that failure to follow directions could result in damage to equipment or data. IMPORTANT: Provides clarifying information or specific instructions. NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. Typographic conventions 53 - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 54
documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback ([email protected]). Include the document title and part number, version number, or the URL when submitting your feedback. 54 Documentation feedback - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 55
Firmware Management host bus adapter HP Systems Insight Manager Integrated Lights-Out International Organization for Standardization keyboard, video, monitor Modular Smart Array non-volatile random access memory Simple Object Access Protocol HP Service Pack for ProLiant serial, USB, video - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 56
, 9 Firmware updates multiple enclosures, 19 OA, 19 scripted installation, 19 VC, 19 H help obtaining, 51 HP 56 Index technical support, 51 HP SIM using for updates, 26 HP SUM execution modes, 21 minimum requirements, 21 HP SUM and HP SPP updating OA enclosure, 29 I Implementation steps, 12 driver - HP ProLiant BL660c | HP ProLiant and Integrity Firmware Management Best Practice - Page 57
setup, 19 R related documentation, 51 S Scenarios Firmware deployment, 7 installation, 9 Scripted installation firmware updates, 19 Server(s) in single location updating, 9 symbols in text, 53 T technical support HP, 51 text symbols, 53 TPM (Trusted Platform Module) Trusted Platform Module, 24
HP ProLiant and Integrity Firmware
Management Best Practices Implementer
Guide
Abstract
This document describes the best practices for performing a firmware and software update for your server environment. This
document is intended for individuals who perform updates and understand the configuration and operations of Microsoft
Windows, Windows Server, Linux, smart components, and the risk of data loss from performing updates.
HP Part Number: 613178-002
Published: June 2012
Edition: 2