HP Smart Update Best Practices Implementer Guide

them to plan and implement any changes needed to support the new SIM version control
infrastructure. In most cases, the only change needed will be to remove the Version Control
Agent from the servers after validating the new SIM version control infrastructure 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 at http://www.hp.com/go/hpsum/documentation.
5 How can I leverage the HP SUM pull-from-web functionality when my data center cannot be
connected to the Internet for security reasons?
In this case, the only way to leverage the functionality is to execute HP SUM from a workstation
that is dual-homed on a network with Internet access and to a management 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 pulls updates through the network connected to the Internet and deploys
them on the management network.
6 Does the HP SUM CLI allow creation of a group from a file with a list of IP addresses or DNS
names when the file is presented as a file name that is given as a CLI command-line parameter?
HP SUM can accept an input file for the IP addresses and user credentials. The use current
credentials option can be used with the CLI for Windows only (it’s not clear text across the
network) as current credentials are not available for Linux users. For more information on how
to use this in your firmware deployments, see “HP SUM special considerations” (page 26).
7 What is the purpose of the dryrun scripting option?
Its primary purpose is to test scripts called from the CLI approach to HP SUM. The dryrun feature
in HP SUM is activated by using the /dryrun or --dryrun switch, which causes HP SUM to
bypass the actual calling of the firmware smart components during installation and return
SUCCESS. This mode is useful for validating when the targets are available, that credentials
are valid, and that all of the network interfaces and ports are available for a successful firmware
deployment.
NOTE: HP SUM 6.x does not support the DRYRUN option.
8 When using the HP SPP to upgrade an entire c7000 Enclosure and all of its constituents, including
the OAs, server blades, iLOs, and switch modules:
• Can I simply give the HP SUM tool the OA IP address?
• Is the tool able to upgrade all of the components inside the chassis because the OA can
automatically identify the addresses of the iLOs and modules?
• Do I have to manually add IP addresses of the blades, 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 server firmware in online mode. HP SUM updates the OA through the OA
interface, not through the NIC interface. The HP SPP and HP Integrity bundles provide the
firmware versions that you use to update the server firmware.
You need to provide the IP address or DNS name for G7 and earlier targets that you want to
update. HP SUM detects the OA host servers list on targets, and if you added servers to the OA
host servers list, HP SUM will ask if you want to add the target.
If you are using a Gen8 server that is running AMS, you do not need to provide an IP address.
36 FAQs