HITACHI HA810 G3 Series Advanced Server User Guide

HITACHI HA810 G3 Series Advanced Server

Product Information

Specifications:

• Product: Hitachi Advanced Server HA800 G3 Series
• Tool: Integrated Smart Update Tools
• Compatibility: Microsoft Windows, Windows Server, Linux, VMware, Service Pack for Hitachi Vantara (SPV), and Smart Components
• Document Number: MK-90HAS8016-01
• Publication Date: June 2023

Product Usage Instructions:

Introduction:
The Integrated Smart Update Tools are designed to update firmware and operating system drivers on HA800 G3 servers. This guide is for users familiar with Microsoft Windows, Windows Server, Linux, VMware, SPV, and Smart Components configurations.

Software Responsibility:
When using this software, ensure that you have the necessary consent as per local privacy laws and verify that your data handling complies with relevant regulations.

Export Controls:
Be aware of U.S. export control laws and other export/import regulations when dealing with the technical data and technology in this document. Compliance is essential.

FAQ:

• Q: What should I do if the features described in the Materials are not available?
  A: Refer to the most recent product announcement for updated information on feature availability or contact Hitachi Vantara LLC for assistance.

• Q: How can I order Hitachi products and services?
  A: Hitachi products can be ordered only under the terms and conditions of applicable agreements with Hitachi Vantara LLC.

• Q: Where can I find copyright and license information for third-party software used in Hitachi Vantara products?
  A: You can find the necessary details in the product documentation or on the Hitachi Vantara website.

Hitachi Advanced Server HA800 G3 Series

Integrated Smart Update Tools User Guide
This document describes how to use Integrated Smart Update Tools to update firmware and operating system drivers on HA800 G2 servers. This document is intended for individuals who understand the configuration and operations of Microsoft Windows, Windows Server, Linux, VMware, Service Pack for Hitachi Vantara (SPV), and Smart Components.

© 2007, 2023 Hitachi Vantara LLC. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Vantara LLC (collectively “Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials.
“Materials” means text, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication. Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about features and product availability, or contact Hitachi Vantara LLC at https://support.hitachivantara.com/en_us/contact-us.html.

Notice:
Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi Vantara LLC.

By using this software, you agree that you are responsible for:

1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals; and
2. Verifying that your data continues to be held, retrieved, deleted, or otherwise processed by relevant laws.

Notice on Export Controls
The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/ 390, PowerHA, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z14, z15, z16, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, Microsoft Edge, the Microsoft corporate logo, the Microsoft Edge logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screenshots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Copyright and license information for third-party and open-source software used in Hitachi Vantara products can be found in the product documentation, at https://www.hitachivantara.com/en-us/company/legal.html or https://knowledge.hitachivantara.com/Documents/Open_Source_Software.

Preface

This document describes common procedures and solutions for the many levels of troubleshooting servers. This document is intended for the person who installs, administers, and troubleshoots servers and server blades. Hitachi Vantara assumes you are qualified to service computer equipment and are trained in recognizing hazards in products with hazardous energy levels. Please read this document carefully to understand how to use these products, and maintain a copy for your reference.

Accessing product documentation
Product user documentation is available on Hitachi Vantara Support Connect: https://knowledge.hitachivantara.com/Documents. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Getting help

• Hitachi Vantara Support Connect is the destination for technical support of products and solutions sold by Hitachi Vantara. To contact technical support, log on to Hitachi Vantara Support Connect for contact information: https://support.hitachivantara.com/en_us/contact-us.html.
• Hitachi Vantara Community is a global online community for Hitachi Vantara customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hitachivantara.com, register, and complete your profile.

Comments

Please send us your comments on this document to doc.comments@hitachivantara.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Vantara LLC.

Thank you!

Introduction

Integrated Smart Update Tools
Integrated Smart Update Tools (iSUT) is the smart update solution for performing online firmware and driver updates. iSUT is used with iLO 5, iLO6, and with update solutions (management appliances such as Smart Update Manager to stage, install, and activate firmware and driver updates.

The solution must be installed on the operating system, where it updates results through Rich Infrastructure Services (RIS) communication.

• iSUT: Polls iLO to check for requests from SUM, Compute Ops Management for updates through local iLO using the iLO channel interface driver installed on the OS and orchestrates staging, deploying, and activating updates. You can adjust the polling interval by issuing the appropriate command-line option provided by iSUT. Performs inventory on target servers, stages deployment, deploys updates, and then reboots the servers.
• iLO 5/iLO 6 with integrated Smart Update (G2 or later servers only): Performs iLO Repository-based updates by downloading the components from iLO Repository when iLO Installation Queue has the components which can be updated by iSUT .
• SUM: A tool for firmware and driver maintenance for Hitachi Advanced servers and associated options.

NOTE: SUM should not manage the same nodes.

Platform support

Operating System/Version supported

• Windows Integrated Smart Update Tools 4.0.0 for Windows
• Linux Integrated Smart Update Tools 4.0.0 for Linux
• VMware ESXi Integrated Smart Update Tools 4.0.0 for VMware ESXi

iSUT operating modes
iSUT runs in the following modes:

• OnDemand mode: This is the CLI-based mode in which every action must be triggered by a user action. OnDemand mode enables the administrator user to write commands in the CLI window that:

  • Stage updates
  • Deploy updates
  • Reboot servers
    You can set the mode to OnDemand using the sut -set mode=OnDemand command.

• Auto/Service mode: This is the automatic mode of update where the user can set the correct mode and polling interval time. After the mode and polling interval time is set, iSUT periodically polls the RIS for a new request. After the request is received,iSUT performs the updates automatically.
  iSUT runs in the following Auto/Service modes:

  • AutoStage
  • Mounts the SPV through iLO Virtual Media.
  • Uses SUM present in the SPV to inventory the server.
  • Copies the applicable components from the SPV to the server for deployment.

NOTE:
AutoStage mode is the default mode for G2 and Gen11 servers. This mode can be used to stage the components before installing firmware.
For installing and activating the staged firmware, a deploy-reboot command must be issued through the iSUT CLI. Alternatively, the iSUT mode must be changed to an AutoDeploy or an OnDemand mode and then a command must be issued through the CLI.

• AutoDeploy

  • Performs all the tasks in AutoStage mode.
  • Updates the applicable components found in the iSUT staging directory on the host server.
    NOTE: Components updated by iSUT in iLO Repository-based updates are downloaded to the iSUT staging directory before updating.

• AutoDeployReboot

  • Performs all the tasks in AutoDeploy mode.
  • If required, reboot the host server.

NOTE: For VMware ESXi, the server must be in Maintenance mode.

NOTE:
If the deployment succeeds, iSUT verifies the updates by default. Use the command sut /deploy noautoverify to prevent the default verification. This is not applicable for iLO Repository-based updates.

• You can set the mode to Auto/Service mode by using the command sut -set mode=AutoStage/AutoDeploy/ AutoDeployReboot.
• Use the status command to view which mode iSUT is running.

iLO Repository-based update options
iLO Repository-based update options are available on G2 and Gen11 servers. Smart update solutions such as SUM can use this mechanism to update servers. This update option needs Agentless Management Service (AMS) to be installed on the target server on which iSUT is installed.

NOTE:
For more information, contact customer support on the Hitachi Advanced Server HA800 G3 Series Smart Update Manager 10.0.0 User Guide.

Dual boot environment notes

• If you have an environment where servers boot to both Windows and Linux operating systems.
• If you run iSUT in one operating system and then are going to run it in another, change the staging directory to the correct path. Use the following command: sut -set stagingdirectory=

IMPORTANT: iSUT requires permission to write to the staging directory.

ESXCLI extension for remote execution
Use ESXCLI extension feature to run iSUT OnDemand commands remotely using ESXCLI (ESXi 7.x / ESXi 8.x).

iSUT ESXCLI extension advantages
On using iSUT ESXCLI extension, you are not required to:

• Log into each remote ESXi host individually to execute command.
• Enable SSH on each of the remote ESXi hosts.
• Run same set of commands manually on each server. A script file can be used to run the supported iSUT commands.

NOTE:
For more information, Contact customer support on supported CLI commands with ESXCLI extension.

Downloading iSUT

• iSUT is available on Windows, Linux and ESXi for G2, and Gen11 systems. This iSUT is part of the Service Pack for Advanced Server. Each SPV contains a contents.html, which can be looked up using the substring Integrated Smart Update Tools to find the iSUT component part of the SPV.
• If you are downloading an older SPV, you can download the latest iSUT version through the product downloads page.
• Contact customer support to Download iSUT.

Downloading iSUT RPM keys

Procedure
Contact customer support

Installing iSUT for Windows and Linux

iSUT installation

• iSUT must be installed manually the first time. Ensure that every Windows or Linux system on which SPV must be applied has iSUT installed.
• After you install iSUT, the default mode of iSUT is as follows:

Server generation/Default mode

G2 and Gen11/AutoStage
During every SPV upgrade, iSUT self-upgrades itself if the version of iSUT found in SPV is higher. During Self-Upgrade, iSUT configurations such as mode are retained (except for OnDemand mode in G2 and Gen11 servers).

• Server generation
  G2 and Gen11

• Current Mode (Before Self-Upgrade)
  OnDemand

• New Mode( after Self-Upgrade)
  AutoStage

NOTE:

• If Server is in Auto (AutoStage/AutoDeploy/AutoDeployReboot) mode before self upgrade, mode will be retained after self upgrade for all generations.
• You can change the iSUT mode to a mode of your choice after a successful iSUT installation. To do so use the following command: sut–set mode=<OnDemand/AutoStage/AutoDeploy/AutoDeployReboot>

iSUT installation for Windows

To install iSUT on Windows, perform the following steps:

1. Download the Smart Component (cpxxxxxx.exe) file to a local directory on the server where you want to install the software.
2. Change to the directory.
3. Run the .exe file by double-clicking it. A dialog box appears.
4. Click the Install button to install iSUT.

iSUT installation for Linux

Prerequisites

• Linux OS configuration is required.
• Directories /tmp and /var/tmp/sut must have exec permission.
• If you are mounting file systems to the /tmp or /var/tmp/sut directories, you must mount them as read/write.

To install iSUT on Linux, use the following command:

• rpm -ivh /sut-.linux.x86_64.rpm
• NOTE: For more information, contact customer support on Linux systems, you can also install iSUT using the repository.

Configuring iSUT components
While installing on Windows and Linux systems, you can configure iSUT using the following methods. On G2 and Gen11 ESXi systems, you must log into the system and run the iSUT commands to configure polling interval, staging directory or mode of operation. For more information on selecting the iSUT mode of operation, see iSUT operating modes.

Method 1

1. Run SUM and set the mode to one of the auto modes (AutoStage/AutoDeploy/AutoDeployReboot) on the Baseline configuration page.
2. Export the configuration details to a directory.
3. Use this configuration file and run the component independently by passing the /config_file option:
   • For Windows: Use the command, cpxxxxxx.exe /silent /config_file C:\temp\cpxxxxxx_conf\sut_cfg.dat.
   • For Linux: Copy the sut_cfg.dat file to /usr/local/hp/ directory and run the install command.

Method 2

1. Extract the component to a directory.
2. Copy sut_cfg.dat to a different directory.
3. Edit the file to set the mode to one of the automodes.
4. Use this configuration file and run the component independently by passing the /config_file option:
   • For Windows:
   • Use the command, cpxxxxxx.exe /silent /config_file C:\temp\cpxxxxxx_conf\sut_cfg.dat.
   • For Linux:
   • Extract the RPM using the command: rpm2cpio sut--.linux.x86_64 | cpio –id
   • Edit the sut_cfg.dat file and copy it to the /usr/local/hp/ directory and run the install command.

Configuring iSUT for High Security/CNSA/FIPS

Prerequisite
iLO must already be set in one of the modes: High Security/CNSA/FIPS

Procedure

1. Provide the iLO credentials to iSUT using the following command: sut -set ilousername=<> ilopassword=<>
2. Change the iSUT mode to the requisite mode.
3. Initiate updates.

NOTE:
Required Host Authentication must be enabled to enforce authentication using certificates or iLO credentials.

Configuring iSUT when CAC Smartcard Authentication is enabled in iLO

Prer equisite

• If iLO enables CAC Smartcard Authentication, iSUT can communicate with iLO using a certificate, credentials, or any other authentication methods.
• If iLO enables Strict CAC, iSUT can communicate with iLO only using certificates.

NOTE:
For more information, see CAC Smartcard Authentication in the iLO User Guide. posted at https://knowledge.hitachivantara.com/Documents/Servers.

Procedure

1. Provide the iLO certificate to iSUT using the command sut -add certificate .
   If iSUT locates the file and successfully adds it, it queries for a private key value. Provide the following information:

   • Enter private key path.
   • Does the private key have an associated password (yes/no)?
   • Enter a private key password.

2. Change the iSUT mode to the requisite mode.

3. Initiate updates.

NOTE:
Required Host Authentication must be enabled to enforce authentication using certificates or iLO credentials.

Installing iSUT with the SUM GUI (Windows/Linux)

Prerequisites
Directory with the iSUT components.

About this task
You can also use the SUM CLI and CLI with Input File modes to install iSUT. For more information on using SUM, contact customer support for the SmartUpdate Manager 10.0 CLI Guide.

Procedure

1. Launch SUM in GUI mode.
2. On the Baseline Library screen, add a baseline, and then map to the directory that contains the configured iSUT components.
3. On the Nodes Library screen, add the nodes where you are installing iSUT and assign the baseline with the iSUT components.
4. On the Nodes Library screen, perform inventory on the nodes where you are installing iSUT.
5. Install the components.

Verifying iSUT installation

Procedure

Issue the following command on the host:
sut -status

If iSUT is installed, the command output displays iSUT settings, such as mode of update and polling interval.

Setting the staging directory

About this task
If you do not want to use the default iSUT staging directory, issue the following command to assign the staging directory.

Procedure

1. Open a command-line window.
2. Enter the command /set stagingdirectory= (Window/Linux/VMware ESXi).

iSUT creates a backup configuration file that iSUT can use in future sessions.

Reinstalling iSUT with the SUM GUI

Prerequisites
Directory with iSUT components configured.

About this task
You can reinstall iSUT with SUM and overwrite the currently installed version of iSUT. You can reinstall iSUT to change the configuration for multiple servers at the same time.

Procedure

1. Launch SUM in GUI mode.
2. On the Baseline Library screen, add a baseline, and then map to the directory that contains the configured iSUT components.
3. On the Nodes Library screen, add the nodes where you are installing SUM and assign the baseline with the iSUT components.
4. On the Nodes Library screen, perform inventory on the nodes where you are installing iSUT.
5. Install the components. Use the Advanced Deployment mode and Force the component updates.

Installing iSUT for VMware ESXi

Installing iSUT VMware ESXi

About this task

NOTE:
You can also install iSUT on VMware ESXi using VMware Update Manager (VUM). For more information, contact customer support

Procedure

1. Extract the bundle from the iSUT component (cpxxxxxx.zip).
2. Copy the iSUT bundle (sutComponent_..zip) to the VMware ESXi system.
3. Install the iSUT bundle on the VMware ESXi host—esxcli software component apply -d .
4. Reboot the VMware ESXi host.
5. To clear the iLO settings used by the earlier iSUT installation, execute the sut -deregister command.
6. Set the iSUT mode using the OnDemand command, sut -set mode=<OnDemand/AutoDeploy/ AutodeployReboot>.

NOTE:

• You can set the iSUT mode to AutoDeployReboot mode. However, iSUT reboots the VMware ESXi host only if the host is in Maintenance mode. To set the VMware ESXi host in Maintenance mode, run the command esxcli system maintenance mode set -e true on the VMware ESXi host.
• When using the latest VMware OS image, iSUT gets pre-installed on the OS. If iSUT is already present, you can proceed from Step 5 directly.
• AutoStage mode is the default mode for G2 and Gen11 servers.

During every SPV upgrade, iSUT self-upgrades itself if the version of iSUT found in SPV is higher. During Self-Upgrade, iSUT configurations such as mode are retained (except for OnDemand mode in G2 and above servers).

• Server generation
  G2 and Gen11

• Current Mode (Before Self-Upgrade)
  OnDemand

• New Mode (after Self-Upgrade)
  AutoStage

NOTE:

• If the Server is in Auto (AutoStage/AutoDeploy/AutoDeployReboot) mode before self-upgrade, the mode will be retained after self-upgrade for all generations.
• You can change the iSUT mode to a mode of your choice after a successful iSUT installation. To do so use the following command:
  sut -set mode=<OnDemand/AutoStage/AutoDeploy/AutoDeployreboot>

Installing VMware software Smart Components

Installing VMware software Smart Components on G2 or above using SUM and iSUT

To install the VMware ESXi software bundle Smart Components on G2 or above servers, you must configure the ESXi host with iSUT.

Starting Configuration
Install the custom image for the required version of VMware ESXi.

Set up the ESXi host with iSUT

1. Install the appropriate iSUT component.
   NOTE: Currently, the iSUT products are smart components that do not unzip correctly on the ESXi platform. Unzip the Smart Component in Linux or uncompress them on Windows.

2. After you unzip the smart component to extract the sutComponent..zip file, copy the sutComponent..zip file to the ESXi platform, and then install the component: esxcli software component apply -d <sutComponent_..zip>

3. Reboot the server.

4. If you want iSUT to run in Automode, change the mode to one of the auto modes. For example, sut –set mode=autodeployreboot.

Setup and execute the test using SUM

1. Get the appropriate SPV file.

2. If you are hosting the SPV on a Windows 10 environment, right-click the file, and then mount the *.iso.
   NOTE: If you are not hosting the SPV on a Windows 10 environment, use Virtual CloneDrive to mount ISOs.

3. Navigate to the folder that has the SPV files mounted, and then click launch_sum.bat. The SUM GUI screen appears.

4. Click Baseline Library at the upper-left corner of the SUM GUI.

5. To add a baseline package, click Add Baseline in the top-left pane. The Add Baseline Options screen appears.

6. Click Add Baseline in the pop-up window. The Add Baseline screen appears.
   NOTE: You must have both the cp.zip and cp.compsig files for the smart component available in the same location as the smart components.

7. Click Add. The “Additional package” gets added with a list of the smart components found at the location you specified.
   NOTE: Use the “Additional package” as your baseline if you want to test the installation of the new components. You can test the installation by adding nodes.
   For G2 or above servers, add an iLO node (use iLO IP for a requested IP address).

8. Select Smart Update Manger in the top-left corner of the GUI, and then click Nodes. SUM starts performing “discovery” actions.

After adding a node, you can perform an inventory, and then deploy the smart components.

NOTE:
For more information, contact customer support on Hitachi Advanced Server HA800 G3 Series Smart Update Manager 10.0.0 User Guide.

iSUT log files

About log files
iSUT automatically saves the logs after:

• Deploying updates
• Staging updates
• Verifying updates

iSUT saves the log files in the following location:

• Linux: /var/tmp/sut
• Windows:
  • OnDemand mode: C:\Users\Administrator\AppData\Local\sut\logs
  • Auto mode: C:\Users\System32\config\systemprofile\AppData\Local\sut\logs
• VMware ESXi: /opt/sut/tmp

Collecting log files

Procedure

• Use one of the following commands:
  • Windows: C:\Program Files\SUT\bin\gatherlogs_x64.exe
  • Linux: /opt/sut/bin/gatherlogs.sh
  • VMware ESXi: /opt/sut/bin/gatherlogs.sh

Uninstalling iSUT

Uninstalling iSUT in Windows

Procedure

1. On your Windows server, open Programs and Features.
2. Select Integrated Smart Update Tools for Windows, and then click Uninstall.

Uninstalling iSUT in Linux

Procedure
Use the following command to uninstall: – rpm –e sut

Uninstalling iSUT in VMware ESXi

About this task

Procedure

1. Execute the sut -deregister command.
2. Execute the sut-clearilocreds command only if iLO is configured in a High-Security mode, such as FIPS.
3. Use the following command to uninstall iSUT:
   VMware ESXi 7.x / VMware ESXi 8.x: esxcli software component remove -n sutComponent

iSUT troubleshooting

Baseline URI not Detected as a Supported Baseline

• Symptom
  The URI provided is not detected as a supported baseline ISO.

• Cause
  The directory contents do not match the SPV structure.

Action

1. Verify that the SPV ISO is valid.
2. Reissue the request.

iSUT installs a CHIF driver by default (Windows only)

• Symptom
  iSUT installs an iLO Channel Interface (CHIF) driver on the Windows system if you do not select it for installation.

• Cause
  iSUT requires the CHIF driver to perform tasks.

• Action
  No action.

Cannot clear the iSUT staging directory

Symptom
While staging components, iSUT cannot clear the staging directory.

Solution 1

• Cause
  The user does not have execution permissions for the directory or file.

• Action
  Make sure that the administrator has write permissions for the directory.

Solution 2

• Cause
  Other processes are using the staged files.

• Action
  Verify that other processes are not using the staged files.

iSUT is installed, but does not issue commands

• Symptom
  iSUT installed succeeds, but commands do not function.

• Cause
  A user account without administrator or root user privileges installed iSUT.

• Action
  Uninstall iSUT and reinstall with an administrator account or root user.

iSUT does not recognize a configuration file

• Symptom
  iSUT does not recognize the specified configuration file.

• Cause
  The path to the configuration file includes spaces.

• Action
  Remove all empty spaces from the directory path to a configuration file.

iSUT cannot stage files

Symptom
iSUT cannot stage files.

Solution 1

• Cause
  iSUT files require more space than is available on the disk.

• Action
  Clear disk space on the staging drive and retry the staging operation.

Solution 2

• Cause
  The component is not in the baseline SPV.

• Action
  Verify that the component is in the baseline SPV.

Solution 3

• Cause
  SPV fails security validation on Windows.

• Action
  Update the Windows root certificates. Manually update the GlobalSign Root CA and AddTrust External Root CA certificates.

iSUT cannot mount baseline ISO through iLO Virtual Media

Symptom
Mounting the baseline ISO through the iLO Virtual Media failed.

Cause

• The baseline is not accessible.
• The HTTPS server hosting the baseline ISO is busy.
• There is no iLO Advanced license installed.

Action

1. Check to see if another baseline ISO is already mounted through iLO Virtual Media.
2. Verify that an iLO Advanced license is installed.
3. Verify that the staging directory URI is accessible.
4. Retry the operation.

iSUT cannot start deployment

Symptom
iSUT cannot deploy updates.

Solution 1

• Cause
  The staging directory is not accessible or has been deleted.

• Action
  Verify that the staging directory is valid.

iSUT cannot reboot a server

• Symptom
  iSUT cannot reboot a server after deploying updates to the server.

• Action
  Manually reboot the server.

Components in an iLO installation queue are marked as Exception

Symptom
iSUT marks the component state in the iLO installation queue as an Exception with the message ID as InvalidFile.

Cause

• This can occur if the component signature is not imported into the RPM database.
• Windows certificates are not current.

Action

1. Make sure that the certificates are up-to-date on the system.
   • Linux: contact customer support to Import the rpm keys.

iSUT does not launch SUM

Symptom
SUM does not execute.

Solution 1

• Cause
  The SUM binary does not exist in the staging location.

• Action
  Make sure that SUM exists in the SPV ISO.

Solution 2

• Cause
  The SUM binary does not have the correct permissions.

• Action
  Make sure that the SUM binary has the correct permissions.

iSUT does not support the version of SUM

• Symptom
  iSUT cannot launch SUM.

• Cause
  The version of SUM is too old.

• Action
  Verify that the version of SUM is supported. For more information, see the Integrated Smart Update Tools Release Notes.

An unprivileged account installed iSUT

• Symptom
  iSUT installed succeeds, but the commands do not function.

• Cause
  A user account without administrator or root user privileges installed iSUT.

• Action
  Uninstall iSUT and reinstall with an administrator account or root user.

iSUT unexpectedly changes the command

• Symptom
  A requested command changes during processing.

• Cause
  A user sent a request while iSUT processed another request.

• Action
  Reissue the command that changed. Make sure that one command ends before issuing another command.

Firmware update is delayed when firmware is applied in mixed mode

Symptom
When you create a profile in mixed mode, the firmware update schedule is delayed.

Cause
A group of nodes picked by iSUT for concurrent deployment can have a maximum of 20 nodes. The scheduled nodes that have similar attributes for Force Flag, Install type, Baseline URI, and Schedule time are grouped. These nodes are then sent for concurrent updates. If the update for a concurrent group is already in progress, the schedule for the subsequent group is delayed by 1 hour to allow the scheduled nodes to complete their updates.

Action
Ensure that a single group of nodes sent to iSUT for deployment has the following matching properties: Force Flag, Install type, Baseline URI, and Schedule time (if specified).

Hitachi Vantara
Corporate Headquarters 2535 Augustine Drive Santa Clara, CA 95054 USA.

HitachiVantara.com/contact.

References

• Home - Hitachi Vantara
• Contact Us | Hitachi Vantara
• Product Documentation - Hitachi Vantara Knowledge
• Product Documentation - Hitachi Vantara Knowledge
• Login Page
• Servers - Hitachi Vantara Knowledge

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>