Viewing the installation results

When the installation is complete, the Installation Results screen appears.

Proliant Maintenance CD 90240 Viewing the installation results

The Installation Results screen is divided into the following columns:

  • Product—Specifies the name of the installed component. To see the component version history, click the version number.
  • Status—Specifies the installation status of the component.

The following icons may appear in the Status column.

Icon

Text

Description

Proliant Maintenance CD 53198 Viewing the installation results

Success

The component was installed successfully.

Proliant Maintenance CD 53198 Viewing the installation results

Same/older version successfully installed

The existing component was successfully downgraded or reflashed to the same or older version.

Proliant Maintenance CD 53192 Viewing the installation results

Update returned an error

An update error has occurred. See the HP Smart Update Manager log file for details.

Proliant Maintenance CD 53192 Viewing the installation results

Installation failed

The component was not installed. To see additional details, click View Installation Log.

  • Additional—Enables you to view the installation log for each component and reminds you if a reboot is needed.

    Icon

    Text

    Description

    Proliant Maintenance CD 65806 Viewing the installation results

    Reboot Needed

    The server must be rebooted for the component to take effect.

    To see additional details, click View Installation Log.

    Proliant Maintenance CD 65552 Viewing the installation results

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.

    NOTE: After updating hard drives in external enclosures such as MSA20, you must power cycle the external enclosures. The Reboot button in HP Smart Update Manager only reboots the server but never power cycles an external enclosure.

There are installation logs named hpsum_log.txt and hpsum_detail_log.txt, which contain information about the installation activity for each host being updated. The hpsum_log.txt log contains a brief summary of the installation activity. The hpsum_detail_log.txt log contains all of the installation details, including errors, for each component installed.

The log files can be found in the following locations:

  • For Windows® operating systems, these files are located in subdirectories named according to the IP address of each host in the CPQSYSTEMhplog subdirectory on the boot partition of the local host. The directory containing the local host information is named localhost instead of being named after the IP address.
  • For Linux operating systems, 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 named localhost instead of being named after the IP address.

There is a new file that contains detailed information on the execution of HP Smart Update Manager.

  • For Windows® operating systems, the filename is C:cpqsystemhploghpsum_execution_log_<date>_<time>.log.
  • For Linux operating systems, the filename is /var/hp/log/hpsum_execution_log_<date>_<time>.log.

    NOTE: Using the offline environments provided by the Firmware Maintenance CD and HP BladeSystem Firmware Deployment Tool results in the log files being written to the Linux location.

HP Smart Update Manager also creates trace logs of its installation that can be used to debug problems. These trace files are located in the following places:

  • For Windows Server® 2003/XP/Vista, %TEMP%hp_sum.
  • For Windows Server® 2008, %TEMP%<number>hp_sum. Normally, the <number> is 1.
  • For Linux, /tmp/hp_sum.

HP Smart Update Manager creates a separate trace log for each target server. These are captured in subdirectories under the trace log directories. The directories start with Target_0, Target_1, and so forth. These contain the target specific trace information. No passwords or sensitive data is stored in this trace logs.

Viewing the installation results