HP Integrity Superdome 2 16-socket Instruction Manual

HP Smart Update Manager Release Notes
Version 6.0.1
HP Part Number: 679985-007b
Published: October 2013
Edition: 2

© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P.
Open source software
•OpenPegasus version 2.10.0
For more information, see the OpenPegasus website at http://www.OpenPegasus.org.
•Mongoose version 2.11
For more information, see the Mongoose website at http://sourceforge.net/projects/mongoose/develop.
•open-WSMan
For more information, see the open-WSMan website at http://sourceforge.net/projects/openwsman.
•zlib version 1.2.3
For more information, see the zlib website at http://zlib.net.
•libcurl version 7.21.6
For more information, see the libcurl website at http://curl.haxx.se/libcurl.
•gSOAP version 2.8.3
For more information, see the gSOAP website at http://gsoap2.sourceforge.net.
•libssh2 version 1.2.8
For more information, see the libssh2 website at http://www.libssh2.org.
•libxml2 version 2.7.8
For more information, see the libxml2 website at http://www.xmlsoft.org.
•libxslt version 1.1.26
For more information, see the libxslt website at http://www.xmlsoft.org.
•OpenSSL version 1.0.0d
For more information, see the OpenSSL website at http://www.openssl.org
•Cygwin libraries
For more information, see http://cygwin.com/index.html.
•Genisoimage
For more information, see http://cdrkit.org/.

Version
6.0.1
Description
HP SUM is a technology that installs and updates firmware and software on HP ProLiant servers, and
firmware on HP Integrity servers.
HP SUM provides a web-based GUI and a command-line scriptable interface for:
•Deployment of firmware for single or one-to-many HP ProLiant and HP Integrity servers and
network-based targets such as iLO, OA, and VC Ethernet and Fibre Channel modules.
•Deployment of software for single or one-to-many HP ProLiant servers (supported in Windows and
Linux environments).
NOTE: HP SUM can update some firmware for VMware vSphere 5.x and later.
The latest version of HP SUM is available on the HP website at http://www.hp.com/go/hpsum.
Operating systems and devices
Prerequisites
IMPORTANT: Before deploying any components to a system, be sure that a recent backup of the
system is available in the event the deployment procedure fails.
Enable the network ports that HP SUM uses. For more information, see “Network ports used by HP
SUM” (page 5).
Prerequisites for using Linux root credentials
•If you have run HP SUM as a root user, remove the temp directory created by HP SUM.
•Make sure you have read/write access permissions to the /tmp and /var directories.
•If you create a sudo user, make sure that you add that user to the /etc/sudoers file. The
following table shows the privileges and specifications for users.
SpecificationPrivilegeUser
ALLALL= (ALL)Root
ALLALL= (ALL)Sudo_user
•Edit the entry in the /etc/sudoers file so the system asks for the sudo user password instead
of root user password when you run the sudo command.
The following table shows the privileges to comment or remove from /etc/sudoers.
SpecificationPrivilegeUser
ALLALL= (ALL)All
This often occurs in SUSE Linux systems.
Description 3

#Defaults targetpw # ask for the password of the target user. For example,
WARNING! Only use this option with Defaults targetpw.
•To use super user functionality, configure the user as a super user with all root privileges. You
can also use non-root user with a root user to update components.
HP SUM deployment
HP-UX5 VMware ESXi/vSphere4 Linux4 Windows4
HP SUM
runs
on/Deploys
to
SoftwareFirmwareSoftwareFirmwareSoftwareFirmwareSoftwareFirmware
N/AYes2,3 N/AYes1 YesYesYesYesWindows
N/AYes2,3 N/AYes1 YesYesN/AN/ALinux
N/AN/AN/AYesN/AYesN/AYesOffline SPP
1. VMware ESXi 5.0 and later
2. I/O via online HP-UX
3. Platform firmware via iLO
4. HP ProLiant nodes running a supported OS version
5. HP Integrity nodes running HP-UX
NOTE: You can update non-supported operating systems offline. Refer to documentation for
confirmation.
VMware ESXi operating systems
You can update servers running VMware vSphere 5.1 or later operating systems remotely while running
HP SUM on a Linux or Windows system. HP SUM only supports updating firmware for VMware nodes.
Firmware that HP releases is available in the HP SPP. For information on the recommended driver and
firmware versions for HP ProLiant servers running VMware vSphere 5, see the VMware firmware and
software recipe available on the HP Online Depot website at http://vibsdepot.hp.com/. For more
information on the firmware updates available in the HP SPP, see the HP Service Pack for ProLiant
Release Notes.
VMware firmware
The following must be true to update a VMware vSphere node:
•The node must be running VMware vSphere 5 or later.
•The node must be active on the network so HP SUM can detect it.
•You are executing HP SUM on a Windows or Linux host computer.
4 Operating systems and devices

NOTE: You cannot execute HP SUM locally to update a VMware vSphere node.
•The VMware server must be running hp-smx-provider-500.03.01.2–434156 or later. Download
the providers for the appropriate version of VMware vSphere release from one of the following
locations:
◦Version 1.3.5 and later of the HP Insight Management WBEM Provider offline bundle. You
can download the bundle from the HP Online Depot at http://vibsdepot.hp.com.
◦The provider is included in version 5.25 and later of the HP Custom Image. You can download
the HP Custom Image ISO from the Custom VMware Image for HP ProLiant Servers website
at http://www.hp.com/go/esxidownload.
Supported bundles
•HP SPP – The minimum HP SPP version is 2012.10.0
•HP Integrity bundles – HP SUM 6.0.1 supports all currently released HP Integrity bundles
Supported browsers
•Internet Explorer version 9 or later
•Firefox version 17 ESR or later
•Chrome version 24 or later
•Screen resolution of 1024 x 768
Network ports used by HP SUM
HP SUM requires that certain network ports are available for proper operation. If you lock down
network ports, make sure that the ports listed in the network port tables are open so that HP SUM
works correctly when connecting to remote node servers and hosts. If you are unable to unlock these
network ports, the only option is to run HP SUM locally and update network-based hosts, such as the
OA, iLO, and VC modules, through their web interfaces.
Updates for most node types require network traffic in both directions between the server running HP
SUM and the node. The server running HP SUM creates a local HTTP server, which is used to serve
firmware binaries to the node and to communicate node status. The remote node issues HTTP requests
and posts status updates to the server running HP SUM during the update process. If there is a routing
problem or firewall blocking traffic back from the remote node to the system running HP SUM, firmware
updates might be blocked, status updates blocked or delayed, or both.
Table 1 HP SUM Windows network ports
DescriptionPorts
Establishes a connection to a remote node via SSH to perform node inventory.Port 22
A secure data port used to transfer information.Port 443
Connects to the remote ADMIN$ share on node servers. These are the standard
ports Windows servers use to connect to the remote file shares. If you can connect
Ports 445 and 137/138/139 (Port 137
is used only if you are using NetBIOS
naming service.) remotely to a remote Windows file share on the node server, you have the correct
ports open.
Default for some internal communications. This port listens on the remote side if
there is no conflict. If a conflict occurs, the next available port is used.
Port 62286
Updates are passed to the node and retrieved through an internal secure web
server that uses the first available port in the range of 63001-63002. This allows
Ports 63001–63002
iLO and VC firmware updates without having to access the host server. It also
allows the servers to run VMware or other virtualization platforms to update the
Operating systems and devices 5

Table 1 HP SUM Windows network ports (continued)
DescriptionPorts
iLO firmware without requiring a server reboot or a migration of the virtual
machines to other servers.
Remote HP Integrity iLO and Superdome 2 updates require these ports to be
open on systems for network traffic in both directions to transfer firmware files.
You can use these FTP ports to perform switch updates.Ports 21 or 63006–63010
Table 2 HP SUM Linux network ports
DescriptionPorts
Establishes a connection to a remote node via SSH to perform node inventory.Port 22
A secure data port used to transfer information.Port 443
Default for some internal communications. This port listens on the remote side if there
is no conflict. If a conflict occurs, the next available port is used.
Port 62286
Updates are passed to the node and retrieved through an internal secure web server
that uses the first available port in the range of 63001-63002. This support allows
Ports 63001–63002
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 servers.
Remote HP Integrity iLO and Superdome 2 updates require these ports to be open on
systems for network traffic in both directions to transfer firmware files.
You can use these FTP ports to perform switch updates.Ports 21 or 63006–63010
NOTE: HP SUM 6.x supports /port and /ssl_port options. This allows you to use ports other
than 63001 and 63005. Use these options to avoid conflicts with firewalls.
Special network configuration note for HP Integrity servers
HP Integrity servers have management network and production interfaces. These are usually kept on
separate subnets in an installation. To perform full remote administration of the server, access is required
for both networks. If you keep both networks isolated, you need to perform management and operating
systems tasks separately.
Enhancements
The following enhancements are included in this version of HP SUM:
•Added a confirmation message on the Automatic Localhost Guided Update describing what
happens when you click Deploy.
•Indicated required values on the Create Custom Baseline screen with a *.
•Remove the Download from hp.com option from the Add Baseline screen. A future version of HP
SUM will include this function.
•Added support for fully-qualified DNS names.
•Added support for Red Hat Enterprise Linux 5.10.
•Added support for VMware vSphere 5.5.
6 Enhancements

GUI changes
Description6.0.1 term6.0.0 term
More accurately describes what you can
update using the Localhost Guided
Update.
Localhost Guided UpdateGuided Update
On the Localhost Guided Update
interactive screen and the Add Node
Start OverReset
screen, this button has been renamed to
better describe what this button does.
This change is on the Add Node, Edit
Node, Inventory, and other screens
Baseline to ApplyBaseline
where you can select a baseline to apply
to a node.
This change describes that the
deployment will not take place
Review/DeployDeploy
immediately. You can review the updates
that HP SUM will deploy before
beginning deployment.
On the Add Baseline screen, this label
has been changed to better describe the
location where you can find a baseline.
Browse LocallyHP SUM Default Location
Changed report name in the Report
Center interface. The report filename has
not changed.
Last Deploy DetailsInstalled Details
Changed report name in the Report
Center interface. The report filename has
not changed.
Deploy PreviewInstallable details
Fixes
The following fixes are in this version of HP SUM:
•HP supports deploying components over an IPv6 network
•HP SUM deploys components successfully to remote nodes running a Linux operating system
•HP SUM reports contain information for remote nodes.
•You can set the Custom Baseline version in supported browsers on the Custom Baseline screen.
•You can log into HP SUM and access existing data if HP SUM logs out a user due to timing out
on Windows hosts.
•Using HP SUM in Japanese environments allow you to log in without an error.
•HP SUM supports more than 13 nodes from an input file in CLI mode.
•HP SUM supports the USEWMI parameter when Windows and Linux nodes are included in an
input file.
•HP SUM provides informative error messages when a VMware provider is not present.
Fixes 7

Downloading HP SUM
You can download HP SUM from the HP website or from the HP Software Delivery Repository.
Downloading HP SUM from the HP website
1. Launch a web browser.
2. Go to http://www.hp.com/go/hpsum/download.
3. Click on the file that you want to download:
NOTE: These downloads do not include software or firmware. Software and/or firmware can
be obtained from the HP Service Pack for ProLiant, Integrity Firmware Bundles, or download the
latest components from hp.com using HP SUM baseline functionality.
•◦HP Smart Update Manager ISO - The HP SUM ISO contains HP SUM and a bootable
ISO environment. Firmware and Software components can be added to create a
customized baseline.
◦HP Smart Update Manager RPM - The HP SUM RPM is a native package for Linux and
is also available on the Linux http://www.hp.com/go/sdr.
◦HP Smart Update Manager zip - The HP SUM zip contains the files for running HP SUM
on supported Windows and Linux operating systems.
NOTE: Linux file permissions for script and binary files must be modified to add execute
mode.
Downloading HP SUM from the SDR website
You can download HP SUM as an RPM from the HP Software Delivery Repository at http://
downloads.linux.hp.com/. The SDR contains a version of the HP SUM RPM for each supported operating
system and architecture type.
You can use yum commands to search for HP SUM and download it to your system. You can also use
a web browser to navigate the HP SDR and download the rpm.
Use the following commands to search, download, or install HP SUM from the SDR:
Command exampleAction
yum search hpsumSearch for HP SUM with yum
yum install hpsumInstall HP SUM with yum
rpm -Uvh hpsum-5.3.5-66.rhwl5.i386.rpmDownload HP SUM from the SDR with a web browser, and
then install the RPM.
For more information on using the HP SDR, see the Getting Started and FAQ sections on the HP
Software Delivery Repository website at http://downloads.linux.hp.com/SDR/index.html.
For more information on using HP SUM with the SDR, see Linux best practices using HP Service Pack
for ProLiant (SPP) and Software Delivery Repository (SDR) at http://h20000.www2.hp.com/bc/docs/
support/SupportManual/c03479393/c03479393.pdf.
Installation instructions
There are two methods for using HP SUM on your systems:
•Online mode: Runs HP SUM on a Windows or Linux operating system.
8 Downloading HP SUM

Launching HP SUM in online mode
1. Mount the ISO on your host.
2. Open Start.html, found in the root directory of the ISO, in a supported browser.
3. Follow the directory on the screen.
•Offline mode: Runs HP SUM from the Linux kernel included in the ISO. Offline mode includes two
modes:
◦Automatic mode: Firmware components are installed without your interaction. Automatic
mode will begin by default 30 seconds after you install a DVD or USB key with the ISO
burned on it.
NOTE: Booting the HP SUM ISO from iLO virtual media is only supported in Automatic
mode. If you try to use interactive mode, you might experience performance issues.
◦Interactive mode: Use the GUI to update components.
Initiating interactive mode
1. Open Start.html, found at the root of the ISO, in a supported browser.
2. Follow the instructions on the screen.
Migrating nodes from HP SUM 5.x to HP SUM 6.0.1
HP provides scripts that migrate the targets you added to HP SUM 5.x into nodes that HP SUM 6.0.1
recognizes. If you want to edit the targets that you migrate to HP SUM 6.0.1, use the /script
parameter. This generates a file that you can edit with a text editor application.
NOTE: The migration script does not support sudo credentials.
To migrate nodes to HP SUM 6.0.1:
1. Navigate to the directory that holds HP SUM.
2. Double-click port_targets.bat (Windows) or port_targets.sh (Linux).
You can also run the scripts from the command line.
Script syntax:
port_targets.bat [/y] [/h] [/script] [/user {username} /password {password}
The script supports the following options:
DefinitionOption
Continue the migration without using prompts./y
Print the script help./h
This option creates a file with the migration commands, it
does not run the script. You can edit the script commands
manually before migrating the targets.
NOTE: Use this option to select the targets you migrate, or
edit the user credentials for an individual target.
/script
This options sets a default username and password credentials
for each node that HP SUM migrates. If you do not use this
option, each node is given the following credentials:
/user {username} /password {password}
•user=username
•password=passwd
Migrating nodes from HP SUM 5.x to HP SUM 6.0.1 9

Issues and suggested actions
The following are known issues and limitations with HP SUM. For a full list of troubleshooting items
see the HP Smart Update Manager User Guide
HP SUM does not display the download from hp.com button
This version of HP SUM does not support downloading updates from hp.com to add a baseline to the
baseline library. HP SUM will include this function in a future version.
Suggested Action: Download the updates, place them in a directory, and then add the directory as a
baseline in HP SUM.
The /use_web legacy CLI command does not work
Suggested Action: No action. This is a known issue. This version of HP SUM does not support this
command.
HP SUM 6.0.1 does not display nodes or baselines that HP SUM 6.0.0 displayed
Suggested Action: If you ran HP SUM 6.0.0 and added nodes and baselines, manually add the nodes
and baselines to HP SUM 6.0.1. If you ran the port_targets script to migrate HP SUM 5.x nodes
to HP SUM 6.0.0, run the HP SUM 6.0.1 port_targets script to migrate the nodes from HP SUM
5.x. For more information, see “Migrating nodes from HP SUM 5.x to HP SUM 6.0.1” (page 9).
Viewing logs after deploying updates in offline mode
Suggested Action: Run gatherlogs in the HP SUM directory function from a write-able directory.
HP SUM might not display scroll bars or buttons correctly
Suggested Action: Set your screen resolution to 1024 x 768.
HP SUM does not work properly in Internet Explorer 8
Suggested Action: Use Internet Explorer 9 and later.
HP SUM engine stops running when HP SUM is mounted from a virtual media source
Suggested Action: Do not mount a virtual media source through iLO and perform an update of iLO
firmware. A known issue causes the iLO to restart and causes HP SUM to stop working.
Some screens are not translated from English
Suggested Action: No action. This is a known issue that will be fixed in a future version.
HP SUM does not deploy multiple components in legacy CLI mode when listed separately
in one command
Suggested Action: Copy the components into a directory and use the /use_location command. If
you are deploying more than ten components, use the work around.
HP SUM does not build source RPMs
Suggested Action: Build the source RPM outside of HP SUM and then add the RPM to a baseline. After
HP SUM performs inventory on the baseline, it can deploy the RPM. This is how HP SUM designed to
work.
10 Issues and suggested actions

HP SUM legacy CLI documentation includes incorrect information about the
/oa_username attribute
Suggested Action: Use the /oa_username and /oa_password attributes even if the OA and VC
use the same credentials.
This argument provides the user name credential for OA
associated with VC specified with the target command-line
/oa_username
parameter. Only one set of OA credentials can be specified
with command-line parameters. You can add multiple VC
nodes to command-line parameters with the target
parameter only if the credentials of OAs associated with
specified VCs are the same. You do not need to provide an
OA network address associated with VC. HP SUM queries
it from a specified VC node.
To update multiple VCs with different user names and
passwords, or VCs with OAs that have different credentials,
use the corresponding input files OAUID and OAPWD.
Provides the password credential for OA associated with VC
specified with the "node" command-line parameter. Only
/oa_password
one set of OA credentials can be specified with command-line
parameters. You can add multiple VC nodes to command-line
parameters with the "node" parameter only if the credentials
of OAs associated with specified VCs are the same. You do
not need to provide an OA network address associated with
VC. HP SUM queries it from a specified VC node.
To update multiple VCs with different user names and
passwords, or VCs with OAs that have different credentials,
use the corresponding input files OAUID and OAPWD .
HP SUM legacy CLI documentation includes incorrect information about the /dryrun
attribute
Suggested Action: HP SUM legacy CLI mode supports the /dryrun parameter. The documentation
will be corrected for a future release.
HP SUM stops responding when finding nodes using the Find Nodes function
Suggested Action: Do not enter an IP Start Address that is higher than the IP End Address.
You cannot close the HP SUM report windows or online help in offline mode
Suggested Action: Do not view reports or use the online help in offline mode. If you want to view
reports, view them outside of offline mode. If you information on using HP SUM, please see the HP
Smart Update Manager User Guide on the HP website at http://www.hp.com/support/
HP_SUM_UG_en. This is a known issue that will be fixed in a future version.
iPDU node components do not display the Force option
Suggested Action: HP SUM does not support downgrading or rewriting components for an iPDU node.
HP SUM does not respond when you update an iPDU node in legacy CLI mode
Suggested Action: Update iPDU nodes in GUI mode. This is a known issue that will be resolved in a
future version of HP SUM.
HP SUM does not generate reports for QLogic Fibre Channel switch
Suggested Action: There is no work around for this. This is a known issue that will be resolved in a
future version of HP SUM.
Issues and suggested actions 11

HP SUM does not display the Force button for components to be updated on nodes
running Red Hat Enterprise Linux 5.10
Suggested Action: The work around for this issue is to manually reinstall the RPM outside of HP SUM.
This issue will be fixed in a future version of HP SUM.
HP SUM displays “Update returned an error” when deploying the HP Fibre Channel
Enablement Kit for Linux
Suggested Action: View the update log. If you see the error Enablement kit is not supported
for the installed driver version, use the following instructions to work around this issue:
1. Install HBA drivers before installing the Enablement kit.
2. Make sure the driver and Enablement kit version match.
This known issue will be resolved in a future version of HP SUM.
HP SUM displays the error “Unable to start hpsumservice service on node” when it tries
to access a remote node
Suggested Action: Due to network security settings, HP SUM cannot start the HP SUM engine on the
remote node. Run HP SUM locally on the node.
HP SUM cannot create a session on a remote node
Suggested Action: Do not use special characters in passwords on remote nodes. This issue will be
resolved in a future version of HP SUM.
HP SUM stops working when it deploys updates to a Cisco switch
Suggested Action: There is no work around. This issue will be resolved in a future version of HP SUM.
HP SUM input file mode does not apply the LOCALACCESS-ENABLED and
LOCALACCESS-TYPE configuration parameters to System Management Homepage
Suggested Action: Use HP SUM in GUI mode to configure SMH components.
HP SUM requires minimum versions of VC and OA to support HP Integrity nodes
Suggested Action: Verify that HP Integrity i2 OA versions are 3.30 and VC version 3.6, and HP Integrity
i4 servers are OA version 3.60 and VC version 3.70.
HP SUM displays the iLO firmware version as 0.0.0 for Linux nodes
Suggested Action: Make sure that the CHIF driver is installed so HP SUM can detect the correct iLO
firmware version. This applies to iLO2, iLO3, and iLO4.
Documentation feedback
HP is committed to providing 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.
12 Documentation feedback