HP Smart Update Best Practices Planning Guide

NOTE: For more information about comparing supported HBA driver versions and HP storage
devices, see the HP Single Point of Connectivity Knowledge (SPOCK) website at http://
www.hp.com/storage/spock.
◦ If the VC firmware is earlier than 1.34, update the VC, the OA, and then the blades.
◦ If the VC firmware is 1.34 or later:
Without an operating system, the installation order is blade infrastructure (for example,
OA or VC), and then blades (offline).
–
– With an operating system, update the OA, blades (offline or online), and then the
VC.
◦ With VC firmware greater than 3.00, you must install OA firmware 3.00 first.
◦ HP Integrity BL8x0 i2 blades require OA firmware greater than 3.00.
• Ensure that the NIC firmware included in a release set is supported by the operating system
vendor and external network switch vendors before updating. Review the following known
issues:
◦ A purple screen (PSOD) occurs on some 10GbE adapters. For more information, see the
customer advisory website at
http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c02496982
◦ Updating Broadcom 1GbE drivers for Windows Servers requires first updating to version
4.6.16.0. For more information, see the customer advisory website at
http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c01684544
◦ Emulex be2net Inbox Driver version 4.0.88.0 does not support Flex-10 or Flex Fabric
Adapters. For more information, see the customer advisory website at
http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c03005737
Performing the update best practices
1. Download HP SPP or the Integrity bundle. For more information, see “Downloading the HP
SPP” (page 23) or “Downloading Integrity bundles” (page 24).
NOTE: HP SUM supports updating firmware only for VMware ESXi targets.
2. Gather information about the servers and targets you want to update.
a. Gather IP addresses for the OA, Virtual Connect Manager, iLO, and at least one NIC in
each server.
b. For all VC modules, run the VCSU health check to determine if the VC modules are in a
good health state that allows firmware updates to proceed before updating any OA or
VC modules.
c. Run HP SUM with the /report and /firmware_report options using the gathered
OA, Virtual Connect Manager, iLO, and server IP addresses to build a report that shows
what is currently installed on the targeted devices, and the updates you need to perform.
The report does not generate information for offline targets or components. With HP SUM
5.0.0, you can generate the reports in the HP SUM GUI.
Best practices quick review 9