HP Smart Update Best Practices Implementer Guide
Creating a custom baseline in HP SUM
HP SUM 5.3.0 and later includes a function that allows you to easily create a baseline of
components from your update repositories. You can create baselines based on operating system,
node, and update criticality. This allows you to create a new update baseline that includes only
updates for a specific server, or set of servers. For more information on using HP SUM to create
a baseline, see the HP Smart Update Manager User Guide.
Miscellaneous BladeSystem firmware-related questions
This section contains questions directly related to blade firmware updates.
1 Can HP SIM use the HP SPP as a VCRM custom baseline?
Yes, it can be used by dropping the downloaded and expanded bundle into the VCRM directory
and running a rescan on this directory from the HP Systems Management Homepage for the
VCRM. For information on additional support for the HP SIM 7.0 release, see HP SIM and
Version Control Agent.
NOTE: VCRM 7.0.0 and later is required to support the HP SPP.
2 What is the recommended tool for determining the currently-deployed BladeSystem enclosure
firmware versions?
Using HP SUM 5.1.0 or later, you can generate either an HTML or XML report file detailing
the repository contents, target firmware, target installable details, and failed dependencies.
You can view both files in a web browser, such as Microsoft Internet Explorer. The reports
support JavaScript-enabled web browsers Internet Explorer 6.0 or Mozilla Firefox 3.5 and
later. The XML reports also allow you to write programs to pull the report information and
display it in other locations.
NOTE: Not all reports are available on all GUI screens. If a report is not available, HP SUM
grays out the report option.
3 What are the dependencies between the SPP firmware and drivers?
System software (for example, drivers and services) dependencies for firmware updates are
very generic in that a driver needs to be loaded so the device can be discovered, version
checked, and so on.
4 Can we upgrade each component directly to the latest version or do we need intermediate
revision steps?
Almost all components can be upgraded to the latest firmware revision without issue. The only
component that requires an interim revision is for OA firmware updates from 1.x firmware
revisions to 2.x versions. For more information, see the following support documents:
• Customer Advisory: HP OA - Upgrading Firmware From Version 1.x to Version 2.25 (or
Later) Will Not Be Successful
http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c01597033
• Link to earlier versions of the OA firmware:
www.hp.com/go/oa
NOTE: If updating from a version older than the 4.6.16.0 version of the Broadcom 1 Gb
NIC driver, it is first necessary to update to the 4.6.16.0 version before continuing to later
versions. More information about this can be obtained from the customer advisory on the
advisory website at http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/
?docId=emr_na-c01684544.
5 Can I update my Blades HBA and CNA firmware online?
Creating a custom baseline in HP SUM 37