Deploying ProLiant Support Packs in Windows
Minimum requirements for Windows servers
Overview of Firmware Maintenance CD
Firmware Maintenance CD deployment
options
Firmware Maintenance CD and Windows PSPs powered by HP Smart Update Manager
Graphical deployment on a local host
Scripted deployment on a local host
Deployment to multiple remote hosts
First time selecting an installation host
First time selecting bundles to filter
First time selecting components to install
Using the GUI: local host installations
Selecting an installation host
Selecting components to install
Viewing the installation results
Using the GUI: multiple-host installations
Selecting remote hosts or groups
Selecting bundles to filter on multiple hosts
Selecting components to install on multiple hosts
Viewing the installation results for multiple hosts
Advanced installation of PSPs in
Windows
Deploying firmware and software simultaneously
Recovering from a failed ROM upgrade
Recovering from a loss of Linux remote functionality
Troubleshooting installation of the PSP for Microsoft Windows
In this section |
Beginning with the ProLiant Support Pack for Microsoft® Windows® version 7.90 or later, the HP Smart Update Manager utility enables you to deploy PSP software and firmware components from a single, easy-to-use interface. This utility enables legacy support of existing software and firmware components while simplifying the overall deployment process. It is no longer necessary to run the SETUP executable files (SETUPC.EXE, SETUPEX.EXE, and SETUP.EXE), the HP Smart Update Manager utility now provides this functionality. The utility also provides installation logic and version control that automatically check for dependencies, installing only the correct updates for optimal configuration.
|
NOTE: The PSP contains numerous files. All files must be present in the same directory as the HPSUM.EXE program for the PSP to be properly installed. |
Beginning with the ProLiant Support Pack for Microsoft® Windows® version 7.90 or later, users can now deploy firmware and software components simultaneously. For more information about this new feature, see "Deploying firmware and software simultaneously".
|
IMPORTANT: Before deploying software updates on a host server, be sure that a recent backup of the host server is available in the event the deployment procedure fails. |
|
NOTE: For a current list of supported operating systems, refer to the PSP website (http://www.hp.com/servers/psp). |
For successful component deployments on Microsoft® Windows® hosts, the following minimum requirements must be met:
· A local administrative system running a supported Microsoft® Windows® operating system must be available.
· One or more remote host servers running a supported Microsoft® Windows® operating system in need of a software upgrade must be available. If the local administrative system (local host) is the only server that requires an upgrade, remote host servers are not necessary.
· At least 256 MB of memory must be available on the local administrative system running a supported Windows® operating system.
· Sufficient hard-drive space, which is generally at least twice the file size of the components to be deployed.
· All remote host servers must be connected to the same network and use TCP/IP to enable the systems to be seen by the administrative system.
· There must be an account with administrator privileges on each host server. HP recommends that the user name and password for the administrator account on each host server are the same as those on the local administrative system. If administrator privileges are not set up in this way, you must have the user name and password for each remote server available. Alternatively, you can use a domain account on the local administrative system that has administrator privileges on the host servers.
· The beginning and ending IP addresses entered for the range of hosts must both be on the same subnet.
In this section |
Beginning with the Firmware CD 7.50, the Firmware Maintenance CD uses the HP Smart Update Manager utility to deploy firmware components from a single, easy-to-use interface that is supported in both Windows® and Linux environments. This utility enables legacy support of existing firmware components while simplifying the firmware deployment process. It also provides installation logic and version control that automatically checks for dependencies, installing only the correct updates for optimal system configuration.
|
CAUTION: The HP Smart Update Manager utility and the firmware components should be used only by individuals who are experienced and knowledgeable in their use. Before using HP Smart Update Manager to update firmware, be sure to back up the target server and take all other necessary precautions so that mission-critical systems are not disrupted if a failure occurs. |
With the HP Smart Update Manager, the host and group information are stored from session to session. The username, password, and current credentials are not stored within a session or from session to session.
To successfully deploy HP Smart Update Manager on target systems based on Microsoft® Windows®, the following must be available:
· A local administrative system with 256 MB of memory, running a supported Windows® operating system.
· Sufficient hard-drive space—As a standard practice, sufficient hard-drive space equals at least twice the file size of the components to be deployed.
To successfully deploy HP Smart Update Manager on target systems based on Linux, the following must be available:
· A local administrative system with 256 MB of memory, running a supported Linux operating system
· glibc 2.2.4-26 or later
· gawk 3.1.0-3 or later
· sed 3.02-10 or later
· pciutils-2.1.8-25.i386.rpm or later
To successfully update HP Smart Update manager on remote target systems based on Linux, the following must be available:
· tcl-8.x package
· tcl-5.x package
· expect-5.x package
|
IMPORTANT: The HP Smart Update Manager does not support cross-platform deployments (for example, deployments from Linux systems to Windows® systems). |
You can deploy the HP Smart Update Manager and firmware components online or offline.
· When performing an online deployment, you must boot the server from the operating system. The HP Smart Update Manager supports online deployments of all ROM flash components for both Windows® and Linux, including system, hard-drive (SAS only), array-controller, Lights-Out Management ROM flash components, NIC firmware, and HP Onboard Administrator for HP c-Class BladeSystem.
|
NOTE: The Onboard Administrator firmware is only supported in online deployments. |
· When performing an offline deployment, you can boot the server from the Firmware Maintenance CD or a USB drive key that contains the Firmware Maintenance CD contents. The HP Smart Update Manager supports offline deployments of all ROM flash components including system, hard-drive, array-controller, and Lights-Out Management ROM flash components. When performing an offline deployment, you can also access a removable device that contains supplemental updates.
|
NOTE: You can add firmware components to the USB drive key in the /compaq/swpackages directory. |
To deploy components in an online manner:
1. Insert the Firmware Maintenance CD or USB drive key. If you use the Firmware Maintenance CD, the Firmware Maintenance CD interface opens automatically. If you use a USB drive key, you must start the interface manually. Open a command-line interface and type one of the following commands to access the Firmware Maintenance CD:
o In Windows®:
\_autorun\autorun_win
o In Linux:
/autorun
2. Read the End-User License Agreement. If you agree to the terms of the license agreement, click Agree to continue. The Firmware Maintenance CD interface is displayed.
3. Click the Firmware Update tab.
4. Click Install Firmware. The HP Smart Update Manager is initiated.
5. Select and install the desired components. See "Using the GUI: local host installations " or"Using the GUI: multiple-host installations " for more information.
To deploy components in an offline manner:
1. Boot the server from the Firmware Maintenance CD or a USB drive key.
2. At the prompt, select a language and keyboard.
3. Click Continue.
4. Read the End-User License Agreement. If you agree to the terms of the license agreement, click Agree to continue. The Firmware Maintenance CD interface is displayed.
5. Click the Firmware Update tab.
6. Click Install Firmware. The HP Smart Update Manager is initiated.
7. Select and install the desired components. See "Using the GUI: local host installations " or "Using the GUI:
multiple-host installations " for more information.
In this section |
HP Smart Update Manager deploys firmware and software smart components on a local host or one or more remote hosts. The remote hosts must be online and running the same operating system as the system running HP Smart Update Manager such as when the remote hosts are running Linux, the HP Smart Update Manager should also be running on a Linux system. HP Smart Update Manager supports the following operating systems:
· Microsoft® Windows Server™ 2003 and Microsoft® Windows Server™ 2003 x64 (firmware and software components)
· Red Hat Enterprise Linux 3, 4, and 5, and SUSE Linux Enterprise Server 9 and 10 x86 and AMD64/EM64T (firmware components only)
The following table describes typical HP Smart Update Manager deployment scenarios.
Scenario |
Description |
Graphical deployment on a local host |
Use this scenario when you: · Are not familiar with command line tools · Are deploying components on a local, single-host · Do not require scripting |
Scripted deployment on a local host |
Use this scenario when you: · Are familiar with command line tools · Are deploying components on a local, single-host · Must perform a customized, scripted deployment |
Graphical deployment to a remote host |
Use this scenario when you: · Are not familiar with command line tools · Are deploying components on one or more remote hosts · Do not require scripting |
Scripted deployment to a remote host |
Use this scenario when you: · Are familiar with command line tools · Are deploying components on one or more hosts · Must perform a customized, scripted deployment to one or more host systems |
The easiest way to deploy components to a local, single-host is to use the HP Smart Update Manager graphical interface.
To deploy components to a local host using the GUI:
1. Ensure all minimum requirements are fulfilled as
described in "Minimum
requirements.
2. Ensure that the components to be deployed are accessible to the local host and are available in the same directory as the HP Smart Update Manager.
See "Using the GUI: local host installations " for information about performing the deployment using the graphical interface.
To deploy components to a local host using the command line interface:
1. Ensure all minimum requirements are fulfilled as
described in "Minimum
requirements.
2. Ensure that the components to be deployed are accessible to the local host and are available in the same directory as the HP Smart Update Manager.
3. Create a script to customize the deployment. See "Command line interface
for more information.
4. Execute the script.
The following figure illustrates the multiple-host deployment process.
To deploy components to multiple remote hosts using the GUI:
1. Ensure all minimum requirements are fulfilled as
described in "Minimum
requirements.
2. Ensure that the components to be deployed are accessible to the administrative system and are available in the same directory as the HP Smart Update Manager.
For information about performing the deployment using the
graphical interface, see "Using the GUI: multiple-host installations.
To deploy components to multiple remote hosts using the command line interface:
1. Ensure all minimum requirements are fulfilled as
described in "Minimum
requirements.
2. Ensure that the components to be deployed are accessible to the administrative system and are available in the same directory as the HP Smart Update Manager.
3. Create a script to customize the deployment. See "Command line interface" for more information.
4. Execute the script.
The HP Smart Update Manager provides an easy-to-use graphical interface that enables you to deploy and maintain software and firmware components. The HP Smart Update Manager is delivered with the PSP and the Firmware Maintenance CD. To start the deployment, run HPSUM.EXE.
The Inventory Progress screen is displayed while the HP Smart Update Manager builds an inventory of available updates.
The Select Installation Host(s) screen appears when the inventory process is complete.
The Select Installation Host(s) screen enables you to choose a host for component installation. By default, the first time you run the HP Smart Update Manager on a particular system, the only host available is local host. However, you can select remote hosts as your target by using the GUI. For more information about using the graphical interface for multiple remote deployments, see "Using the GUI: multiple-host installations."
The following columns are included in the Select Installation Host(s) screen:
· Host Name — Displays the host IP address or DNS name.
· Type — Categorizes the system as a host or group.
· Last Used — Enables you to sort the list by the most recently-used hosts.
· Description — Displays the user-defined description given to a host.
When the Remote Host or Group option in the Select Installation Host(s) screen is selected, you can sort the host list by selecting to view only the hosts, the groups, or both.
The Select Installation Host(s) screen also includes the following buttons:
· Manage Hosts — Adds, edits, and deletes hosts.
· Manage Groups — Adds, edits, and deletes groups.
· Edit — Edits the selected host.
· Next — Proceeds to the next step in the installation process.
· Exit — Exits the HP Smart Update Manager.
To continue with the deployment process, click Next. If the system discovery finds one or more predefined bundles such as from a PSP, the Select Bundle Filter screen appears. Otherwise, the deployment process proceeds. For multiple remote deployments, enter the credentials for the host. The Select Items to be Installed screen appears.
The Select Bundle Filter screen displays information about the predefined bundles available on your system and enables you to select which bundles to install. This screen also allows you to set options for non-bundle product versions.
For more information about the Select Bundle Filter screen, see "Selecting bundles to filter." Click OK to continue to system discovery. For multiple remote deployments, enter the credentials for the host. The Select Items to be Installed screen appears.
The Select Items to be Installed screen displays information about which components are available for installation on your system and enables you to select or clear components to install.
For more information about the Select Items to be
Installed screen and its sections, see "Selecting components to install."
After first time installations, the HP Smart Update Manager can deploy smart components on a local host or one or more remote hosts. The easiest way to deploy components on a local host is to use the HP Smart Update Manager GUI.
To continue with the deployment process using a local host, select a host from the Select Installation Host(s) screen, and click Next.
The Discovery Progress screen appears while the HP Smart Update Manager checks the local system to see which items are already installed. If the system discovery finds one or more predefined bundles such as from a PSP, the Select Bundle Filter screen appears. Otherwise, the Select Items to be Installed screen appears.
When the discovery process is complete, the Select Bundle Filter screen appears.
The Select Bundle Filter screen is divided into two sections.
The upper part of the screen includes the product and status information:
· Product field — Displays the product name of the predefined bundles found on the system. It also provides information about available versions.
· Status field — Indicates whether the installation is ready to proceed. It also provides additional information about the contents of the identified bundles.
The lower part of the screen includes options for installation. The Installation Options section allows you to set options for non-bundle product versions.
· To view all versions of the products included in the bundle, select ALLOW NON-BUNDLE VERSIONS. This option allows you to include updates that might be newer than those released in the bundle.
· To view updates of products not included in the bundle, select ALLOW NON-BUNDLE PRODUCTS. This option allows you to update other components on your system as you apply the bundle
· To force the installation process on the bundle products, select FORCE ALL BUNDLE PRODUCTS. This option allows you to install bundle products when the installed version is the same as or newer than the components in the bundle. This allows the installed software to be downgraded.
To view the PSP version history, click the version number in the product field.
To view a list of the bundle contents, click View Contents. This list also appears when you click the number of components in the status field.
To view the list of missing components, click the Missing Components link. You can obtain the missing components from the source media or from the HP website (http://www.hp.com).
Click OK to proceed with the deployment process.
When the discovery process and selecting the bundles to filter is complete, the Select Items to be Installed screen appears.
The Select Items to be Installed screen includes the following sections:
· Host field — Displays the system where the selected items will be installed.
· Status field — Indicates whether the installation is ready to proceed.
· Reboot section — Enables you to specify reboot settings and determine when reboots occur.
· Component selection pane — Enables you to specify which components to install.
When multiple hardware devices, such as hard drives or array controllers, exist in a single server, HP Smart Update Manager only lists each device once. If the devices have different firmware versions, the versions are listed from latest to earliest in a range. Whenever there are multiple instances of the firmware for installation, the instances are listed from earliest to latest. All hardware device firmware is flashed, if needed, to the selected version.
The component selection pane might be divided into sections, depending on your system. These sections can include the following headings:
· Updates to be Installed — Components in this section can be installed on your system.
· Installation Not Needed — Components in this section do not need to be updated.
· No Device Driver — The devices supported by components in this section are detected on the system but require that you install a device driver.
· Deselected by User — The components in this section are deselected and are not installed.
|
NOTE: If the Installation Not Needed section appears, you must click Installation Options to be able to select the components. |
The Select Items to be Installed screen also includes the following buttons:
· Select All — Selects all available components for installation
· Deselect All — Deselects all components currently selected for installation
· Default — Restores the selections in the product installation pane to the default view, which is based on the current configuration of the local system
· Exit — Exits the HP Smart Update Manager
· Install — Installs all selected components
· Add Supplemental — Enables you to deploy additional components from a removable device. The additional components must be located on the root of the device. This button is available only for offline deployments from the Firmware Maintenance CD.
The Status field of the Select Items to be Installed screen displays information about whether the installation is ready to proceed.
Icon |
Text |
Description |
|
Ready |
All selected components are ready to be installed. |
|
Already up-to-date |
No component installation is required. |
|
None Selected |
No components are selected for installation. |
|
x Critical Action |
X components are not ready for installation due to failed dependencies, where x is the number of components. The installation cannot proceed until the dependencies are met or the component is deselected for installation. |
The reboot section of the Select Items to be Installed screen enables you to specify preferred reboot behavior.
To instruct the system to reboot after updates are installed:
1. Click Reboot System After Installation.
2. Click Always or If Needed.
If Always is selected, then the system always reboots unless there is a component installation failure. If you select If Needed, then the system reboots if needed by at least one component unless there is a component installation failure.
To change the delay before reboot or the reboot message, click Reboot Options. The Set Reboot Options screen appears.
|
NOTE: In Linux, the Reboot Delay time is automatically converted from seconds to minutes. Any value under a full minute, 59 seconds or less, will be rounded to the next minute for Linux. |
Make any changes, and click OK.
The component selection pane of the Select Items to be Installed screen displays (by type) all components available for installation based on server and hardware options. The HP Smart Update Manager automatically checks each component for dependencies, if the component is already installed on the system, or if it requires a reboot after installation. Items available for installation are selected by default. You can deselect any components you do not want to install.
The component selection pane is divided into the following columns:
· Product — Specifies the name of the component, version number, and new component version number. To view the component version history, click the new version number.
· Status — Displays the status of the component.
Icon |
Text |
Description |
|
Ready for installation |
The component is ready for installation. |
|
Not selected for installation |
The component is not selected for installation. |
|
Already up-to-date |
The component is already up-to-date. To downgrade or rewrite a component, click Installation Options. |
|
No device driver installed |
The devices supported by the components in this section are detected on the system but require a device driver. Install the device driver. |
|
Deselected by user |
The component has not been selected for installation. |
|
Failed dependencies |
The component has a dependency that has not been met. To determine the nature of the failed dependency, click View Failed Dependencies. |
· Optional Actions — Allows you to select the bundles to filter by clicking Select Bundle Filter or configure components by clicking Configure Now. If you failed to select a bundle, want to change the bundle you are using, or want to change the bundle options, click Select Bundle Filter. If a component is configurable, it is indicated in the Optional Actions column and you can click Configure Now to configure the selected component.
· Additional — Contains the installation options for the components.
Failed dependencies are pre-requisites for HP Smart Update Manager to properly install the components. To determine if you need to configure components, see the information provided by the Failed Dependencies screen. The following figure shows the Failed Dependencies screen:
Installation Options allows you to specify component installation behavior. There are two screens which can appear when you click Installation Options in the Additional Options column. The component type to be installed determines which screen is presented. The first screen applies to firmware and software components and the second screen applies only to firmware. The screens are:
· Select Allow Downgrades to force the current firmware to be downgraded to an older version.
· Select Allow Rewrites to enable the HP Smart Update Manager to overwrite the current firmware version with the same version.
· Select Allow Shared Devices to upgrade firmware in a shared storage environment.
|
CAUTION: Updating the firmware while a shared device is in use can lead to data loss. Before enabling the Allow Shared Devices option, be sure any other servers sharing the selected devices are offline. |
The following table illustrates how changing the options for firmware upgrade behavior can change the firmware upgrade results. In this example, the array controller is assumed to be an HP Smart Array 6402 controller.
If the existing array controller has firmware version 3.00 installed, then updating the firmware produces results as described in the following table:
|
Default |
Allow downgrades |
Allow rewrites |
Firmware upgrade v3.05 |
3.05 |
3.05 |
3.05 |
Firmware upgrade v3.10 |
3.10 |
3.10 |
3.10 |
If the existing array controller has firmware version 3.10 installed, then updating the firmware produces results as described in the following table:
|
Default |
Allow downgrades |
Allow rewrites |
Firmware upgrade v3.05 |
No change |
3.05 |
3.10 |
Firmware upgrade v3.10 |
No change |
No change |
3.10 |
After you have selected all the components that you want to install, click Install to proceed with the installation. For more information about the individual components, see Component configuration. The Installation Progress screen appears.
When the installation is complete, the Installation Results screen appears.
The Installation Results screen includes the following information:
· Product — Specifies the name of the installed component. To see the component version history, click the version number.
· Status — Displays the installation status of the component.
Icon |
Text |
Description |
|
Success |
The component was installed successfully. |
|
Same/older version successfully installed |
The existing component was successfully downgraded or reflashed to the same or an older version. |
|
Update returned an error |
An update error has occurred. Click View Installation Log to see additional details. If limited information is available in the log file, see the HP Smart Update Manager log file. |
|
Installation failed |
The component was not installed. Click View Installation Log to see additional details. |
· Additional — Enables you to view the installation log for each component and reminds you if a reboot is needed.
Icon |
Text |
Description |
|
Reboot Needed |
The server must be rebooted for the component to take effect. |
To see additional details, click View Installation Log.
The Installation Results screen also includes the following buttons:
· Reboot Now — Reboots the server (This button is available for local installations only).
· Exit — Exits the HP Smart Update Manager.
The log files can be found in the following locations:
There are installation logs called hpsum_log.txt and hpsum_detail_log.txt which contain information about the installation activity for each host being updated. hpsum_log.txt contains a brief summary of the installation activity. hpsum_detail_log.txt contains all of the installation details, including errors, for each component installed.
· For Windows®, these files are located in subdirectories named according to the IP address of each host in the \CPQSYSTEM\log subdirectory on the boot partition of the local host. The directory containing the local host information is called \CPQSYSTEM\log\localhost instead of using the IP address.
· For Linux, these files are located in subdirectories named according to the IP address of each host in the /var/hp/log subdirectory of the local host. The directory containing the local host information is called localhost instead of using the IP address.
The HP Smart Update Manager provides an easy-to-use graphical interface that enables you to deploy and maintain firmware and software components.
The Inventory Progress screen appears while the HP Smart Update Manager builds an inventory of available updates. When the inventory process is complete, the Select Installation Host(s) screen appears.
The Select Installation Host(s) screen enables you to choose multiple groups and/or hosts for component installation.
NOTE: Local hosts cannot be included in a list with remote hosts or in a group.
To add hosts, see "Managing Hosts ." To add groups, see "Managing Groups."
To continue with the deployment process:
1. Select one or more hosts or groups.
2. Click Next to continue.
3. Enter the credentials for the host ("Entering credentials for hosts").
4. Click OK to proceed as described in Selecting bundles to filter on multiple hosts or "Selecting components to install on multiple hosts."
5. When the installation is complete, the Installations results for multiple hosts screen ("Viewing the installation results for multiple hosts" ) appears.
To add, edit, or delete hosts, click the Manage Hosts button. The Manage Hosts screen appears.
To add a host:
1. Click Add Host. The New Host dialog box appears.
2. Select the method to add a host from the following:
a. Enter the DNS name of the host to be added.
b. Enter the IP address of the host to be added.
c. Enter the IP address range of the hosts to be added. The starting and ending IP addresses must both be on the same subnet.
3. Enter an optional user-defined description given to the host to be added.
4. Click OK.
The new host is added to the list on the Select Installation Host(s) screen.
To edit an existing host:
1. Click the Edit Host button on the Manage Hosts screen. The Edit Host dialog box appears.
2. Make the desired edits.
3. Click OK.
To delete a host:
1. Click the Delete Host button on the Manage Hosts screen.
2. Click Yes when the confirmation screen appears.
To add, edit, or delete groups, click the Manage Groups button. The Manage Groups screen appears.
To add a group:
1. Click Add Group. The Edit Group dialog box appears.
2. Enter a group name.
3. Enter an optional user-defined description given to the group to be added.
4. Select the hosts to be added to the group from the available hosts pane. You can add new hosts from this screen by clicking the New Host button. For more information on adding hosts, see "Managing hosts."
5. Click the Enter >> button to move the selected hosts to the new group.
6. Click OK.
The new group is added to the list on the Select Installation Host(s) screen.
To edit an existing group:
1. Select the desired group and click the Edit Group button on the Manage Groups screen. The Edit Group dialog box appears.
2. Edit the group name as needed.
3. Edit the optional user-defined description given to the host as needed.
4. Use the Enter >> and << Remove buttons to add or remove hosts as needed.
5. Click OK.
To delete a group, select the group on the Manage Groups screen, then click the Delete Group button.
Click Yes when the confirmation screen appears.
When a single remote host is selected, the Enter Credentials for Host screen appears.
To enter the credentials for the host, choose one of the following:
· Select Enter Username and Password, and then enter the username and password.
· Select Use Current Credentials to use the currently logged-in user's credentials.
If an active update process is detected on the remote host, you can select Skip host or Restart update. Skip host causes the host to be ignored for the rest of the update process, while Restart update causes any existing or in-progress installation to be terminated.
Click OK to continue.
When a group or multiple hosts are selected, the Enter Credentials for Group screen appears.
The screen separates the remaining hosts that still require credentials from the completed hosts.
Each pane is divided into the following columns:
· Name — Specifies the name of the host.
· Status — Specifies the credentials status of the host.
Icon |
Text |
Description |
|
Entered |
The credentials for the host have been entered. |
|
Needs Credentials |
The credentials for the host have not been entered. |
|
Credentials Failed |
The credentials entered for the host have failed. |
|
Unable to access host |
The host cannot be accessed using the credentials entered, or the host cannot be found in the network. |
|
Host Skipped Due to Existing HPSUM Session |
The host is skipped due to an existing HP Smart Update Manager session. |
· Description — Displays the user-defined description given to the host.
To enter the credentials for the host:
1. In the left pane, select the host from the list of hosts requiring credentials. If all the credentials are the same, click Select All to select all the hosts on the list.
2. Click the Enter >> button to enter the required credentials and to move the selected host to the Completed Hosts pane.
3. Click Next to continue.
If the system discovery finds one or more predefined bundles, the Select Bundle Filter screen appears.
See "Selecting bundles to filter" for more information about the screen. Click OK to proceed with the installation process.
The Select Items to be Installed screen displays the server hosts and their status information.
The Select Items to be Installed screen includes the following buttons:
· View Host — Enables you to view additional information about a host after you select it.
· Install — Installs all selected components on all remote hosts.
· Exit — Exits the HP Smart Update Manager.
The server host pane of the Select Items to be Installed screen displays summary information for the server hosts available for installation, and features a drilldown of individual hosts.
The server host pane is divided into the following columns:
· Host — Specifies the name of the system, number of updates available, and the estimated time for the installation.
· Status — Specifies the status of the host.
Icon |
Text |
Description |
|
Ready |
The host is ready for installation. |
|
Nothing to Install |
The host is already up-to-date. |
|
Host Skipped Due to Existing HPSUM Session |
The host is skipped due to an existing HP Smart Update Manager session. |
|
Action Required |
The host is not ready for installation. Click View Host for additional information. |
|
Discovery Failed |
The host is not ready for installation. The detection of installed hardware, software, and firmware has failed. |
|
NOTE: The default reboot behavior after updates are installed might also appear in the Status column. |
To zoom in to single host selections, click View Host on the Select Items to be Installed screen. The Selections for Single Host screen appears.
To set single-host selections, proceed as described in "Selecting Components to Install."
After setting the single-host selections for all hosts to be updated, click Install on the Select Items to be Installed screen to proceed with the installation.
When the installation is complete, the Installation Results screen appears.
The Installation Results screen is divided into the following columns:
· Host —Specifies the IP address or DNS name of the host.
· Status — Specifies the overall installation status of the component.
Icon |
Text |
Description |
|
Success |
The host was updated successfully. |
|
Nothing to install |
The host is already up-to-date. |
|
Installation cancelled by user |
The installation was cancelled and cannot continue. |
|
Installation failed |
One or more of the components have failed. |
The Installation Results screen also includes the following buttons:
· View Host — Enables you to view installation results for the selected host.
· Exit — Exits the HP Smart Update Manager.
To view single-host installation results, double-click on the host (or select the host), and then click View Host.
Proceed as described in Viewing the installation results.
In this section |
This section addresses advanced installation of PSPs in Windows®.
Component configuration requires that Smart Components are in a write-accessible location. A CD or read-only network share is not supported. If you have obtained your support pack from the SmartStart CD, copy the entire contents of the support pack directory to the local hard drive or a network share, and then make sure the read-only attributes are cleared from all files.
Some components might have required or optional configuration settings. Configuration parameters can include information necessary to set up the component correctly or passwords required for software installed by the component. If the optional configuration data of a component is not provided and the component has not been installed previously, it will use default values for that configuration data. If the component has been previously installed and configured, then the existing configuration information will be preserved if no changes are made to the configuration data.
Configurable components are indicated in the Optional Actions column of the Select Items to be Installed screen screens. To configure a component, click Configure Now.
Follow the instructions when the Item Configuration screen appears. When the configuration is complete, the Select Items to be Installed screen reappears.
The HP Smart Update Manager command-line interface enables you to script custom installations.
The general command line syntax for the HP Smart Update Manager is:
hpsum [/h[elp]] [/f[orce]] [/g (downgrade)] [/e (rewrite)]
[/m[utual]] [/r[eboot]] [/reboot_message "message"]
[/reboot_delay timeout_in_seconds] [/reboot_always] [/s[ilent]]
[/c <component_to_install>][/group] [/bundle] [/allow_update_to_bundle] [/dryrun] [/continue_on_error <error>] [/override_existing_connection] [/user <username>]
[/passwd <password>] [/target <netAddress>]
Using HP Smart Update Manager with HP BladeSystem C-Class Onboard Administrator or remote hosts requires the user ID, password and the target server IP address or DNS name to log in.
|
NOTE: All arguments and information enclosed in brackets are optional. The arguments may be prefixed with either a '-' or '/' character. These examples show only the '/'. |
If no command line arguments are executed on the command line, the component GUI appears.
Command line argument |
Description |
/h[elp] or /? |
This argument displays command line Help information. |
/f[orce] |
This argument enables you to override or downgrade an
existing installation of a given component. |
/g or /downgrade |
This argument enables you to downgrade to an earlier version of firmware for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) |
/e or /rewrite |
This argument enables you to rewrite the same version of firmware to a device in the event that the firmware has been compromised, or to confirm that the version has been correctly installed. This argument must be used with the /force option or it will be ignored. (Applies to firmware only.) |
/m[utual] |
This argument informs the firmware flash engine to flash the firmware if the device to be flashed is in a shared storage environment. If the device to be flashed is in a shared storage environment and the -m option is not passed, the component installation will fail. (Applies to firmware only.) |
/r[eboot] |
This argument causes the server (or host server in a remote installation) to reboot if the following conditions are met: · The /reboot option has been selected or given as a command line argument. · All components selected for installation were successfully installed. ·
At least one of the components
installed required a reboot to complete its installation. |
/reboot_message "message" |
This argument displays the specified reboot message on remote consoles connected to the server to be rebooted. This argument must be used with the /reboot option or it will be ignored. |
/reboot_delay timeout_in_seconds |
This argument delays the reboot of the server for timeout_in_seconds seconds. This argument must be used with the /reboot option or it will be ignored. Acceptable values are between 15 and 3600. The default timeout value is 15 seconds for Windows® and 60 seconds for Linux. |
/reboot_always |
This argument forces the server to reboot if the following conditions are met: ·
The /reboot_always option
has been selected or given as a command line argument. All
components selected for installation were successfully installed. |
/s[ilent] |
This argument causes the installation to run silently
with no GUI or console output. All data is written to the log file. Any
prompts use the default option and continue the installation without user
input. If a component requires input before installation, such as
configuration information, the installation of the component fails and an
error message is written to the log file. |
/c <component to install> |
This argument specifies a single component to install. You can specify multiple /c options and components. The components are installed in the order provided unless dependencies between components require installation in a different order. If so, the utility changes the installation order based on the component dependencies to ensure the successful installation of as many components as possible. |
/group
<HPSUMgroup> |
This argument specifies an already defined group name
in the HP Smart Update Manager internal database where the group hosts
reside. |
/bundle
<bundlename> |
This argument specifies the name of the bundle to be
installed and can be specified multiple times. |
/allow_update_to_bundle |
This argument allows the user to install newer
versions of components defined in a PSP or firmware bundle if they
exist. This parameter will allow these
components to replace the older versions of the same component that may have
shipped with the bundles. |
/dryrun |
This argument simulates the installation for a test
run. Nothing is installed. |
/continue_on_error <error> |
This argument causes the installation to continue and
ignore errors. Currently, only the <error>=ServerNotFound
is supported. The ServerNotFound
option can be used to bypass inactive or unavailable remote targets when
deploying firmware or software to multiple remote hosts at the same time. |
/override_existing_connection |
This argument is used to define the behavior when a
remote host is found to already have an existing HP Smart Update Manager
session in progress. The /override_existing_connection overrides the session in
progress and re-initializes the installation framework on the remote host. |
/user
<username> |
This argument enables you to log in to HP BladeSystem C-Class Onboard Administrator or remote hosts
with this user ID. |
/passwd <password> |
This argument enables you to use this password for the
userid specified in the /user parameter. The password is used to login to remote
hosts and HP BladeSystem C-Class Onboard
Administrators. |
/target
<netAddress> |
This argument is the IP address or the DNS name of a
HP BladeSystem C-Class Onboard Administrator or
remote host. When two Onboard Administrators are in an enclosure, this
argument should be the active Onboard Administrator. |
HP Smart Update Manager has consolidated the return codes from Linux and Windows® components into a new, enhanced return code mapping. These return codes determine the status of the component installation. You can also use return codes in a script to control the execution of the script and determine any required branching.
To view the installation log file locations, see "Viewing the installation results."
Return code |
Value |
Text |
SUCCESS_NO_REBOOT |
0 |
The installation was successful. |
SUCCESS_REBOOT |
1 |
The installation was successful, but a reboot is required. |
SUCCESS_NOT_REQUIRED |
3 |
The component was current or not required. |
FAILURE_GENERAL |
-1 |
A general failure occurred. See the error log for details. |
FAILURE_BAD_PARM |
-2 |
A bad input parameter was encountered. |
FAILURE_COMPONENT_FAILED |
-3 |
The installation of the component failed. |
The PSP for Microsoft® Windows® (version 7.90 or later) powered by the HP Smart Update Manager utility enables you to deploy firmware and PSP software components simultaneously. Deployment of firmware and software components simultaneously is supported only for Windows® online deployments. The Microsoft® Windows® PSP and firmware components must be in the same directory in order to deploy simultaneously.
To deploy firmware and PSP software components simultaneously, run the HP Smart Update Manager. On the Select Bundle Filter screen, select the bundle and the ALLOW NON-BUNDLE PRODUCTS option.
Click OK to proceed with the deployment process. The Select Items to be Installed screen appears with the appropriate firmware and software components.
In this section Recovering from a failed ROM upgrade Recovering from a loss of Linux remote functionality Troubleshooting installation of the PSP for Microsoft Windows |
Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure.
When you flash the system ROM, ROMPaq
writes over the backup ROM and saves the current ROM as a backup, enabling you
to switch easily to the alternate ROM version if the new ROM becomes corrupted
for any reason. This feature protects the existing ROM version, even if you
experience a power failure while flashing the
When the server boots, the system identifies whether the current ROM is corrupt. If a corrupt ROM is detected, the system boots from the backup ROM and alerts you through POST that the ROM is corrupt.
To access the redundant ROM through RBSU:
1. Access RBSU by pressing the F9 key during powerup when the prompt is displayed in the upper right corner of the screen.
2. Select Advanced Options.
3. Select Redundant ROM Selection.
4. Select the ROM version.
5. Press the Enter key.
6. Press the Esc key to exit the current menu or press the F10 key to exit RBSU. The server restarts automatically.
If RBSU is inaccessible, you can switch ROM images by changing the switch settings on the system configuration switch. See your server documentation for more information.
If both ROM images are corrupt, use ROMPaq recovery.
If both the current and backup versions of the ROM are corrupt, perform ROMPaq disaster recovery procedures:
1. On another server, insert the Firmware Maintenance CD. The Firmware Maintenance CD interface opens automatically.
2. Read the End-User License Agreement. If you agree to the terms of the license agreement, click Agree to continue. The Firmware Maintenance CD interface is displayed.
3. Click the Firmware Update tab.
4. Click Browse Firmware CD.
5. Browse to and save the ROMPaq image to the hard drive.
6. Execute the ROMPaq image to create the ROMPaq diskette.
7. Switch to the server with the corrupted
8. Power down the server.
9. Insert the ROMPaq diskette.
10. Power up the server.
a. The server generates one long beep and two short beeps to indicate that it is in disaster recovery mode. If the diskette is not in place, the system continues to beep until a valid ROMPaq diskette is inserted.
b. The ROMPaq diskette flashes both system ROM images. If successful, a sequence of ascending audible beeps is generated. If unsuccessful, a sequence of descending audible beeps is generated and you need to repeat the disaster recovery process.
11. Power down the server.
12. Remove the ROMPaq diskette.
13. Power up the server.
To manually set the server for ROMPaq disaster recovery:
1. Power down the server.
2. Remove the access panel.
3. Set the system maintenance switch positions for disaster recovery. Switch positions are server-specific; see the server documentation for information about the correct settings for your server.
4. Insert a ROMPaq diskette with the latest system ROM from the Firmware Maintenance CD or the HP website (http://www.hp.com/support).
5. Install the access panel.
6. Power up the server.
7. Allow the system to boot completely.
8. Repeat steps 1 and 2.
9. Reset the system maintenance switch positions to their original settings.
10. Repeat steps 5 and 6.
To recover from an option ROM upgrade failure, use the recovery method that is appropriate to the specific option.
Array controllers support Recovery ROM, which is a
redundancy feature that ensures continuous system availability by providing a
backup
|
NOTE: Storage option ROMs cannot be downgraded with ROMPaq because ROMPaqs have been retired as a delivery method for storage options. |
To perform disaster recovery for RILOE II, iLO, and iLO 2, see the documentation for your particular Lights-Out management product on the Remote management website (http://www.hp.com/servers/lights-out).
When the Unable to Access Host message appears, the target firewall is enabled. By default, the target firewall is enabled in Linux.
To recover remote Linux functionality, the target and host firewall must be disabled or reconfigured.
The following issues might be encountered with the Microsoft® Windows® PSPs. The issues are in bold and their resolutions follow.
· How do I set the rules for Windows® Firewall and Security Policy
properly?
When the Windows Security Alert appears, click Unblock and set your firewall settings to the following:
1. Click Start>Control Panel>Administrative Tools>Windows Firewall with Advanced Security>Inbound Rules>Remote Administration (NP-IN).
2. Select Enabled and Allow the connections.
In this section |
To download the ProLiant Firmware Maintenance and other CDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads).
For information about firmware support, refer to the ProLiant
Firmware Maintenance CD Matrix
(http://www.hp.com/servers/smartstart/supportmatrices).
For more information about PSPs, refer to the PSP website (http://www.hp.com/servers/psp).
To download the latest PSPs, refer to the software and
drivers download page (http://www.hp.com/servers/swdrivers).
For information about HP Subscriber's
Choice, refer to the Subscriber's Choice website (http://www.hp.com/go/subscriberschoice).
For information about Online ROM Flash
Components, refer to the Online ROM Flash User Guide
on the Online ROM Flash
website (http://h18023.www1.hp.com/support/files/server/us/romflash.html).
For information on the HP Systems
Insight Manager, refer to the following documents on the HP Systems Insight
Manager website (http://www.hp.com/go/hpsim):
HP Systems Insight Manager
Installation and User Guide
HP Systems Insight Manager Help
Guide
For information about the SmartStart Scripting Toolkit, refer to the Toolkit website
(http://www.hp.com/servers/sstoolkit).
To download the SmartStart
and other CDs, refer to the SmartStart download
website (http://www.hp.com/go/ssdownloads).
For information about the ProLiant Essentials Rapid Deployment Pack, refer to the
Rapid Deployment Pack website(http://www.hp.com/servers/rdp).
For general information on management
products, refer to the ProLiant Essentials website
(http://www.hp.com/servers/proliantessentials).
For information about operating
systems supported by ProLiant servers, refer to the
operating system support matrices (http://www.hp.com/go/supportos).
For information about SmartStart support, refer to the SmartStart
support matrices (http://www.hp.com/servers/smartstart/supportmatrices).
For information about Microsoft®
Windows® operating systems, refer to the Microsoft®
website
(http://www.microsoft.com).
For information about Linux operating
systems, refer to one of the following websites:
· Red Hat Linux (http://www.redhat.com)
· SUSE LINUX (http://www.novell.com/linux)
For the name of the nearest HP
authorized reseller:
· In
the United States, see the HP US service locator
webpage
(http://www.hp.com/service_locator).
· In other locations, see the Contact
HP worldwide (in English) webpage
(http://welcome.hp.com/country/us/en/wwcontact.html).
For HP technical support:
· In
the United States, for contact options see the Contact
HP United States webpage
(http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:
o Call 1-800-HP-INVENT (1-800-474-6836). This service is
available 24hours a day, 7days a week. For continuous quality improvement,
calls may be recorded or monitored.
o If you have purchased a Care Pack (service upgrade),
call 1-800-633-3600. For more information about Care Packs, refer to the HP website
(http://www.hp.com).
· In other locations, see the Contact
HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).
graphical user interface
HP Smart Update Manager
Integrated Lights-Out
Integrated Lights-Out 2
network interface controller
Power-On Self Test
ProLiant Support Pack
ROM-Based Setup Utility
Remote Insight Lights-Out Edition II
read-only memory
serial attached SCSI
universal serial bus