HP ProLiant DL388e HP ProLiant and Integrity Firmware Management Best Practice
HP ProLiant DL388e Manual
View all HP ProLiant DL388e manuals
Add to My Manuals
Save this manual to your list of manuals |
HP ProLiant DL388e manual content summary:
- HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 1
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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 2
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. Acknowledgments Microsoft®, Windows®, Windows® XP, Windows Vista®, and Windows NT® are - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 3
the HP WBEM Providers to single servers with VMware ESXi 5.0 and later 27 Deploying the HP WBEM Providers to single servers with a VSphere Client 28 Deploying the HP WBEM Providers to multiple servers concurrently 29 Using Onboard Adminstrator (HP ProLiant servers only 29 Updating servers in - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 4
a USB Key...43 Using a hard drive...44 6 Troubleshooting 45 Troubleshooting HP SUM...45 HP SUM fails on Windows hosts due to McAfee firewalls 45 Troubleshooting connection errors 47 Collecting trace directories...48 Troubleshooting failed iLO firmware updates 49 7 Support and other resources 51 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 5
i2/rx28xx i2/Superdome 2, and ProLiant ML/DL/SL server iLO firmware • Broadcom, Intel, Mellanox and QLogic NIC firmware • Smart Array Controller firmware • SAS and SATA hard drive firmware • Emulex, QLogic, and Brocade Fibre Channel HBA and CNA firmware • Tape blade firmware • HP 3Gb and 6Gb SAS BL - HP ProLiant DL388e | 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 7
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 an operating system using • HP SPP • HP Integrity Smart Update Firmware bundles Recommended deployment tool: • VCSU - HP ProLiant DL388e | 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 9
to 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 10
enclosure if you cannot update all servers at once. Even if you need to perform partial updates, maintain the installation order. 5. Perform the update. 6. Review the results and log files from the update to ensure the updates completed correctly. 7. Use HP SUM to generate a report of the current - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 11
all servers. • For ProLiant G7 servers and earlier, use the SmartStart Scripting Toolkit. For ProLiant Gen8 servers, use the Scripting Toolkit. • Install updates on each server individually across a network. • Copy the HP SPP to one computer at the remote location using a network share (Windows) or - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 12
For ProLiant G7 servers and earlier, use the HP SmartStart Scripting Toolkit. For ProLiant Gen8 servers, use the HP Scripting Toolkit. • Script deployment of firmware using HP SUM, Microsoft SCCM in Windows, and YUM or the HP Software Delivery Repository for Linux. • Copy the HP SPP, or HP Integrity - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 13
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 Manager Information Library at http:// www.hp.com - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 14
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 key, see "Adding components to the HP SPP" (page 43). iLO - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 15
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 ZIP file, and then copy the ISO image to a directory on a USB key or network hard drive. For - HP ProLiant DL388e | 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 17
to update VC firmware: • Install Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7 on the client. • Upload Administrative or Power User privileges on the client system to install and run the utility when upgrading from VC 4 Gb FC module 1.31 or earlier. • Install a valid HP VC - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 18
again. 4. Enter Yes when ready to update the VC firmware. NOTE: VC firmware updates can take from approximately 10 minutes to as long as one hour, depending on the number and type of modules in the enclosure. Do not restart modules or close the window while the update process is in progress, or the - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 19
in the BladeSystem infrastructure at once; updates require a multi-step process. 1. Download the HP SPP. For more information, see "Downloading the updates" (page 9). 2. Set up either Microsoft IIS or Apache web servers. 3. Install OpenSSH (Windows only), and generate the SSH keys needed to automate - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 20
Install the following packages: • tftp-server • dhcp • httpd • syslinux 2. Set up a DNS server on your network. 3. Activate TFTP within XINETD. • Change disable=yes to disable=no in /etc/xinet.d/tftp • Restart XINETD 4. Set up the PXE server world readable. 6. Configure PXELINUX a. Create directory - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 21
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 through the input file functionality. To protect your credentials - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 22
installations to ensure the scripts are working without deploying the firmware updates HP Smart Update Manager User Guide, available on the HP Smart Update Manager Information Library at http://www.hp section consists of a number of settings and their values. Each configuration setting must appear - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 23
Windows file system if the user cannot provide the recovery key. HP SUM detects if a TPM is enabled in your system. If a TPM is detected in your system or 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 24
BitLocker support to allow firmware updates: 1. Click Start, and then search for gpedit.msc in the Search Text box. 2. When the Local Group Policy Editor starts, click Local Computer Policy. 3. Click Computer Configuration→Administrative Templates→Windows Components→BitLocker Drive Encryption - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 25
or port 63006, if it is not. This support allows iLO and VC firmware updates without having to access the host server. It also allows servers running VMware or other virtualization platforms to update their iLO without having to reboot their server or to migrate their virtual machines to other - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 26
to update. 16. Click 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 27
8. Unzip the bundle contents to a local hard drive. Deploying the HP WBEM Providers to single servers with VMware ESXi 5.0 and later 1. On the VMware server, press F2, and then log in to the server. 2. Click Troubleshooting Options and then enable SSH support. 3. On the local workstation where you - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 28
On the local workstation where you extracted the bundle contents, use SSH to connect to the VMware server (SSH ). NOTE: For Windows servers, use Putty or another terminal emulation program that provides SSH support. 8. Use SCP to copy the contents of the extracted bundle to the /var/log - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 29
. For more information VMware scripts, see 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 30
you time. The following are requirements 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 31
rebooting the server during a later maintenance window. System ROM firmware can be updated in either online or offline mode. For a list of System ROM driver dependencies, see "Driver dependency considerations" (page 36). iLO firmware iLO firmware is activated immediately upon update of the iLO by an - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 32
have installed HP SPP 2012.01.0 or later, you can update FC HBA and CNA firmware online in supported Windows and Linux environments. Power Management Controller firmware Power Management Controller firmware controls the power subsystem of the HP servers. This firmware has a number of dependencies - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 33
Any version of the driver meets the requirements to update the SAS or SATA hard drive firmware. NOTE: Gen8 servers require HP SUM 5.1.0 and later. Behind a non-Smart Array controller requirements • Use HP SUM 4.1.0 or later. HP added support for SAS and SATA hard drive firmware located behind a non - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 34
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 Windows - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 35
to force downgrade VC firmware. • Update single module-HP SUM does not allow you update only a single module. • Non-redundant configuration-If HP SUM detects that the VC module is non-redundant, it will not allow you to perform any updates. This prevents an accidental server outage. • Not part of - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 36
versions released in May 2011, and all ProLiant Gen8 servers, you must have the iLO driver. You use the iLO driver to flash the ROM. See the drivers for the type of iLO in your server to determine the correct version of the iLO driver to use. Windows: • iLO 2 firmware 1.78 or later • CpqCiDrv.sys - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 37
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 drivers. • q57xp32.sys • bxvbdx.sys • nxp2nic - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 38
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 controller in the server. SAS and SATA hard drive Windows • hpcisss2.sys driver 5.8.0.0 or later • bchtsw32.sys (any version) • lsi_sas.sys (any - HP ProLiant DL388e | 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 40
network. HP SUM can be executed on a Windows XP, Vista, or Windows 7 workstation. The HP SUM remote deployment capabilities can update remote servers, OAs, VC modules, and iLOs. When leveraging the workstation, none of the servers are connected directly to the Internet. In this configuration, HP SUM - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 41
, iLOs, modules, and so on, into the HP SUM GUI interface, thereby creating my own group, which is, 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 42
manually, it will not be included as part of the latest HP SPP or HP Integrity bundle. 10 How often should we upgrade firmware? Update your ProLiant firmware once per year to keep your firmware up-to-date with the latest updates. 11 How does the firmware version affect our support status with HP - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 43
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 website and install it on a workstation. Once - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 44
a directory on the hard drive in the location where HP SUM will be executed. 2. Ensure execute privileges are available in Linux by using the chmod 700 * command. By default, the files are copied off the DVD in Linux as read-only with no execution privileges. 3. Copy any updated files into the same - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 45
trace logs of its installation that can be used to debug problems. These trace files are located in the following places: • Windows Server 2003/Vista/7: %TEMP%\hp_sum\ • Windows Server 2008: %TEMP%\\hp_sum normally the is "1." • Linux: /tmp/hp_sum HP SUM creates a separate trace - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 46
bottom of the screen, click Add (Add new rule). 9. From the screen 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 47
is part of the administrator's or Linux root equivalent group. If it is not, HP SUM blocks installation to the target. • Ensure WMI is enabled and running on all Windows target servers. • For Windows target servers, enter the user name in DOMAIN\USER format, where is the administrative user - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 48
trace directories for connection problems. For more information, see "Collecting trace directories" (page 48). • Ensure the server has a valid serial number. Collecting trace directories HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems. These files - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 49
security override switch is set to disabled. 3. Boot the USB drive key containing the iLO flash component. NOTE: For more information on creating a USB Key, see the HP ProLiant and Integrity Firmware Management Best Practices Planning Guide. 4. After the first screen displays, switch to text console - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 50
. NOTE: Resetting the iLO causes all iLO settings to reset to defaults. After following this set of instructions, it is necessary to reset their iLO configuration settings, after updating the iLO firmware to the latest version if the user has changed the iLO default settings. 50 Troubleshooting - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 51
email notification 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 52
http://www.hp.com/go/hpsim ◦ HP Systems Insight Manager 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 - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 53
in 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 DL388e | 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 DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 55
HP Service Pack for ProLiant serial, USB, video Trusted Platform Module unit identification light universal serial bus Virtual Connect Version Control Agent Version Control Repository Manager Virtual Connect Support Utility Virtual Machine Virtual SAS Manager Web Based Enterprise Management Windows - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 56
, 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 deployment, 12 offline automatic mode - HP ProLiant DL388e | HP ProLiant and Integrity Firmware Management Best Practice - Page 57
PXE server 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
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