HP Smart Update Tools User Guide

Transcription

1 HP Smart Update Tools User Guide Version Abstract This document describes how to use HP Smart Update Tools (HP SUT) to update firmware and operating system drivers on HP ProLiant servers. This document is intended for individuals who understand the configuration and operations of Microsoft Windows, Windows Server, Linux, smart components, and the risk of data loss from performing updates. Part Number: Published: May 2016 Edition: 1

2 Copyright 2015, 2016 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Acknowledgments Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat Enterprise Linux is a registered trademark of Red Hat, Inc. Linux is a registered trademark of Linux Torvalds in the U.S. and other countries.

3 Contents 1 Introduction...5 HP SUT key features...5 HP SUT products...5 HP SUT operating modes Downloading, installing, and launching HP SUT for Windows and Linux...7 Installation requirements...7 Downloading and installing HP SUT for Windows and Linux from the Hewlett Packard Enterprise website...7 Installation modes and credential choices...8 Verifying HP SUT for Windows and Linux installation...10 Deploying HP SUT using a Linux build plan...10 Creating a build plan for Linux...10 Editing an existing build plan...12 Removing HP SUT...12 Using a dual boot environment for HP SUT for Windows and Linux Downloading, installing, and launching HP SUT for VMware ESXi...13 Installation requirements...13 Configuring HP SUT for VMware ESXi Using HP SUT with HPE OneView Using HP SUT for Windows and Linux from the command line...16 Command-line arguments Using HP SUT for VMware ESXi from the command line...18 Command-line arguments Using HP SUT gatherlogs scripts Troubleshooting...21 Troubleshooting for HP SUT for Windows and Linux...21 HP SUT Self Update fails on a TPM-enabled machine...21 Could not clear staging directory...21 Baseline URI provided is invalid...21 Insufficient disk space to copy the files...21 Unable to mount baseline ISO through ilo Virtual Media...21 The concurrent download limit of the baseline ISO has been reached or the baseline provided is not detected as a supported baseline...22 HP SUM execution failed...22 Baseline inventory operation failed...22 Deployment operation failed...23 Version of HP SUM in the baseline ISO is lower than Staging directory is improper...23 Staging directory creation failed...23 Reboot command failed...24 Operation request was changed unexpectedly while processing another request...24 Failed to copy file during staging...24 Staging or deployment failed due to unknown error...24 HP SUT does not understand the baseline request from HPE OneView...24 Media browse window appears after mounting the Virtual Media...24 Troubleshooting for HP SUT for VMware ESXi...24 HP SUM baseline validation failed...24 HP SUM binary download failed...25 SPP folder creation failed...25 Contents 3

4 Reboot command execution failed...25 ilo version mismatch...25 ESXi target moves to Installfailed state when updating HP SUT through HPE OneView...25 Tips for detecting vcenter Server and HPE OneView connection failure FAQs Support and other resources...28 Accessing Hewlett Packard Enterprise Support...28 Accessing updates...28 Websites...28 Customer self repair...29 Remote support...29 Documentation feedback...29 Index Contents

5 1 Introduction HP Smart Update Tools (HP SUT) is a software utility used by HPE OneView 2.0 to stage, install, and activate firmware and driver updates. HP SUT reports the progress of the updates through the HPE OneView dashboard. HP SUT can be run in two different modes: As a service HP SUT runs in the background via the ilo management network to enable fully automatic updates with no operating system (OS) administrator intervention required. As a command-line application HP SUT runs in OnDemand mode from the command line, giving the OS administrator control over the maintenance process. HP SUT leverages HP Smart Update Manager (HP SUM) for dependency checking, installation order, and staging information. HP SUT orchestrates the deployment of firmware and drivers using HP SUM from within the Service Pack for ProLiant (SPP) that is supplied from HPE OneView. For more information about HP SUM, see: HP SUT key features HP SUT key features include: Assists HPE OneView in performing online server firmware and driver updates. Provides automated compliance reporting in the HPE OneView dashboard. Decreases the number of reboots needed during the server maintenance window, increasing system uptime. Moves firmware staging and development tasks outside the actual maintenance window so that one reboot during the maintenance window activates both firmware and driver updates. HP SUT products HP SUT offers the following products that run with HPE OneView: HP SUT for Windows and Linux Stages, installs, and activates firmware and drivers online to supported versions of Microsoft Windows and Linux operating systems. Delivered format for 64-bit systems includes Windows smart component and Linux RPM. Available for download from HP SUT for VMware ESXi Online stages, installs, and activates firmware and software updates to supported versions of VMware ESXi. Download and install on Red Hat Enterprise Linux 7.0 (64 bit) as an RPM. HP SUT key features 5

6 Figure 1 HP SUT for VMware ESXi architecture HP SUT operating modes HP SUT can be run in either Auto mode or OnDemand mode. Table 1 HP SUT interface options Interface Auto mode OnDemand mode Description This mode enables HP SUT to run in the background, as a service on the host server and poll HPE OneView at scheduled intervals to keep HPE OneView up-to-date by posting the progress in the firmware section of the server profile. In Auto mode, when HPE OneView makes a request, HP SUT automatically stages and deploys available components. If the staged components do not require a reboot to activate, the components are automatically activated after installation. However, if the components do require a reboot to activate, HP SUT waits for the OS administrator to execute an activation command using the command line. This information is reported through the HPE OneView dashboard. See Using HP SUT with HPE OneView for more information about Auto mode. This is the default mode. This mode allows the OS administrator to write requests as command-line arguments on the host server instead of allowing a service run automatically in the background. In this mode, the activation process only moves forward when the OS administrator logs into the host server and executes an HP SUT command from the command line. HP SUT communicates the current status of the firmware to HPE OneView, which is displayed in the dashboard. See Using HP SUT for Windows and Linux from the command line or Using HP SUT for VMware ESXi from the command line for more information about running HP SUT from the command line. 6 Introduction

7 2 Downloading, installing, and launching HP SUT for Windows and Linux These instructions are for Windows and Linux users only. See Downloading, installing, and launching HP SUT for VMware ESXi for information about downloading and installing HP SUT for VMware ESXi. In the Windows and Linux configuration, HP SUT runs on each server. You can download HP SUT from the Hewlett Packard Enterprise website. These downloads do not include firmware, software, or drivers. You can obtain software and firmware from the SPP. Figure 2 HPE OneView systems using HP SUT for Windows and Linux Installation requirements HP SUT requires HP SUM or later, ilo 4 firmware 2.30 or later, and an ilo Advanced Pack license for deployment. If the server firmware is managed by HPE OneView 2.0, all of the requirements are met when HPE OneView is performing the server updates. Therefore, it is not required to update the ilo firmware or apply a license when using HP SUT to perform firmware and driver updates. Downloading and installing HP SUT for Windows and Linux from the Hewlett Packard Enterprise website 1. Go to and download the correct version of HP SUT for your operating system (.exe or.rpm). 2. Install HP SUT manually or in a script. See Creating a build plan for Linux for creating and running a script. Installation requirements 7

8 Installation modes and credential choices HP SUT for Windows and Linux supports three installation modes besides the default OnDemand mode: AutoStage AutoDeploy AutoDeployReboot Each mode uses the current user credentials (for example: Administrator in Windows, root in Linux) automatically for firmware and software updates through HP SUM. NOTE: HP SUT cannot be installed as part of a server profile from HPE OneView. In HP SUT for Windows and Linux 1.0.0, the default mode is AutoDeploy. Starting with HP SUT for Windows and Linux 1.0.1, the default installation mode was changed to OnDemand. Users can change the installation mode from OnDemand to AutoStage, AutoDeploy, or AutoDeployReboot using one of the following methods: Method 1 Configure the installation mode for HP SUT in HP SUM using the baseline GUI before installing HP SUT Windows SUT component update in HP SUM Linux SUT component update in HP SUM To configure components: 1. On the HP SUM Baseline Library screen, select the baseline you want to use, select Components, and then click Configuration state until the components that offer configuration settings are filtered to the top. 2. Select the Configurable for HP SUT component you want to configure. 3. Change the Mode to any of the Auto state, and then click Save in HP SUM to store the component settings in the current HP SUM database. 4. Use this baseline to install SUT component on the each of the target servers. To configure and export component configurations: 8 Downloading, installing, and launching HP SUT for Windows and Linux

9 1. On the HP SUM Baseline Library screen, select the baseline you want to use, select Components, and then click Configuration until the components that offer configuration settings are filtered to the top. 2. Select the Configurable for HP SUT component you want to configure. 3. Change the Mode to any of the Auto modes, click Save and Export, and then select a directory where you want to save the component configuration. HP SUM creates a directory named after the component you exported. The name is component name_conf. The Activity screen displays the address where it saved the configuration file. HP SUM includes a README file that provides instructions on how to deploy the component in stand-alone mode. Method 2 Configure the installation mode for HP SUT by passing the configuration file directly to the HP SUT component installation. 1. Run HP SUM, set the mode to either AutoDeploy, AutoDeployReboot, or AutoStage on the baseline configuration page, and then export the configuration details to a directory. Use one of the following configuration files to run components independently: Windows: cp exe /silent /config_file C:\temp\cp027867_conf\hpsut_cfg.dat Linux: Copy the hpsut_cfg.dat file to /usr/local/hp/ directory and run the install command 2. Extract the component to a directory, copy hpsut_cfg.dat to a different directory, and edit the file to set the mode to Auto. 3. Use the following configuration file to run the component independently: Method 3 Windows: /config_file option: cp exe /silent /config_file C:\temp\cp027867_conf\hpsut_cfg.dat Linux: a. Extract the RPM using rpm2cpio command: irpm2cpio hpsut linux.x86_64 cpio id b. Edit the hpsut_cfg.dat file, copy it to /usr/local/hp/ directory, and run the install command. After HP SUT is installed, change the mode using the set mode command: 1. Copy the HP SUT component on to the target server, and execute the component on the command prompt/shell prompt, or double-click the component executable. 2. After HP SUT is installed successfully, open a new console, and execute the following command: hpsut -set mode=autodeploy Installation requirements 9

10 Verifying HP SUT for Windows and Linux installation To verify the installation, open a Windows or Linux command prompt window and enter either of the following: hpsut status hpsut /status The installation status of the current firmware is displayed, along with information about the staging directory, the baseline Uniform Resource Identifier (URI), and the mode of operation, as shown in the following example. IMPORTANT: higher. If this command does not work, verify that the ilo firmware version is 2.30 or Deploying HP SUT using a Linux build plan Creating a build plan for Linux You can write a script to install HP SUT on Windows or Linux. The following is an example of an Insight Control Server Provisioning build plan for Linux for deploying HP SUT. The same type of script can be created for Windows and it can also be replicated for other deployment tools. #!/bin/sh # (c) Copyright 2015 Hewlett Packard Development Company, L.P. # Globals mountpoint=/mnt/media if [! d $mountpoint ] then mountpoint=/mnt/ms fi # =================== # MAIN # =================== HPSUT_RPM_NAME=$1 HPSUT_INSTALL_FILE=$mountpoint/Media/SUT/$HPSUT_RPM_NAME echo Installing the HPSUT rpm $HPSUT_INSTALL_FILE at time `dat` rpm ivh $HPSUT_INSTALL)FILE 10 Downloading, installing, and launching HP SUT for Windows and Linux

11 hpsut_install_status=`rpm qs hpsut wc 1` Adding the HP SUT installation script to IC Server Provisioning 1. Place your downloaded HP SUT package in the media server path: $ROOT/Media/SUT/ <SUT_RPM_NAME>. 2. Provide the HPSUT_RPM_NAME as input to the script, as shown in the following figure. Figure 3 Parameters NOTE: If an alternate location in the media server is required, you can change it and the script must be modified accordingly. The variable HPSUT_INSTALL_FILE must be modified to the new path. A similar script must be written for Windows as well. For Windows, the binary must be named cp exe and must be run as cp exe/s from the.bat script. This installs the script without prompting you. 3. Click OK. After the script executes, as shown in the following figure, the RPM installation logs contain any errors listed in the STDERR section. Figure 4 Successful build plan Deploying HP SUT using a Linux build plan 11

12 Editing an existing build plan You can edit an existing build plan for Windows or Linux and add the HP SUT-Linux-Install script to it. When editing the build plan, note the following: The Set Media Source must been executed as part of the build plan prior to editing. The input parameter has to be provided as the RPM name of the HP SUT installer binary that has been downloaded from Removing HP SUT You can run the following script as part of a build plan to remove HP SUT from a Linux server. A similar script can be created for Windows. #!/bin/sh # (c) Copyright 2015 Hewlett-Packard Development Company, L.P. # Globals # ==================== # MAIN # ==================== HPSUT_RPM_INSTALLED_NAME=`rpm qa hpsut` echo Removing the HPSUT rum $HPSUT_RPM_INSTALLED_NAME at time `date` rpm e $HPSUT_RPM_INSTALLED_NAME status=$? if [ $status!= 0 ]; then echo Removing HPSUT has failed else echo Removing HPSUT was successful fi exit $status Using a dual boot environment for HP SUT for Windows and Linux The following shows a summary of all the possibilities in a dual boot setup where both Windows and Linux versions of HP SUT coexist: Table 2 Dual boot setup Installation order Windows only Linux only Windows and then Linux Linux and then Windows Can you run HP SUT from Windows? Yes No No Yes, if the staging directory is changed to a Windows directory before staging begins. Yes No, if the staging directory is changed to a Linux directory before staging begins. Can you run HP SUT from Linux? No Yes Yes No, if the staging directory is changed to a Windows directory before staging begins. No Yes, if the staging directory is changed to a Linux directory before staging begins. 12 Downloading, installing, and launching HP SUT for Windows and Linux

13 3 Downloading, installing, and launching HP SUT for VMware ESXi These instructions are for VMware ESXi users only. See Downloading, installing, and launching HP SUT for Windows and Linux for information about downloading and installing HP SUT for Windows and Linux. In the VMware ESXi configuration, HP SUT does not run on the host directly. Instead, it runs remotely on a separate VM or server so that it can be configured to talk to HPE OneView and to all of the ESXi hosts. Only a single instance of HP SUT for VMware ESXi can be associated with a single vcenter Server and a single HPE OneView instance. If you have the same vcenter Server host associated with another HPE OneView, you must run and install another HP SUT for VMware ESXi instance to handle the same vcenter Server and the additional HPE OneView you are managing in your environment. Figure 5 HPE OneView systems using HP SUT for VMware ESXi Installation requirements HP SUT for VMware ESXi inventories, stages, installs, and activates drivers and firmware updates to support VMware vsphere operating systems. HP SUT for VMware for ESXi is available for the HPE OneView product as a 64 bit Linux RPM. As a best practice, Hewlett Packard Enterprise recommends not running HP SUT for VMware ESXi in a HPE OneView managed server. If HP SUT does run in this manner and firmware updates are performed, HP SUT will stop. Installation requirements 13

14 Configuring HP SUT for VMware ESXi 1. Prepare the environment by installing HP SUT for VMware ESXi on a Red Hat Enterprise Linux 7.0 or later server. This can be a server or a VM. 2. Run the following setup commands to set up the vcenter Server host details and the HPE OneView host details. vcenter Server settings are: vcenterhost, vcenterusername, and vcenterpassword. HPE OneView settings are: managementhost, managementhostusername, and managementhostpassword. NOTE: Make sure the ESXi server is powered on and booted into the OS. These commands allow HP SUT to retrieve the firmware profile details from HPE OneView and use the OATH token from vcenter Server to get credential-less access to the ESXi host to perform the firmware and OS driver updates. 14 Downloading, installing, and launching HP SUT for VMware ESXi

15 4 Using HP SUT with HPE OneView HP SUT runs on systems managed by HPE OneView, keeping HPE OneView up to date with the progress of firmware and driver update requests, and posts that progress in the Firmware section of the Server Profile page. HP SUT can run in one of two operating modes: Auto mode or OnDemand mode. OnDemand mode is the default mode and allows the OS administrator to write requests as command-line arguments on the target server. When running in Auto mode, and a request is made by HPE OneView, HP SUT automatically stages and deploys components. If the deployed components do not require a reboot, the firmware and drivers are activated immediately. However, if the components do require a reboot to activate, an OS administrator can choose to reboot the server using the hpsut -activate command from the command line. All of this information is reported through the HPE OneView dashboard. There are three variations of the automatic operating mode available when running HP SUT with HPE OneView: Auto stage (autostage) When a request is made by HPE OneView, HP SUT stages the components on the server in the staging location. Any further action requires you to issue commands from the command line. Auto deploy (autodeploy) When a request is made by HPE OneView, HP SUT stages and deploys the components, but does not activate them. Any further action requires that the user issue commands from the command line. Auto deploy reboot (autodeployreboot) When a request is made by HPE OneView, HP SUT stages, deploys, and reboots the server in order to move the firmware to an active state. HP SUT polls for pending requests from HPE OneView. By default, this polling occurs every five minutes. You can adjust the polling interval in increments of minutes, using the appropriate command line option provided by HP SUT. When running in OnDemand mode, you can write requests to stage and deploy components and reboot as command-line arguments. These command-line arguments are executed directly on the target server as HP SUT stages, deploys, and then reboots the server, based on the commands selected. Table 3 contains an explanation of all of the modes available to HP SUT. NOTE: The mode is set to autodeploy when HP SUT is installed. Use the command line option to change the mode. Table 3 HP SUT modes Mode Stage (components copied local to system) Install (run components, FW/SW installed) Activate (reboot system) OnDemand mode Step initiated by Administrator Step initiated by Administrator Step initiated by Administrator Auto stage mode Step initiated automatically by HP SUT Step initiated by Administrator Step initiated by Administrator Auto deploy mode Step initiated automatically by HP SUT Step initiated automatically by HP SUT Step initiated by Administrator Auto deploy reboot mode Step initiated automatically by HP SUT Step initiated automatically by HP SUT Step initiated automatically by HP SUT 15

16 5 Using HP SUT for Windows and Linux from the command line Running HP SUT from the command line is also referred to as running in OnDemand mode, which is the default mode. OnDemand mode allows you to write requests as command-line arguments on the host server instead of letting the service run automatically in the background. When you use this mode, the activation process only moves forward when you log into the host server and enter an HP SUT command from the command line. You can use the command line to set the SPP to be updated and then use the commands to deploy the SPP on the node. You can also use this mode to stage or deploy the SPP specified by HPE OneView. If the node is managed by HPE OneView, you will not be allowed to set the SPP using the command line. When running in OnDemand mode, HP SUT waits for a user command from the command-line to execute requests, show the help, and check the status of updates. The general command-line syntax for HP SUT is as follows: hpsut [/command] NOTE: For example: On both Windows and Linux, use a slash or hyphen before each argument. hpsut /status hpsut -status Command-line arguments HP SUT recognizes the following command-line arguments: Table 4 HP SUT command line arguments Option /activate /clearstaging /deploy /deployreboot /exportconfig /h[elp] or /? /importconfig Description Used to activate deployed components by rebooting the node if a reboot is required. The command is allowed in the InstalledPendingReboot state. The command asks for user confirmation before rebooting. You can pass the optional parameter force to avoid this confirmation step. The command asks the user for confirmation before rebooting. You can pass the optional parameter force to avoid this confirmation step. Clears everything in the current staging directory. This command is allowed in the InstalledPendingReboot and Activated stages. Deploys files. Performs a reboot after deploying components only if any of the components require a reboot. This option is only available in Auto mode. Uses the config file name as a parameter and writes all HP SUT setting values to the file. This command is allowed in all states. Displays command line help information. Takes the config file name as a parameter and sets all settings per the config file. This command is allowed in the following states: StageFailed InstallFailed Activated 16 Using HP SUT for Windows and Linux from the command line

17 Table 4 HP SUT command line arguments (continued) Option Description ActivatedFailed InstallPending Reboot /pollingintervalinminutes /set /set savelogs=<true false> /set stagingdirectory=<dir_path> /stage /start /status /stop /verify /version Sets the polling interval HP SUT looks at for requests. The default is 5 minutes. Allows you to make changes to different options in HP SUT. Possible values are: -set mode -set stagingdirectory -set rebootmessage -set rebootdelay -set baselineuri Allows you to specify if you want to save generated log files. Allows you to specify the directory in which components are staged. Determines which components need to be applied on the node and copies those components to the stage directory. Starts the HP SUT service if the mode is in AutoStage, AutoDeploy, or AutoDeployReboot. Provides the status of the HP SUT engine depending on the current state. This command can be used by both HPE OneView and OS administrators from the host system where HP SUT is installed. Stops the HP SUT service if it is running. Moves the state to Activated if a reboot has occurred after a deployment. Displays the HP SUT version. Command-line arguments 17

18 6 Using HP SUT for VMware ESXi from the command line HP SUT for VMware ESXi is currently supported in two modes: AutoDeploy, which is a fully automatic mode, and AutoDeployReboot, which requires user intervention to manually perform the reboot. The general command-line syntax for HP SUT for VMware ESXi is as follows: hpsutesxi [/status] NOTE: For example: Use a slash or hyphen before each argument. hpsutesxi /status hpsutesxi -status Command-line arguments Table 5 HP SUT for VMware ESXi command-line arguments Option /help /set /set mode /start /status Description Displays command line help information. Examples: hpsutesxi /help hpsutesxi help Allows you to set HPE OneView and VMware vcenter Server host address, username, and password. Setting OneView details: hpsutesxi set managementhostname=ipaddress_1 managementhostusername=administrator managementhostpassword=******** hpsutesxi /set managementhostname=ipaddress_2 managementhostusername=administrator managementhostpassword=******** Setting vcenter details hpsutesxi set vcenterhostname=ipaddress_1 vcenterusername=administrator@vsphere.local vcenterpassword=********* hpsutesxi /set vcenterhostname=ipaddress_2 vcenterusername=administrator@vsphere.local vcenterpassword=********* Changes the operating mode. Examples: hpsutesxi set mode=autodeploy AutoDeployReboot hpsutesxi /set mode=autodeploy AutoDeployReboot Starts the HP SUT for VMware ESXi service. Example: hpsutesxi start hpsutesxi /start Provides the status of the HP SUT for VMware ESXi engine for ESXi nodes for which a request was received. 18 Using HP SUT for VMware ESXi from the command line

19 Table 5 HP SUT for VMware ESXi command-line arguments (continued) Option Description NOTE: This command gives a summary of all nodes so the output may span many pages. You can use the Linux > command or the >> command to redirect the output to a file to see all of the details. Examples: hpsutesxi /status hpsutesxi -status /stop /version Stops the HP SUT for VMware ESXi service, if it is running. Examples: hpsutesxi stop hpsutesxi /stop Displays the HP SUT for VMware ESXi version. Examples: hpsutesxi /version hpsutesxi -version Command-line arguments 19

20 7 Using HP SUT gatherlogs scripts The gatherlogs.sh and gatherlogs.bat scripts are used to collect logs that are useful for debugging and troubleshooting issues for HP SUT for VMware ESXi and HP SUT for Windows and Linux. HP SUT for Windows To create logs in a Windows environment, use the script gatherlogs.bat, located at C:\Program Files\Hewlett-Packard\HPSUT\bin. HP SUT for Windows collects the logs in a *.zip file. The logs are copied to a different location, depending on the mode used to create the files. OnDemand mode Logs are copied to: C:\Users\Administrator\AppData\Local\hpstut\logs Auto mode Logs are copied to: C: Windows\System32\config\systemprofile\AppData\Local\hpsut\logs If you are unable to find the *.zip file in the above locations, run the gatherlogs.bat script and send the *.zip file created by the script to support. HP SUT for Linux To create logs in a Linux environment, use the script gatherlogs.sh, located at /opt/hp/hpsut/bin. HP SUT for Linux collects the logs and copies the *.tar.gz file to /opt/hp/hpsut/logs. If you are unable to find the *.tar.gz file in that location, run the gatherlogs.sh script and send the *.tar.gz file created by the script to support. HP SUT for VMware ESXi To create logs in the VMware ESXi environment, use the script gatherlogs.sh script, located at /opt/hp/hpsutesxi/bin. HP SUT for VMware ESXi collects logs and copies the *.tar.gz file to the /opt/hp/hpsutesxi/logs folder. If you are unable to find the *.tar.gz file in the /opt/hp/hpsutesxi/logs folder, run the gatherlogs.sh script and send the *.tar.gz file created by the script to support. 20 Using HP SUT gatherlogs scripts

21 8 Troubleshooting Troubleshooting for HP SUT for Windows and Linux HP SUT Self Update fails on a TPM-enabled machine Symptom If a Trusted Platform Module (TPM) is present and enabled on the server, the Self Update operation that uses a custom baseline fails. StageFailed appears as the Deploy Status. Cause This behavior occurs if the following conditions are true: The server has TPM enabled. HP SUT installed. The HP SUM version in the baseline is not equal to Solution Create a custom baseline with HP SUM to upgrade. Update HP SUT to outside the SPP by running the component manually. Disable the TPM and use the baseline with HP SUM or later. Could not clear staging directory Symptom During staging, the ClearStagingFailed error appears. Cause Failure could be due to one or both of the following reasons: There are no execution permissions on the directory/file. The staged files are used by other processes. Solution 1. Make sure the staging directory has write permissions and that previously staged files are not used by another application. 2. Retry the operation. 3. If the problem persists, contact your authorized support representative and provide them with a support logs/dump. Baseline URI provided is invalid Symptom While attempting to mount the specified baseline ISO, the baseline URI link provided was found to be invalid. Cause Either the URI specified does not have an ISO extension or the protocol is not HTTP or HTTPS. SolutionResubmit the request with a valid accessible URI to a baseline ISO image. Insufficient disk space to copy the files Symptom The available disk space is less than the required space to copy the files. Action Free disk space on the drive where the staging directory is located, and retry the staging operation. Unable to mount baseline ISO through ilo Virtual Media Symptom Mounting the specified baseline ISO through ilo Virtual Media failed. Troubleshooting for HP SUT for Windows and Linux 21

22 Cause Failure may be caused by one or more of the following reasons: The baseline is not accessible. The HTTP server hosting the baseline ISO is busy. An HPE ilo Advanced license is not installed. Solution 1. Check whether any other baseline ISO is already mounted through ilo Virtual Media. 2. Install an HPE ilo Advanced license. 3. Verify the provided URI for accessibility. 4. Retry the operation. 5. If the problem persists, contact your authorized support representative and provide them with a support logs/dump. The concurrent download limit of the baseline ISO has been reached or the baseline provided is not detected as a supported baseline Symptom The URI provided is not detected as a supported baseline ISO. Cause The failure may be caused by the following reasons: The concurrent download limit of the baseline has been reached due to other ongoing firmware updates. The directory contents does not match with the SPP structure. Solution If the baseline ISO mounted is an SPP, retry the request later, or resubmit the request with a valid link to a supported baseline ISO image. HP SUM execution failed Symptom HP SUM binary failed to execute. Cause Failure may be caused by more of the following reasons: HP SUM binary does not exist in the staging location. HP SUM binary does not have the appropriate permissions. HP SUM encountered a failure during the execution. Solution 1. Make sure HP SUM binaries are available in the staging directory with the appropriate permissions. 2. Clear %temp%\\hpsum and %systemdrive%\\windows\\temp\\hpsum (Windows) and /tmp/hpsum (Linux) directory. 3. Resubmit the request. 4. If the problem persists, contact your authorized support representative and provide them with a support logs/dump. Baseline inventory operation failed Symptom HP SUM inventory has failed. Cause Failure may be caused by one or more of the following reasons: HP SUM failed to start. HP SUM report generation failed. The report does not have the data to complete the inventory operation. Solution 22 Troubleshooting

23 1. Configure HP SUM to run using different ports if the ports are already in use. 2. Clear the following: Windows: %temp%\\hpsum and %systemdrive%\\windows\\temp\\hpsum Linux: /tmp/hpsum 3. Resubmit the request. 4. If the problem persists, contact your authorized support representative and provide them with a support logs/dump. Deployment operation failed Symptom Firmware/Driver/Software deployment has failed. Cause Failure may be caused by one or more of the following reasons: HP SUM failed to start. Deployment of one or more smart component updates has failed. The report does not have the data to complete the deployment. Solution 1. Verify whether the ports used for HP SUM are occupied. 2. Configure HP SUM to run using different ports if the ports are occupied. 3. Clear the following: Windows: %temp%\\hpsum and %systemdrive%\\windows\\temp\\hpsum Linux: /tmp/hpsum 4. Resubmit the request. 5. If the problem persists, contact your authorized support representative and provide them with a support logs/dump. Version of HP SUM in the baseline ISO is lower than Symptom Version of HP SUM in the baseline ISO is lower than Solution Use the Baseline URI with HP SUM or later. Retry the operation. Staging directory is improper Symptom HP SUT is unable to trigger the deployment. Cause Failure may be caused by one or both of the following reasons: The staging directory is deleted. The staging directory is not accessible. Solution 1. Verify that the staging directory is accessible. 2. If the provided staging directory is a network-mounted disk, ensure that it is available during deployment. 3. Resubmit the request. Staging directory creation failed Symptom While staging, the creation of staging directory failed. Cause Failure may be caused by incorrect permissions. Solution Ensure that the directory where the staging directory is being created has write and execute permissions. Perform stage operation after providing sufficient permissions. Troubleshooting for HP SUT for Windows and Linux 23

24 Reboot command failed Symptom After initiating reboot during activation, the reboot of the server failed. Solution Reboot the server using OS commands. Operation request was changed unexpectedly while processing another request Symptom HP SUT operation request is changed by an external client. Solution Resubmit the request, and ensure that one request processes completely before submitting another. Failed to copy file during staging Symptom HP SUT encountered a failure during staging. Cause This failure may be caused by one or both of the following reasons: The component is not available in the baseline ISO. The HTTP ISO location is no longer accessible. Solution 1. Verify that the component being staged is present in the baseline ISO. 2. Ensure that the baseline ISO is available over HTTP for the duration of the stage. 3. Resubmit the request. Staging or deployment failed due to unknown error Symptom Staging or deployment failed due to an unknown error. Solution Retry the operation. If the problem persists, execute gatherlogs and collect the HP SUM and HP SUT support logs, contact your authorized support representative, and provide them with the support logs. HP SUT does not understand the baseline request from HPE OneView Symptom The baseline request from HPE OneView contains data that HP SUT does not understand. Solution Make sure that the version of HPE OneView managing the server is compatible with the installed version of HP SUT. Media browse window appears after mounting the Virtual Media Symptom After mounting the Virtual Media in Linux, the Linux media browse window opens. Cause Since the mounted location is now accessed, the unmount command will fail. This is OS-specific behavior. Solution In the File Management Preferences window that displays, clear the Browse media when inserted checkbox, and close the window. Troubleshooting for HP SUT for VMware ESXi HP SUM baseline validation failed Symptom Validation on downloaded baseline components failed. Cause This can be caused by one or both of the following reasons: The staging directory is read-only. Component download failed due to network issues. Solution 24 Troubleshooting

25 1. Ensure that the staging directory has write permissions. 2. Ensure the network connection is stable during the download. 3. Resubmit the firmware deployment request. HP SUM binary download failed Symptom The download of HP SUM files failed. Solution 1. Ensure the network connection is stable during the download. 2. Resubmit the firmware deployment request. SPP folder creation failed Symptom Folder creation to download baseline components failed. Cause This may be caused by a permissions issue. Solution Ensure that the staging directory has write permissions. Resubmit the firmware deployment request. Reboot command execution failed Symptom There was a problem sending server reboot request to ilo. Solution Reboot the server using another method, or resubmit the firmware deployment request. ilo version mismatch Symptom The ilo 4 firmware version is less than the required minimum version Solution Upgrade the ilo 4 firmware version to 2.30 or later. ESXi target moves to Installfailed state when updating HP SUT through HPE OneView Symptom HP SUT is stuck at installing if you have HP QLogic NX2 Online Firmware Upgrade Utility for VMware. Solution Create a custom baseline to remove the QLogic component. 1. Create a custom baseline using corresponding versions of HP SUM and SPP supported by HP SUT, such as HP SUM and SPP Remove the existing QLogic card component. NOTE: If you are using the extracted path, remove the HP QLogic NX2 Online Firmware Upgrade Utility for VMware component (CP zip) from the temporary directory before launching HP SUM. If you are using the mount location, deselect the CPO26245.zip component. 3. Update the card using the latest component. Make sure to update the component number. Troubleshooting for HP SUT for VMware ESXi 25

26 Tips for detecting vcenter Server and HPE OneView connection failure Management software/vcenter relationship and connection status is displayed by the status command. Success: ConnectionSuccess Failure: ConnectionFailed If the vcenter Server credentials entered are incorrect, the following response is displayed: Failed to connect to vcenter Server. <Incorrect credentials are provided. Please enter the correct credentials.> If the vcenter Server is not reachable over the network, the following response is displayed: Failed to connect to vcenter Server. <vcenter server is unreachable over the network. Ensure that IP assigned to the vcenter server is reachable.> If the Management appliance credentials entered are incorrect, the following response is displayed: Failed to connect to Management appliance. <Incorrect credentials are provided. Please enter the correct credentials.> If the Management appliance is not reachable over the network, the following response is displayed: Failed to connect to Management appliance. <Management appliance is unreachable over the network. Ensure that IP assigned to the Management appliance is reachable.> For HP SUT for VMware ESXi, the size of the HP SUM files and VMware components are approximately 1 GB. If the HP SUM files or components cannot be downloaded because of low disk space, examine the size of the staging directory. Delete the old SPPs and unused SPPs from the staging directory. HP SUT does not automatically manage SPPs. Manual deletion is required. 26 Troubleshooting

27 9 FAQs Does HP SUT need to be installed on every server? Yes, it must be installed on every server that you want to manage with HP SUT. Where can I download HP SUT components? The HP SUT Windows and Linux versions are available from the support center with links from the SUT product page: They are distributed as separate.exe files or as.rpm downloads. Are there any requirements to use HP SUT? ilo Advanced license 2.3 or later, HP SUM or later, and HPE OneView 2.0 or later. How do I change from Auto mode to OnDemand mode? Use this command: HPSUT -set mode=ondemand How do I set a new baseline URI? For HP SUT for Windows and Linux, enter: hpsut -set baseleineuri=<http url of SPP ISO> or hpsut /set baselineuri=<http url of SPP ISO>. For HP SUT for VMware ESXi, enter: hpsutesxi -set baselineuri=<http url of SPP ISO> or hpsutesxi /set baselineuri=<http url of SPP ISO> NOTE: All set commands are in this format: command set parameter. After the command completes, you see the next action you can perform. Generally, the next action is to stage the components to the staging directory. If the command does not complete, a message appears that the command did not complete, followed by a reason for the failure. As the OS administrator, how do I review the deployed contents? Use the hpsut status command, which displays a list of all files. This includes any failed dependencies and whether a reboot is required after the deployment. After the status command finishes, any required user actions are also listed. This includes the executedeploy or the deployreboot commands to deploy components. As an OS administrator, how do I stage the firmware and driver updates for a specific SPP? Use the hpsut stage command. This command first clears the staging directory and then mounts the ISO through the ilo Virtual Media. This procedure may take a few minutes as it copies the information from the ISO to the staging location. After the copy procedure finishes, HP SUT analyzes the applicable components and displays a lists of all components to be applied. These components are also copied to the staging directory. I am in maintenance mode. How do I deploy the updates that I staged earlier? Use the hpsut deploy command. HP SUT then calls HP SUM. After the deployment is complete, you can obtain a log file from the location that appeared on the screen during the deployment. How do I perform the firmware and driver update if I have set up an http SPP ISO URI? Use the following commands: Hpsut set baselineuri=<http_path_to_iso> Hpsut stage Hpsut deploy Hpsut -activate 27

28 10 Support and other resources Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: Information to collect Technical support registration number (if applicable) Product name, model or version, and serial number Operating system name and version Firmware version Error messages Product-specific reports and logs Add-on products or components Third-party products or components Accessing updates Websites Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method. To download product updates, go to either of the following: Hewlett Packard Enterprise Support Center Get connected with updates page: Software Depot website: To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements. Website Hewlett Packard Enterprise Information Library Hewlett Packard Enterprise Support Center Link Support and other resources

29 Website Contact Hewlett Packard Enterprise Worldwide Subscription Service/Support Alerts Software Depot Customer Self Repair Insight Remote Support Link Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR. For more information about CSR, contact your local service provider or go to the CSR website: Remote support Remote support is available with supported devices as part of your warranty or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support. For more information and device support details, go to the following website: Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Customer self repair 29

30 Index A accessing updates, 28 auto deploy, 15 auto deploy reboot, 15 auto stage, 15 automated compliance reporting, 5 C CLI, 5, 6, 16, 18 command-line arguments, 16, 18 command-line interface, 16, 18 contacting Hewlett Packard Enterprise, 28 customer self repair, 29 D documentation providing feedback on, 29 downloading HP SUT for VMware ESXi, 13 HP SUT for Windows and Linux, 7 driver updates, 5 dual boot HP SUT for Windows and Linux, 7 E ESXi, 5, 13 F FAQs, 27 features, 5 firmware and driver activation, 5 firmware and driver updates, 5 firmware updates, 5 G gatherlogs, 20 H Hewlett Packard Enterprise SDR, 7 Hewlett Packard Enterprise website, 7 HP SUM, 5 HP SUT, 5 auto mode, 6 debugging, 20 operating modes, 6 HP SUT features, 5 HP SUT for VMware ESXi, 5, 18 HP SUT for Windows and Linux, 5, 16 HP SUT products, 5 I ilo firmware, 7 ilo management network, 5 installing HP SUT for VMware ESXi, 13 HP SUT for Windows and Linux, 7 introduction, 5 L launching HP SUT for VMware ESXi, 13 HP SUT for Windows and Linux, 7 Linux build plan, 7 Linux RPM, 5, 13 M maintenance window, 5 O ondemand, 15, 16, 18 ondemand mode, 6 OneView, 5, 13, 15 OneView dashboard, 5 operating modes auto deploy, 15 ondemand, 15 R reboot, 5 remote support, 29 removing HP SUT for Windows and Linux, 7 S scripts, 20 Smart Update Tools, 5 SPP, 16 support Hewlett Packard Enterprise, 28 system uptime, 5 T troubleshooting, 21 baseline inventory operation failed, 22 baseline URI invalid, 21 clear staging directory, 21 create staging directory, 23 deployment failed due to unknown error, 24 deployment operation failed, 23 detecting vcenter connection failure, 26 ESXi target fails, 25 failed to copy file during staging, 24 for HP SUT for VMware ESXi, 24 for HP SUT for Windows and Linux, 21 HP SUM baseline, 23 HP SUM baseline validation failed, 24 HP SUM binary download failed, 25 HP SUM execution failed, 22 HP SUM lower than 7.4.0, 23 ilo version mismatch, 25 ilo Virtual Media, 21 improper staging directory, 23 Installfailed state, Index

31 insufficient disk space, 21 media browse window displays, 24 mount baseline ISO, 21 OneView connection failure, 26 OneView request not understood, 24 operation request changed unexpectedly, 24 reboot command execution failed, 25 reboot command failed, 24 SPP folder creation failed, 25 staging failed due to unknown error, 24 URI not supported baseline ISO, 22 U updates accessing, 28 V vcenter, 13 verifying HP SUT for Windows and Linux, 7 VMware, 13 W websites, 28 customer self repair, 29 Windows and Linux, 7 Windows smart component, 5 31