Hitachi Compute Connector for VMware vrealize Orchestrator User s Guide v01.4.0

Transcription

1 Hitachi Compute Connector for VMware vrealize Orchestrator v FASTFIND LINKS Document Organization Software Version Getting Help Contents MK-92ADPTR078-04

2 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation. AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/os, z9, z10, zseries, z/vm, and z/vse are registered trademarks or trademarks of International Business MAChines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

3 Contents 1 Contents Preface... 9 Intended Audience Software Version Document Revision Level Release Notes Document Organization Related Documents Terminology and Abbreviations Document Conventions Convention for Storage Capacity Values Getting Help Comments Introduction Overview Architecture Contents 3 Hitachi Compute Connector for VMware vrealize Orchestrator

4 Workflow Support System Requirements and Installation System Requirements Required Hardware Required Software Limitations and Restrictions Memory and CPU Utilization Required Pre-operation Install HCSM Configure HCSM for Blade Servers Configure HCSM for Rack Servers Distribution Package Install the Adapter Deploy the Adapter in vrealize Orchestrator Undeploy the Adapter in vrealize Orchestrator Uninstall the Adapter Installation File and Directory Locations Import Self-Signed SSL Certificates for HCSM Configuring Windows Service Access Using HTTPS Generating an SSL certificate Using Adapter Workflows Provision a Chassis and a Server Input Validation Adapter Workflows Add Chassis Get Chassis Information Contents Hitachi Compute Connector for VMware vrealize Orchestrator

5 Turn Off Chassis LID Turn On Chassis LID Get Fan Modules Add Shared FC Port Remove Shared FC Port Get Shared FC Port Information Add Dedicated FC Port Remove Dedicated FC Port Add Dedicated NIC Port Get Dedicated FC Port Information Remove Dedicated NIC Port Get Dedicated NIC Port Information Get LPAR Bootorder Settings Set bootorder Settings Get memory Settings Set memory settings Get logical CPUs Assign LPAR CPUs: Shared Assign LPAR CPUs: Dedicated Get Server LPAR Physical CPU Get Server LPAR CPU Group Get Server Boot Order Set Server Boot Order Set Server Boot Order Get IO FW supported card Information Disable ForcePXE Enable ForcePXE Get HBA ports Activate LPAR Add Quick LPAR Deactivate LPAR Contents 5 Hitachi Compute Connector for VMware vrealize Orchestrator

6 Get LPAR Information Deploy Windows OS to LPAR Reactivate LPAR Remove LPAR Get Management Modules Get NIC Ports Add Virtual NIC Port Add Virtual NIC Port With Tagged VLANs Add Virtual NIC Port With Untagged VLAN Get Virtual NIC Port Information Remove Virtual NIC Port Get Power Supply Modules Add Server Get Server Information Power Off Server Power On Server Reset Server Get Server EFI Settings Turn Off Server LID Turn On Server LID Get Server LPAR FC Port Information Get Server LPAR NIC Port Information Get Switch Modules Cold Migrate LPAR Hot Migrate LPAR Recover Failed LPAR Migration AutoDeploy ESXi Add Hitachi Compute Webservice Host Get CPU for Quanta Server Get Fan for Quanta Server Update Blade firmware Contents Hitachi Compute Connector for VMware vrealize Orchestrator

7 Update Chassis firmware Disable Server MAC Address Disable Server WWN Get Server MAC Address Lastset Get Server WWN Lastset Set Server MAC Address Set Server WWN Remove Chassis Remove Server Logging and Troubleshooting Logging Log Files Log Format Log Rotation Log Configuration File Logging Levels Troubleshooting The HTTPS connection doesn t work for the web service Message Codes Product ID and Message Catalog Message Codes Contents 7 Hitachi Compute Connector for VMware vrealize Orchestrator

8 8 Contents Hitachi Compute Connector for VMware vrealize Orchestrator

9 Preface This document describes how to use the Hitachi Compute Connector for VMware vrealize Orchestrator (Hitachi Adapter). Use this guide as needed to configure your adapter. This preface includes the following information: Intended Audience Software Version Document Revision Level Release Notes Document Organization Referenced Documents Related Documents Terminology and Abbreviations Document Conventions Convention for Storage Capacity Values Getting Help Comments Note The use of the Hitachi Compute Connector for VMware vrealize Orchestrator and all other Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems. Preface 9 Hitachi Compute Connector for VMware vrealize Orchestrator

10 Intended Audience This user guide addresses users of the Hitachi Compute Connector for VMware vrealize Orchestrator. VMWare vrealize Orchestrator provides orchestration, integration, and automation of IT processes through the creation of workflows, enabling you to define and standardize best practices and improve operational efficiency. This user guide assumes that the reader is an experienced user of VMWare vrealize Orchestrator. Software Version This document applies to version of the Hitachi Compute Connector for VMware vrealize Orchestrator. Document Revision Level Revision Date MK-92ADPTR August 2014 First release MK-92ADPTR March 2015 Replaces MK-92ADPTR MK-92ADPTR October 2015 Replaces MK-92ADPTR MK-92ADPTR April 2016 Replaces MK-92ADPTR MK-92ADPTR June 2016 Replaces MK-92ADPTR MK-92ADPTR Nov 2016 Replaces MK-92ADPTR Release Notes Release notes can be found on the documentation CD. Release notes contain requirements and more recent product information that may not be fully described in this manual. Be sure to review the release notes before installation. Document Organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter Introduction System Requirements and Installation Using Adapter Overview of the product Installation, uninstallation, pre-configuration, requirements, and other basics Expands the vrealize Orchestrator workflow 10 Preface Hitachi Compute Connector for VMware vrealize Orchestrator

11 Workflows Chapter Logging and Troubleshooting Message Codes functionality to work with Hitachi server devices Server logs and other troubleshooting information Error codes Related Documents # 1. VMware vrealize Orchestrator documentation 2. Hitachi Compute Systems Manager User Guide (MK- 91HC194) Current online documentation for VMware vrealize Orchestrator v6.0/7.0 A guiding document to get started with Hitachi Compute Systems Manager Terminology and Abbreviations Term ESXi Server workflow engine vrealize Server The VMware ESXi Server application is an operating systemindependent hypervisor. A workflow engine can be used to automate bulk operations and create workflow processes to integrate existing third-party tools. The VMware vrealize Server is the centralized management tool for the vsphere suite. The vrealize Server allows the management of multiple ESX servers and virtual machines (VMs) from different ESX servers through a single console application. Abbreviation HCSM Hitachi Compute Systems Manager Document Conventions This document uses the following typographic conventions: Convention Bold Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels Example: Click OK. Preface 11 Hitachi Compute Connector for VMware vrealize Orchestrator

12 Convention Italic Indicates a variable, which is a placeholder for actual text provided by the user or system Example: copy source-file target-file Note: Angled brackets (<>) also indicate variables. screen/code Indicates text on the screen or that you enter Example: # pairdisplay -g oradb <> angled Indicates a variable, which is a placeholder for actual text brackets provided by the user or system Example: # pairdisplay -g <group> Note: Italic font also indicates variables. [ ] square Indicates optional values brackets Example: [a b] indicates that you can select a, b, or nothing. { } braces Indicates required or expected values Example: { a b } indicates that you must select either a or b. vertical bar Indicates a choice between two or more options or arguments Examples: [a b] indicates that you can select a, b, or nothing. { a b } indicates that you must select either a or b. This document uses the following icons to draw attention to information: Icon Label Note Calls attention to important and/or additional information Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively Caution Warns the user of adverse conditions and/or consequences (for example, disruptive operations) WARNING Warns the user of severe conditions and/or consequences (for example, destructive operations) 12 Preface Hitachi Compute Connector for VMware vrealize Orchestrator

13 Convention for Storage Capacity Values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: Physical Capacity Unit Value 1 KB 1,000 bytes 1 MB 1,000 2 bytes 1 GB 1,000 3 bytes 1 TB 1,000 4 bytes 1 PB 1,000 5 bytes 1 EB 1,000 6 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: Logical Capacity Unit Value 1 KB 1,024 (210) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes 1 BLOCK 512 bytes Getting Help The Hitachi Data Systems Support Center staff is available 24 hours a day, seven days a week. Provisions for patches and fixes are restricted to normal business hours, 8 a.m. to 5 p.m. PST. To reach us, visit the support website for current telephone numbers and other contact information: If you purchased this product from an authorized HDS reseller, contact that reseller for support. Before calling the Hitachi Data Systems Support Center, provide as much information about the problem as possible, including: The circumstances surrounding the error or failure. The exact content of any error messages displayed on the host systems. Preface 13 Hitachi Compute Connector for VMware vrealize Orchestrator

14 Comments Please send us your comments on this document: Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. Thank you! (All comments become the property of Hitachi Data Systems Corporation.) 14 Preface Hitachi Compute Connector for VMware vrealize Orchestrator

15 1 Introduction This chapter includes the following sections: Overview Architecture Workflow Support Introduction 15 Hitachi Compute Connector for VMware vrealize Orchestrator

16 Overview The Hitachi Compute Connector for VMware vrealize Orchestrator (Hitachi Adapter) is a plug-in for VMware vrealize Orchestrator, a GUI-based workflow management solution for the datacenter. vrealize Orchestrator (vro) provides direction, integration, and automation of IT processes using workflows. These enable system administrators to resolve issues quickly and reuse their solutions as best practices, thus avoiding errors and repetitive work. In addition, vrealize Orchestrator produces status reports so that you can see how well a process is working. The Hitachi Compute Connector for vro is a Java plug-in that is installed on the vrealize Orchestrator server. The Hitachi Adapter provides server configuration, discovery, and additional management functionality for customizing automation. Specifically, the adapter does the following: Allows vrealize Orchestrator to discover Hitachi Compute Blade and Compute Rack server components (such as chassis, blade, and memory). Allows users to manage both blade servers and rack-mounted servers. Architecture Figure 1 illustrates the Hitachi Compute Connector for VMware vrealize Orchestrator adapter architecture. Figure 1. Hitachi Adapter Architecture 16 Introduction Hitachi Compute Connector for VMware vrealize Orchestrator

17 The Hitachi adapter provides the option of using HTTP or Secure Sockets Layer (SSL, or HTTPS) to communicate between the adapter and the hardware management tool Hitachi Compute System Manager (HCSM). Users can choose HTTP or HTTPS when provisioning blade and rack servers. Workflow Support WORKFLOW CB 500 CB 2500 CR 210H CR 220H QuantaPlex QuantaGrid 1 Add chassis * * Add server ** ** * * Disable forcepxe ** ** * * Disable server MAC ** ** * * - - address 5 Disable server WWN ** ** * * Enable forcepxe ** ** * * Get HBA ports ** ** * * Get IO FW supported ** ** * * - - card info 9 Get NIC ports ** ** * * Get chassis * * information 11 Get fan modules * * Get management * * modules 13 Get powersupply * * modules 14 Get server EFI settings ** ** * * Get server MAC ** ** * * - - address lastset 16 Get server WWN ** ** * * - - lastset 17 Get server boot order ** ** * * Get server information ** ** * * * * 19 Get switch modules * * Power off server ** ** * * * * 21 Power on server ** ** * * * * 22 Reset server ** ** * * * * 23 Set server MAC ** ** * * - - address 24 Set server WWN ** ** * * Set server boot order ** ** * * * * 26 Turn off chassis LID * Turn off server LID ** ** * * * * 28 Turn on chassis LID * Turn on server LID ** ** * * * * Introduction 17 Hitachi Compute Connector for VMware vrealize Orchestrator

18 WORKFLOW CB 500 CB 2500 CR 210H CR 220H QuantaPlex QuantaGrid 30 Update blade firmware ** ** Update chassis * * firmware 32 Activate LPAR ** ** Add dedicated FC port ** ** Add dedicated NIC ** ** port 35 Add quick LPAR ** ** Add shared FC port ** ** Add virtual NIC port ** ** Add virtual NIC port ** ** with tagged vlans 39 Add virtual NIC port ** ** with untagged vlan 40 Assign CPUs: ** ** dedicated 41 Assign CPUs: shared ** ** Deactivate LPAR ** ** Get LPAR information ** ** Get LPAR bootorder ** ** settings 45 Get dedicated FC port ** ** information 46 Get dedicated NIC port ** ** information 47 Get logical CPUs ** ** Get memory settings ** ** Get server LPAR CPU ** ** group 50 Get server LPAR FC ** ** port information 51 Get server LPAR NIC ** ** port information 52 Get server LPAR ** ** physical CPU 53 Get shared FC port ** ** information 54 Get virtual NIC port ** ** information 55 Reactivate LPAR ** ** Remove LPAR ** ** Remove dedicated FC ** ** port 58 Remove dedicated NIC port ** ** Introduction Hitachi Compute Connector for VMware vrealize Orchestrator

19 WORKFLOW CB 500 CB 2500 CR 210H CR 220H QuantaPlex QuantaGrid 59 Remove shared FC ** ** port 60 Remove virtual NIC ** ** port 61 Set bootorder settings ** ** Set memory settings ** ** Get CPU for Quanta * * server 64 Get fan for Quanta * * server 65 Add Hitachi Compute Webservice Host 66 Cold Migrate LPAR ** ** Hot Migrate LPAR ** ** Recover failed LPAR ** ** Migration 69 Deploy Windows OS to ** ** LPAR 70 AutoDeploy ESXi ** ** * * * * 71 Remove Chassis * * Remove Server ** ** * * * * * : Supported **: Supported on server blade of the chassis - : Not Supported + : Prerequisite for Quanta management Introduction 19 Hitachi Compute Connector for VMware vrealize Orchestrator

20 20 Introduction Hitachi Compute Connector for VMware vrealize Orchestrator

21 System Requirements and Installation This chapter contains installation information including hardware and software requirements, pre-configuration requirements, and installation instructions. System Requirements Memory and CPU Utilization Required Pre-operation Distribution Package Install the Adapter Deploy the Adapter in vrealize Orchestrator Undeploy the Adapter in vrealize Orchestrator Uninstall the Adapter Installation File and Directory Locations Import Self-Signed SSL Certificates System Requirements and Installation 21 Hitachi Compute Connector for VMware vrealize Orchestrator

22 System Requirements Required Hardware Server Hardware Requirements CPU Memory Graphics Item HDD Capacity Pentium 4 or more 2 gigabytes or more Requirements 80E330600, 16-bit color or more 1 gigabyte or more iscsi Microsoft iscsi Software Initiator Version 2.08 Supported HBAs All host bus adapters (HBAs) certified by Microsoft on the OS are supported. See the relevant Hitachi Compute Blade user document for hardware requirements. Hitachi Servers and Blades Hitachi Servers/Blades Hitachi CB 500 Q A0241-B-9901 Hitachi CB 2500 A Hitachi Blade 520 HB Hitachi Blade 520 HB Hitachi Blade 520 HB Hitachi Blade 520 XB Hitachi Blade 520 XB Hitachi Blade 520 XB Hitachi CR 220H Hitachi CR 210H Required Software or newer or newer QuantaPlex T41S-2U (Sino) QuantaGrid D51B-2U (Nitro) VMware Software Server Firmware Version 5.5 or 6.0 VMware vsphere VMware vrealize Orchestrator 22 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

23 6.0.x or 7.0 VMware vsphere 6.2.x or 7.0 VMware vrealize Automation Hitachi Software Hitachi Compute Systems Manager Hitachi Compute Systems Manager or later Windows Operating Systems Operating Systems Microsoft Windows Server 2008 R2 Standard/Enterprise Edition Microsoft Windows Server 2008 R2 DataCenter Edition Microsoft Windows Server 2012 R2 Standard Edition Microsoft Windows Server 2012 R2 Datacenter Edition Limitations and Restrictions To upgrade or downgrade the Hitachi Adapter, the user must uninstall the current version before installing another version. Memory and CPU Utilization There are no additional requirements for memory than what is specified in the Hardware requirements for VMware vrealize Orchestrator Installation and Configuration guide. CPU Utilization has been tested, and there are no additional requirements. Required Pre-operation Before the Hitachi Adapter can be installed, perform the following steps. Prerequisites: 1. Ensure that vrealize Orchestrator is installed. 2. Install HCSM. 3. Configure HCSM for blade servers or rack servers. System Requirements and Installation 23 Hitachi Compute Connector for VMware vrealize Orchestrator

24 Install HCSM For more information, see the Hitachi Command Suite: Compute Systems Manager User Guide (MK-91HC194-08). Note If you configure HCSM with a self-signed SSL certification, you must import the SSL certificate into the vrealize Orchestrator keystore. Configure HCSM for Blade Servers To set up HCSM for Hitachi Compute Blade servers, you must configure the chassis management modules. For each management module (SVP) used in the Hitachi Compute Blade 500 chassis, configure the following: A Hitachi Compute Systems Manager (HCSM) service The IP address and port number for a HCSM host Configure Chassis Management Modules 1. Access the Compute Blade chassis by entering the chassis IP address into your browser. The WebConsole login page opens. 2. Enter your user name and password. The WebConsole Dashboard opens. 24 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

25 3. Select the Administration tab. In the left-hand navigation pane, select HCSM. The HCSM Administration tab opens to the right. 4. Select the HCSM Service tab. Ensure that HCSM has been enabled. System Requirements and Installation 25 Hitachi Compute Connector for VMware vrealize Orchestrator

26 5. If HCSM is disabled, click Edit. 6. In the Edit HCSM Settings dialog, select Enable, and then add your credentials. Then click Confirm. 7. Select the HCSM Servers tab. Click Add. The Add HCSM Manager Settings dialog opens. 8. To configure the HCSM host server, add its IP address and Port number. 26 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

27 9. Select Confirm to save the management module settings. Configure HCSM for Rack Servers To set up HCSM to work with a Hitachi rack server, follow these steps: 1. Enter the IP address of the rack server into your browser. The rack server's Webconsole opens. Log in as an administrator. 2. Select the Administration tab, and then on the left-hand menu select HCSM. 3. On the right side of the screen, select one of the HCSM servers. Click Edit. The Edit HCSM Servers dialog opens. 4. Complete the server settings, and then click Confirm. Distribution Package 1. Download the Hitachi Compute Connector for VMware vrealize Orchestrator distribution package, Hitachi-Compute-Connector-for- VMware-vRealize-Orchestrator-Setup(01.4.0)-(x64)-01.exe. 2. Run the distribution package. At a location you select, it installs the following files: o Installer for x64 systems: Hitachi-Compute-Connector-for-VMware-vRealize-Orchestrator- Setup(01.4.0)-(x64)-01.exe System Requirements and Installation 27 Hitachi Compute Connector for VMware vrealize Orchestrator

28 Install the Adapter o Hitachi Compute Connector for VMware vrealize Orchestrator, MK-92ADPTR078. To install the Hitachi Adapter, follow these steps: 1. Double-click on the installer file: Hitachi-Compute-Connector-for-VMwarevRealize-Orchestrator-Setup(01.4.0)-(x64)-01.exe The Installation Wizard for the Hitachi Adapter opens. 2. Save the o11nplugin-hivcoserver.dar file at the following default location: C:\Program Files\Hitachi\Hitachi Compute Connector for VMware vrealize Orchestrator Deploy the Adapter in vrealize Orchestrator 1. Access the vrealize Orchestrator Configuration interface by entering the following address into a browser: 2. Log in to the vrealize Orchestrator Configuration interface. The vrealize Orchestrator Configuration interface opens. 28 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

29 3. Click Plug-ins on the left-hand menu. In the list of plug-ins that appears, select the Hitachi Compute Connector adapter. 4. For the Plug-in File field, select the o11nplugin-hivcoserver.dar file. By default, this file is located here: Default: C:\Program Files\Hitachi\Hitachi Compute Connector for VMware vrealize Orchestrator 5. Click Upload and Install. 6. Click Apply changes. In a successful installation, the following message appears. The o11nplugin-hivcoserver.dar adapter file is installed here: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\plugins. 7. On the left side of the vrealize Orchestrator Configuration module, select Startup Options. The server startup options appear on the right. System Requirements and Installation 29 Hitachi Compute Connector for VMware vrealize Orchestrator

30 8. Click Start Service to start the vrealize Orchestrator server. 9. Close the vrealize Orchestrator Configuration module. Undeploy the Adapter in vrealize Orchestrator 1. Delete the o11nplugin-hivcoserver.dar file from the following location: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\plugins\ 2. Access the vrealize Orchestrator Configuration interface by entering the following address into a browser: 3. Log in to the vrealize Orchestrator Configuration interface. Click Startup Options on the left-hand menu. o Click Restart Service to restart the vrealize Configuration service. o Click Restart the vco configuration server to restart the vrealize Orchestrator Server service. 4. Close the vrealize Orchestrator Configuration module. 30 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

31 Uninstall the Adapter 1. From the Windows Control Panel, select Programs and Features. 2. Select Hitachi Compute Connector for VMware vrealize Orchestrator. Right-click it, and then select Uninstall. Installation File and Directory Locations Files and directories related to the Hitachi Adapter are shown in the following table. File and Directories Created by Installer (Installed) Added by users manually Repaired by Installer Deleted by Installer (Uninstalled) <Hitachi Compute X Connector for VMware vrealize Orchestrator Installation Directory> o11nplugin- X - - X HiVCOServer.dar version.txt X - - X Key: X = Target of the process. -= Not target of the process. Import Self-Signed SSL Certificates for HCSM If your HCSM system was configured with a self-signed SSL certification, you must import the SSL certification into the vrealize Orchestrator keystore. No action is needed for other types of SSL certifications. 1. Open the vrealize Orchestrator client, and then log in with Administrator permissions. System Requirements and Installation 31 Hitachi Compute Connector for VMware vrealize Orchestrator

32 2. Select Workflow mode. 3. Open Library > Configuration> SSL Trust Manager. 4. Double-click the workflow Import a certificate from URL. 5. To import the certificate, add the HTTPS URL for HCSM. No action is needed for HTTP configurations. 6. Select Yes for Will you accept a certificate with warnings. Click Submit. 32 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

33 7. Restart the vrealize Orchestrator client. Configuring Windows Service Access Warning The plug-in and Windows service components of this product support a communication mode that uses unencrypted HTTP. When this mode is used, secret information such as server credentials passes between the two software components in plain-text. If the two components reside on separate hosts, this plain-text traffic flows over the network and could be intercepted. To mitigate this risk, configure the two components to communicate using HTTPS instead of HTTP. This is required only when working with Quanta servers. After the plug-in is installed into vrealize Orchestrator, it is necessary to configure it to access the Windows service component (Hitachi Compute Service for vrealize Orchestrator). 1. Open the vcenter Orchestrator Client application from the start menu. 2. You are prompted to log in use the default post-install credentials vcoadmin/vcoadmin or the SSO credentials. 3. In the left-hand pane, select the blue Workflows tab. 4. Browse to Library -> Hitachi -> Server. System Requirements and Installation 33 Hitachi Compute Connector for VMware vrealize Orchestrator

34 5. Run the Add Hitachi Compute Web Service Host workflow. Notes on this workflow: This workflow only needs to be used one time after installing Hitachi Compute Connector for VMware vrealize Orchestrator. It is a one-time operation. If HTTPS communication between the plug-in and Windows service is desired, choose Yes from the SSL radio-button. Ensure that the Hitachi Compute Web Service Host is set to the FQDN of the web service host if HTTPS connection is desired. Note Additional steps are required before HTTPS communication can function. You must create an SSL certificate and configure vrealize Orchestrator before using vrealize Orchestrator. See Using HTTPS below for more information. Refer to the Add Hitachi Compute Web Service Host workflow. 34 System Requirements and Installation Hitachi Compute Connector for VMware vrealize Orchestrator

35 Using HTTPS To use HTTPS support, follow these steps: 1. Choose SSL support while using the Add Hitachi Compute Web Service Host workflow (see Configuring Windows Service Access for more information). 2. Obtain an SSL certificate. If you want to use a self-signed certificate, here is one way to generate one. Generating an SSL certificate The certificate should be located in < C:\Program Files\Hitachi\Hitachi Compute Connector for vro\cert>. 1. Remove any existing files from this folder. 2. Run the following PowerShell command: New-SelfSignedCertificate -dnsname <My_DNS_hostname or server_fqdn> -CertStoreLocation cert:\localmachine\my 3. Run the following PowerShell command: Export-Certificate -Cert cert:\localmachine\my\<thumbprint_generated_above> -FilePath "C:\Program Files\Hitachi\Hitachi Compute Connector for vro\cert\vrocompute_cert.cer" 4. Restart the Hitachi Compute Web service. Restart-Service -Display "Hitachi vro Compute Web Services" System Requirements and Installation 35 Hitachi Compute Connector for VMware vrealize Orchestrator

36 36 System Requirements and Installation

37 Using Adapter Workflows Use the Hitachi Adapter workflows to manage Hitachi Compute Blade and Compute Rack servers. Provision a Chassis and a Server Input Validation Adapter Workflows Using Adapter Workflows 37

38 Provision a Chassis and a Server For the Hitachi Adapter to work properly, you must first provision a chassis and a server. After that, perform all other provisioning as desired. 1. Open the vrealize Orchestrator client, and then log in. 1. Select the Design (workflow) mode. 2. Expand the Library folder list. The Hitachi Server folder contains all Hitachi Adapter workflows. These work for both blade and rack servers. 3. First, select the Add chassis workflow, and then right-click Start Workflow. The Start Workflow dialog box opens. 38 Using Adapter Workflows

39 4. In the Start Workflow dialog, add parameters as desired. Note Use SSL? By default, the workflows are configured using Secure Sockets Layer (SSL) encryption (HTTPS protocol). To configure using the non-encrypted HTTP protocol, select No. 5. Click Submit. Note For instructions on validating parameter data, see Input Validation. 6. Click the Inventory tab. Click the Refresh icon at the top right of the page to update the inventory. Using Adapter Workflows 39

40 The inventory list opens. The Hitachi Compute Connector item contains the Hitachi Compute Repository with sublists of chassis and servers. Note When you add a chassis, the Hitachi Adapter provisions all active components of that chassis. For example, if an added chassis contains four blades that are operational, all four blades are provisioned. Input Validation The following procedure describes the input validation process performed by vrealize Orchestrator client on Hitachi Adapter data. 1. In the provisioning process after you enter parameters and click Submit, input validation begins on the content entered in the parameter fields. 40 Using Adapter Workflows

41 The variables entered in the preceding screen appear in the vrealize Orchestrator Schema tab. The green icons at the beginning and end of the process indicate that provisioning was performed successfully. Identifiers for the successfully provisioned device appear in the lower right window. Using Adapter Workflows 41

42 7. If a parameter is omitted or is incorrect, the vrealize Orchestrator client displays an error message and indicates which parameters were entered incorrectly. 8. If required, a real-time record is available in the Logs tab. 42 Using Adapter Workflows

43 Adapter Workflows Add Chassis The following workflows are organized in alphabetical order by the server component that they affect. For example, all workflows affecting the chassis (Add Chassis, for example) are placed before Get HBA ports, which is placed before Get NIC ports. Add Chassis adds a Hitachi chassis to the vrealize Orchestrator inventory. Required? chassisaddress Required IP address of a given chassis hcsmaddress Required IP address of HCSM server. The IP address must be in the following format: hcsmport Required Port number of HCSM server. The valid range of this port number is between hcsmprotocol Optional Specifies the protocol of HCSM (Default: HTTP) hcsmuser Required Specifies the user name for the HCSM server hcsmuserpassword Required Specifies the user password for the HCSM server The output type is HitachiComputeConnector:Chassis. chassisuniquekey chassismodel chassismodelnumber chassis chassisserialnumber chassisstatus chassissystem chassistype Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Model name of this chassis Model number of this chassis Health status: NORMAL, WARNING, FAIL, UNKNOWN Serial number of this chassis Running Unknown Chassis system types Chassis type Using Adapter Workflows 43

44 error healthstatus information lastrefreshed lidcolor lidstatus maintenancemode svpdefaultgateway svpipaddress svpsubnetmask warning webconsoleurl Number of unconfirmed error alerts Health status Number of unconfirmed information alerts Time when last refreshed LID color: BLUE GREEN RED ORANGE UNKNOWN LID status: ON OFF BLINKING SLOW_BLINKING FAST_BLINKING UNKNOWN Indicates whether a server is in maintenance mode Options: TRUE, FALSE SVP default gateway SVP IP Address SVP subnet mask Number of unconfirmed warning alerts URL of the web console Get Chassis Information Get Chassis Information obtains information about a Hitachi chassis. Type Required? selectedchassis HitachiComputeConnector:Chassis Required The output type is HitachiComputeConnector:ChassisInfo. Selected chassis 44 Using Adapter Workflows

45 chassisuniquekey chassismodel Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Model name of this chassis chassismodelnumber Model number of this chassis chassis chassisserialnumber chassisstatus chassissystem chassistype error healthstatus information lastrefreshed lidcolor lidstatus maintenancemode svpdefaultgateway svpipaddress svpsubnetmask Warning Health Status: NORMAL WARNING FAIL UNKNOWN Serial number of this chassis Running Unknown Chassis system types Chassis type Number of unconfirmed error alerts Health status Number of unconfirmed information alerts Time when last refreshed LID color: BLUE GREEN RED ORANGE UNKNOWN LID status: ON OFF BLINKING SLOW_BLINKING FAST_BLINKING UNKNOWN Indicates whether a server is in maintenance mode Options: TRUE, FALSE SVP default gateway SVP IP address SVP subnet mask Number of unconfirmed warning alerts Using Adapter Workflows 45

46 webconsoleurl URL of the web console Turn Off Chassis LID Turn Off Chassis LID sets the LID light off for a Hitachi chassis. Note Turn off chassis LID does not work on the Hitachi CB2500 chassis. Type Required? selectedchassischassis HitachiComputeConnect Required Selected Address or:chassis chassis message Message of the result Turn On Chassis LID Turn On Chassis LID sets the LID light on for a Hitachi server. Note Turn on chassis LID does not work on the Hitachi CB2500 chassis. Type Required? selected HitachiComputeConnector: Required Selected chassis Chassis Chassis message Message of the result 46 Using Adapter Workflows

47 Get Fan Modules Get Fan Modules obtains information about all active fan modules for a chassis. Type Required? selectedchassis HitachiComputeConnector:Chassis Required Selected chassis chassisuniquekey healthstatus installstatus powerstatus slotno Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Health status: NORMAL, WARNING, FAIL, UNKNOWN Install status: INSTALL. NOT_INSTALL, NA Power status: ON, OFF, UNKNOWN Number of the slot where the fan module is installed Add Shared FC Port Add Shared FC Port adds a shared Fibre Channel port to a specified logical partition. Type Required? selectedserver HitachiComputeCon nector:hitachiserver Required Selected server LPARNo Number Required Logical partition number slotno String Required Slot number of the shared FC port portno String Required Port number of the shared FC port bootavailability Boolean Required Boot availability of the shared FC port vfcid String Required VFC ID of the shared FC port saveconfig Boolean Required Saves the configuration Using Adapter Workflows 47

48 message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Remove Shared FC Port Remove Shared FC Port removes a selected shared Fibre Channel port from a specified LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number slotno String Required Slot number of the shared FC port portno String Required Port number of the shared FC port saveconfig Boolean Required Saves the configuration message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get Shared FC Port Information Get Shared FC Port Information obtains the information of all shared Fibre Channel ports on a specified LPAR. Type Required? selected HitachiComputeConn Required Selected server Server ector:hitachiserver LPARNo Number Required Number of the logical partition The output type is HitachiComputeConnector:LPARSharedFCPortInfo. 48 Using Adapter Workflows

49 serveruniquekey LPARNo LPAR formattedslotno slotno portno pcino portstatus vfcid wwpn wwnn migrationwwpn migrationwwnn busno funcno bootavailability Server unique key Logical partition number Logical partition name Formatted slot number Slot number Port number PCI number Port status VFC ID WWPN WWNN Migration of port World Wide Migration of node World Wide Bus number Function number Boot availability Add Dedicated FC Port Add Dedicated FC Port adds dedicated FC ports to a specified LPAR. All FC ports of this dedicated FC card are assigned to this LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number pcideviceno Number Required Existing dedicated FC PCI device number saveconfig Boolean Required Saves the configuration message Message of the result. If it successfully executes, the message should be Completed. Otherwise, it returns an error message. Using Adapter Workflows 49

50 Remove Dedicated FC Port Remove Dedicated FC Port removes a dedicated FC port to a specified logical partition. All ports of this dedicated FC are removed to this LPAR only. Required? Type selectedserver Required HitachiComputeCon nector:hitachiserver Selected server LPARNo Required Number Logical partition number pcideviceno Required Number Existing dedicated FC PCI device number saveconfig Required Boolean Saves the configuration serveruniquekey LPARNo bootorder type identifier Server unique key Logical partition number Boot order number. If this device does not belong to the current boot order, the value should be *. PCI device type (that is, "LU" "PXE" "iscsi" "USB" "EFI-SHELL") Device identifier Add Dedicated NIC Port Add Dedicated NIC Port adds dedicated NIC ports to a specified LPAR. All NIC ports of this dedicated NIC card are assigned to the LPAR. Type Required? selected server HitachiCompute Connector:Hita chiserver Required Selected server LPARNo Number Required Logical partition number pcidevice No Number Required Existing dedicated FC PCI device number 50 Using Adapter Workflows

51 Type Required? saveconfi g message Get Dedicated FC Port Information Boolean Required Saves the configuration Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get Dedicated FC Port Information obtains the information of all dedicated Fibre Channel ports on a specified LPAR. Type Required? selected HitachiComputeConn Required Selected server Server ector:hitachiserver LPARNo Number Required Number of the logical partition The output type is HitachiComputeConnector:LPARDedicatedFCPortInfo. serveruniquekey LPARNo LPAR formattedslotno slotno portno pcino portstatus wwpn wwnn bootavailability Server unique key Logical partition number Logical partition name Formatted slot number Slot number Port number PCI number Port status WWPN WWNN Boot availability Using Adapter Workflows 51

52 Remove Dedicated NIC Port Remove Dedicated NIC Port removes a dedicated NIC from a specified LPAR. All ports of this dedicated NIC are removed from only this LPAR. Type Required? selectedserve HitachiCo Required Selected server r mputecon nector:hit achiserver LPARNo Number Required Logical partition number pcideviceno Number Required Existing dedicated FC PCI device number saveconfig Boolean Required Saves the configuration message Get Dedicated NIC Port Information Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get Dedicated NIC Port Information retrieves information of all dedicated NIC ports on a specified LPAR. Type Required selectedserver HitachiComputeConnector: Required Selected server HitachiServer LPARNo Number Required Number of the LPAR The output type is HitachiComputeConnector:LPARDedicatedNICPortInfo. It has the following properties: serveruniquekey LPARNo Server unique key LPAR number 52 Using Adapter Workflows

53 LPAR formattedslotno slotno portno pcino LPAR name Formatted slot number Slot number Port number PCI number Get LPAR Bootorder Settings Get LPAR Bootorder Settings retrieves information of the current boot order on a specified LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number The output is a collection of objects, and the object type is HitachiComputeConnector:LPARBootOrderSettingsInfo. It has the following properties: serveruniquekey LPARNo bootorder type identifier Server unique key Logical partition number Boot order number. If this device does not belong to the current boot order, the value should be *. PCI device type (that is, "LU" "PXE" "iscsi" "USB" "EFI-SHELL") Device identifier Set bootorder Settings Set bootorder Settings sets the boot order of a specified LPAR. Using Adapter Workflows 53

54 Type Required? selected HitachiCom Required Selected server Server puteconnec tor:hitachis erver LPARNo Number Required Logical partition number identifier Device identifier Required "Target PCI device":"input format" "LU":"slotno_portno_luno" "PXE":"Mac address(xx:xx:xx:xx:xx:xx)" "iscsi":"mac address_luno(xx:xx:xx:xx:xx :xx_luno)" "USB":"portno_seg bus dev func" or "KVM_seg bus dev func" "EFI-SHELL":"EFI- SHELL"(string) savecon fig ( x:a-z,a-z,0-9) Boolean Required Saves the configuration message Get memory Settings Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get memory Settings retrieves memory information for a specified LPAR. Type Required? selectedserv HitachiComp Required Selected server er uteconnecto r:hitachiser ver LPARNo Number Required Logical partition number 54 Using Adapter Workflows

55 The output type is HitachiComputeConnector:LPARLogicalCPUInfo. It has the following properties: serveruniquekey LPARNo LPAR logicalcpuno assignedphysicalcpuno Server unique key Logical partition number Logical partition name Logical CPU number Assigned Physical CPU number (Integer or "Automatically") Set memory settings Set memory settings sets the memory for a specified LPAR. Note Set LPAR memory settings does not work on the Hitachi CB2500 chassis. Type Required? selectedse HitachiCo Required Selected server rver mputecon nector:hit achiserve r LPARNo Number Required Logical partition number memorysiz eingb Number Required Size of memory memoryno de Number Optional Memory node. The default value is Automatically. saveconfig Boolean Required Saves the configuration Get logical CPUs message Message of the result. If it successfully executes, the message should be Completed. Otherwise, it returns an error message. Get logical CPUs retrieves logical CPU information from a specified LPAR. Using Adapter Workflows 55

56 Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number The output type is HitachiComputeConnector:LPARLogicalCPUInfo. It has the following properties: serveruniquekey LPARNo LPAR logicalcpuno assignedphysicalcpuno Server unique key Logical partition number LPAR name Logical CPU number Assigned Physical CPU number (Integer or "Automatically") Assign LPAR CPUs: Shared Assign LPAR CPUs: Shared edits the logical CPUs (Shared) settings of a specified logical partition. Type Required? selectedserver HitachiCompu Required Selected server teconnector: HitachiServer LPARNo Number Required Logical partition number numoflogicalcpu Number Required Number of the logical CPUs of this logical partition cpugroup Number Required CPU group cpuallocationratio Number Required CPU allocation ratio cpuidledetection Boolean Required CPU idle detection cpuperformancec Boolean Required CPU performance capping apping saveconfig Boolean Required Saves the configuration 56 Using Adapter Workflows

57 message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Assign LPAR CPUs: Dedicated Assign LPAR CPUs: Dedicated edits the logical CPU (dedicated) settings of a specified LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number numoflogicalcpu Number Required Number of the logical CPUs of this logical partition logicalcpulist List Optional Defines the relation of logical CPU and physical CPU cpugroup Number Optional CPU group cpuidledetection Boolean Required CPU idle detection saveconfig Boolean Required Saves the configuration message Get Server LPAR Physical CPU Message of the result. If it successfully executes, the message should be Completed. Otherwise, it returns an error message. Get Server LPAR Physical CPU retrieves the physical CPU information of a specified server for logical partitions. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number Using Adapter Workflows 57

58 The output type is HitachiComputeConnector:LPARDedicatedFCPortInfo. It has the following properties: serveruniquekey LPARNo LPAR formattedslotno slotno portno pcino wwpn wwnn bootavailability Server unique key Logical partition number Logical partition name Formatted slot number Slot number Port number PCI number WWPN WWNN Boot availability Get Server LPAR CPU Group Get Server LPAR CPU Group retrieves the CPU group information of a specified server for LPARs. Type Required? selectedserver HitachiComputeConnector:Hit achiserver Required Selected server The output type is HitachiComputeConnector:ServerLpCPUGroupInfo. It has the following properties: serveruniquekey groupno group numofsharedcores numofdedicatedcores numofthreads Server unique key Group number Group name Shared cores Dedicated cores Number of threads Get Server Boot Order Get Server Boot Order retrieves the current boot order of a specified server. 58 Using Adapter Workflows

59 Type Required? selectedserver HitachiComputeConnector:H itachiserver Required Selected server The output type is HitachiComputeConnector:ServerBootOrder. It has the following properties: serveruniquekey currentbootorderlist possiblebootorderdevices Server unique key List of current boot devices List of possible boot devices Set Server Boot Order Set Server Boot Order sets the boot order of a specified server. This operation requires you power off the specified server. Type Required? selectedserver HitachiCompu teconnector: HitachiServer Required Selected server bootorderdevice List String Required List of boot devices. Each device is separated by comma (for example, Hard Disk 0, PXE Network, CD/DVD Rom ). message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Set Server Boot Order Set Server Boot Order sets the boot order of a specified server. This operation requires you to power off the specified server. Using Adapter Workflows 59

60 Type Required? selectedserv er HitachiComputeC onnector:hitachi Server Required Selected server bootorderde vicelist message String Required List of boot devices. Each device is separated by comma (for example, Hard Disk 0, PXE Network, CD/DVD Rom ). Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get IO FW supported card Information Get IO FW supported card Information retrieves firmware details from all I/O cards on a specified blade. Type Required? selectedserver HitachiComputeConnector:Hit Required Selected achiserver server It has the following properties: partitionnumber serverbladenumber cardtype cardslotnumber cnasettingsupport iofwupdatesupport fwversionsupport Partition number Blade number Card type (that is, "ONBOARD" "MEZZANINE"" "PCI_IOBD") Card slot number CNA configuration availability (that is, "Enable" "Disable") IO firmware updating availability (that is, "Enable" "Disable") Availability of retrieving firmware version (that is, "Enable" "Disable") 60 Using Adapter Workflows

61 controllerfwversion cnaniceightportsetting Support String describing the list of firmware version structure for all controllers on the card. The structure includes ControllerNumber and Firmware version. Each structure is separated by comma, and the controller number and the firmware version are connected by underscore (for example, 01_ , 02_5.2) NicEightPortSetting availability (that is, "Enable" "Disable") Disable ForcePXE Disable ForcePXE disables the forcepxe booting process on a Hitachi server. Type Required? selectedserver HitachiComputeConnector: Required Selected server HitachiServer message Message of the result Enable ForcePXE Enable ForcePXE enables forcepxe booting for a given server. Type Required? selectedserver HitachiComputeConnector:Hit Required Selected server achiserver message Message of the result Get HBA ports Get HBA Ports obtains information about all active host bus adapter (HBA) ports for a given server. Using Adapter Workflows 61

62 Type Required? selectedserver HitachiComputeConnector: HitachiServer Required Selected server The output type is HitachiComputeConnector:ServerHBAPortInfo. serveruniquekey busnumber card cardslotnumber cardtype controllernumber devicenumber functionnumber portnumber serverbladenumber wwnn wwnnchangefromdefault wwnnduplication wwpn wwpnchangefromdefault wwpnduplication Unique key among all of managed chassis, servers (blades/racks/generic servers), and switch modules, including third- party vendors Bus number Card name Slot number Card type: MEZZANINE PCI ONBOARD Controller number Device number Function number Port number Blade number that has this NIC card WWNN TRUE FALSE TRUE FALSE WWPN TRUE FALSE TRUE FALSE 62 Using Adapter Workflows

63 Activate LPAR Activate LPAR removes a selected LPAR from a specified Hitachi server. Type Required? selectedserver HitachiComputeConn Required Selected server ector:hitachiserver LPARNo Number Required Logical partition number message Add Quick LPAR Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Add Quick LPAR creates multiple LPARs using predefined default settings (2 GB RAM, dedicated CPU allocation, 2 virtual NICs, etc.). The predefined default settings are as follows: 2 GB RAM If the segment 1a/1b exists, it creates VNIC0/1 and relates them with the segment accordingly. If the server is allowed to create shared FC, two VFCs are created. It searches for unused VFCs from FC that the PCI number is small. One VFC is selected from one port. Type Required? selectedserver HitachiComp Required Selected server uteconnector :HitachiServ er numberoflpars Number Required Number of the logical partitions firstlparno Number Required First logical partition number saveconfig Boolean Required Saves the configuration Using Adapter Workflows 63

64 message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Deactivate LPAR Deactivate LPAR deactivates a selected LPAR from a specified Hitachi server. Required? Type selecteds Required HitachiComput Selected server erver econnector:hi tachiserver LPARNo Required Number Logical partition number message Get LPAR Information Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get LPAR Information gets the information of all logical partitions of a specified Hitachi server. Type Required? selectedserver HitachiComputeConnector: Required Selected server HitachiServer The output type is HitachiComputeConnector:ServerLPARInfo. serveruniquekey LPARNo LPAR LPARManagerID LPARStatus Server unique key Logical partition number Logical partition name LPAR Manager ID Logical partition status: ACT:Activated DEACT:Deactivated 64 Using Adapter Workflows

65 migrationstatus lastrefreshed error warning information activationorder autoclearsystemeventlog virtualconsole cpuallocation numberoflogicalcpus cpugroup cpuallocationratio cpuidledetection cpuperformancecapping memorysizeinmb memorynode Migration status Time when last refreshed Error count Warning count Information count Activation order. It should be integer or * Auto clear system event log Virtual console. It should be integer or * CPU allocation Number of logical CPUs CPU group CPU allocation ratio CPU IDLE detection CPU performance capping Memory size Memory node Deploy Windows OS to LPAR Deploy Windows OS to LPAR deploys Windows 2008 R2 or Windows 2012 R2 on a specified LPAR. Prerequisites The LPAR needs to be in deactivated state for this workflow to work. This workflow requires the VMware vcenter Orchestrator Plugin for Microsoft Windows PowerShell v1.0.4 or above and a WDS server which can be used as a PowerShell host with Hitachi Infrastructure Adapter for Microsoft Windows PowerShell installed. After configuring WDS on a server, install the latest Hitachi Infrastructure Adapter for Microsoft Windows PowerShell on it. Thereafter, configure it as a PowerShell host. To configure the PowerShell host on VMware vrealize Orchestrator, check the section indicated in the following link: plugins/index.jsp#com.vmware.using.powershell.plugin.doc_10/guid-8ae1cff2- F6F BDD9-F318E461AB2F.html Using Adapter Workflows 65

66 Before deploying a Windows operating system to a Hitachi server, ensure that the following conditions are met: Window Deployment Services (WDS), DHCP, and pre-boot execution environment (PXE) servers must be running. The Hitachi and Quanta servers to receive OS deployments must have empty disks. For Hitachi servers (and LPARs), HCSM must discover the Hitachi servers with empty disks where the OS is to be deployed. For Quanta servers, the Hitachi Server Adapter for Microsoft Windows PowerShell must be installed on the PowerShell Host. The boot order must be preconfigured with PXE boot first in the list. The WDS Server: Must be on the same subnet as the Hitachi server where OS deployment will take place. Must have the following present: The Windows OS boot images to be deployed. The OS deployment images must be stored either in.wim or.vhd file format. Supported OS are Windows Server 2008 R2 and Windows Server 2012 R2. Unattended answer files present on the WDS server in.xml format The DHCP server: Must be on the same subnet as the Hitachi server where OS deployment will take place. Must be configured with either of the following: A pool of spare IPs for dynamic allocation in the same subnet as DHCP Static configuration of IP against the MAC address of the NIC of the corresponding LPAR/blade server where the deployment will take place Type Required? Server HitachiComputeC Required Source server onnector:hitachis erver LparNo Number Required Source LPAR number Hitachi PS Server Host PowerShell:Power ShellHost Required Remote WDS host contains Hitachi PS Server Boot Image Path String Required Path to the desired boot 66 Using Adapter Workflows

67 Reactivate LPAR Type Required? image Unattended script String Optional Path to the unattended install script Reactivate LPAR reactivates a selected LPAR from a specified Hitachi server. Type Required? selectedserver HitachiCompute Required Selected server Connector:Hitac hiserver LPARNo Number Required Logical partition number message Remove LPAR Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Remove LPAR removes a selected LPAR from a specified Hitachi server. Type Required? selected HitachiComputeConnector: Required Selected server Server HitachiServer LPARNo Number Required Logical partition number message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Using Adapter Workflows 67

68 Get Management Modules Get Management Modules gets the management modules of a Hitachi chassis to the workflow. Type Required? selectedchassischassis Address HitachiComputeConn ector:chassis Required Selected chassis The output type is HitachiComputeConnector:ManagementModuleInfo. chassisuniquekey active dictionaryversion firmwareversion healthstatus installstatus lidcolor lidstatus maintenancedefaultgateway maintenanceipaddress maintenancemode maintenancesubnetmask modelnumber parameterversion powerstatus slotno Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Active status: ACTIVE NON_ACTIVE UNKNOWN Version of the firmware Health status: NORMAL, WARNING, FAIL, UNKNOWN Install status: INSTALL, NOT_INSTALL, NA Lid color: BLUE, GREEN, RED, ORANGE, UNKNOWN Lid status: ON, OFF, BLINKING, SLOW_BLINKING, FAST_BLINKING, UNKNOWN Maintenance default gateway Maintenance IP address Indicates whether a server is in maintenance mode Options: TRUE, FALSE Maintenance subnet mask Model number Power status: ON, OFF, Unknown Slot number of this management module 68 Using Adapter Workflows

69 svpdefaultgateway svpipaddress svpsubnetmask Default gateway of SVP IP address of SVP Subnet mask of SVP Get NIC Ports Get NIC Ports obtains information about all active NIC ports for a given server. Type Required? selectedserver HitachiCo Required Selected server mputeco nnector: HitachiSe rver LPARNo Number Required Number of the logical partition The output type is HitachiComputeConnector:ServerNICPortInfo. serveruniquekey busnumber card cardslotnumber cardtype changefromdefault controllernumber devicenumber Unique key among all of managed chassis, servers (blades/racks/generic servers), and switch modules including third-party vendors Bus number Card name example: Emulex 10Gb 4-port converged network mezzanine card Slot number Card type options: MEZZANINE PCI ONBOARD TRUE FALSE Controller number Device number Using Adapter Workflows 69

70 duplication functionnumber macaddress portnumber serverbladenumber TRUE FALSE Function number MAC address Port number Blade number that has this NIC card Add Virtual NIC Port Add Virtual NIC Port adds a virtual NIC port to a specified LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number vnicno Number Required Number of the VNIC segment String Required VNIC segment macaddress String Optional MAC address promiscuousmode Boolean Required Promiscuous mode saveconfig Boolean Required Saves the configuration message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Add Virtual NIC Port With Tagged VLANs Add Virtual NIC Port With Tagged VLANS adds a virtual NIC port with a tagged VLAN to a specified LPAR. Type Required? selectedserver HitachiComputeCon Required Selected server nector:hitachiserver LPARNo Number Required Logical partition number 70 Using Adapter Workflows

71 Type Required? vnicno Number Required VNIC number segment String Required VNIC segment macaddress String Optional MAC address vlanid Number Required VLAN ID promiscuousm Boolean Required Promiscuous mode ode saveconfig Boolean Required Saves the configuration message Message of the result. If it is executed successfully, the message should be Completed. Otherwise, it returns an error message. Add Virtual NIC Port With Untagged VLAN Add Virtual NIC Port With Untagged VLAN adds a virtual NIC port with an untagged VLAN to a specified LPAR. Type Required? selectedser HitachiCo Required Selected server ver mputeco nnector: HitachiSe rver LPARNo Number Required Logical partition number vnicno Number Required Number of the VNIC segment String Required VNIC segment macaddres String Optional MAC address s vlanidlist List of Required List of VLAN IDs number promiscuou Boolean Required Promiscuous mode smode saveconfig Boolean Required Saves the configuration message Message of the result. If it is executed successfully, the message Using Adapter Workflows 71

72 should be Completed. Otherwise, it returns an error message. Get Virtual NIC Port Information Get Virtual NIC Port Information gets information about all virtual NIC ports for a specified LPAR. Type Required? selectedserver HitachiCompute Connector:Hita Required Selected server chiserver LPARNo Number Required Logical partition number The output type is HitachiComputeConnector:LPARVirtualNICPortInfo. serveruniquekey LPARNo LPAR vnicno macaddress segment formattedslotno slotno pcino portno vlantagtype vlanid promiscuousmode txrate Server unique key Logical partition number Logical partition name vnic number MAC address (XX:XX:XX:XX:XX:XX) Network segment Formatted slot number Slot number PCI number Port number VLAN tag type VLAN ID Promiscuous mode Transmission rate Remove Virtual NIC Port Remove Virtual NIC Port removes a selected virtual NIC port from a specified LPAR. 72 Using Adapter Workflows

73 Type Required? selectedserver HitachiComputeConnect Required Selected server or:hitachiserver LPARNo Number Required Logical partition number vnicno Number Required Number of the virtual NIC saveconfig Boolean Required Saves the configuration message Get Power Supply Modules Message of the result. If it is executed successfully, the message should be Completed. Otherwise, it returns an error message. Get Power Supply Modules gets information about the power supply for a specified Hitachi chassis. Type Required? selectedchassis HitachiComputeCon Required Selected nector:chassis chassis The output type is HitachiComputeConnector:PowerSupplyModuleInfo. chassisuniquekey healthstatus installstatus model powerstatus product serialnumber slotno Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Health status: NORMAL, WARNING, FAIL, UNKNOWN Install status: INSTALL, NOT_INSTALL, NA Model name Power Status: ON, OFF, Unknown Product name Serial number Slot number of this management module Using Adapter Workflows 73

74 Add Server Add Server adds a specified server to the workflow. Required? hcsmaddress Required IP address of HCSM server. The IP address must be in the following format: hcsmport Required Port number of HCSM server. The valid range for this port number is hcsmuser Required User name for the HCSM server hcsmuserpassword Required User password for the HCSM server serveraddress Required IP address of a given chassis The output type is HitachiComputeConnector:ChassisInfo. chassisuniquekey Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) serveruniquekey Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules including third-party vendors cpucachesizeinkb CPU cache size cpufrequencyinmhz CPU frequency cpu CPU name currentefiversion EFI versions that are currently running currentfwversion Firmware versions that are currently running currentlomversion LOM versions that are currently running error Error count firmwarerestartrequired TRUE: The blade requires reboot for making updated firmware effective. FALSE: The updated firmware is already effective. healthstatus Health status information Information count lastrefreshed Time when last refreshed yyyy-mm-ddthh:mm:ss+tt:mm or 74 Using Adapter Workflows

75 lidcolor lidstatus iomdefaultgateway iomdhcpenable iomipaddress iomsubnetmask mactype maintenancemode manufacturer memorysizeinmb nmcoldstandby numberofcores numberofcpus osmode partitionno partitionvalid partitionwidth primaryslot remoteconsoleurl serverproduct serverproductnumber serverserialnumber serverstatus yyyy-mm-ddthh:mm:ss-tt:mm LID color LID status LOM (BMC) default gateway LOM DHCP Enable status options: TRUE FALSE LOM (BMC) IP address LOM (BMC) subnet mask MAC type: Original Additional Unknown Indicates whether a server is in maintenance mode Options: TRUE, FALSE Manufacturer Memory size TRUE: The blade is used as Active or Standby blade in an N+M group. FALSE: The blade is NOT used as Active or Standby blade in an N+M group. Cores per CPU Number of CPUs Operating system mode options: Basic HVM Unknown Partition number Validation of partition Number of server modules in this partition Primary slot number of this partition URL of the remote console Product name Product number Unique number among Hitachi Chassis/Blade/Rack Server status options: Running Using Adapter Workflows 75

76 serveruuid slotwidth updatingefiversion updatingfwversion updatinglomversion warning wwntype Stopped Unknown Universally unique identifier (UUID) Number of slots in the chassis EFI versions that are applied after rebooting server Firmware versions that are applied after rebooting server LOM versions that are applied after rebooting server Warning count WWN type: Original Additional Unknown Get Server Information Get Server Information retrieves a Hitachi server and places it into the workflow. Type Required? Descriptio n selecteds erver HitachiComputeConnector:HitachiS erver Required The output type is HitachiComputeConnector:ServerInfo. Selected server bladenumber chassisuniquekey serveruniquekey cpucachesizeinkb cpufrequencyinmhz Blade number Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Unique key among all of managed chassis, servers (blades/racks/generic servers), and switch modules including third- party vendors CPU cache size CPU frequency 76 Using Adapter Workflows

77 cpu currentefiversion currentfwversion currentlomversion error CPU name EFI versions that are currently running Firmware versions that are currently running LOM versions that are currently running Error count firmwarerestartrequired TRUE: The blade requires reboot for making updated firmware effective. FALSE: The updated firmware is already effective. healthstatus Health status information Information count lastrefreshed Time when last refreshed yyyy-mm-ddthh:mm:ss+tt:mm or yyyy-mm-ddthh:mm:ss-tt:mm lidcolor LID color lidstatus LID status lomdefaultgateway LOM (BMC) default gateway lomdhcpenable LOM DHCP Enable status: TRUE FALSE lomipaddress LOM (BMC) IP address lomsubnetmask LOM (BMC) subnet mask mactype MAC type: Original Additional Unknown maintenancemode Indicates whether a server is in maintenance mode TRUE FALSE manufacturer Manufacturer memorysizeinmb Memory size nmcoldstandby TRUE: The blade is used as Active or Standby blade in an N+M Group. FALSE: The blade is NOT used as Active or Standby blade in an N+M Group. numberofcores Cores per CPU numberofcpus Number of CPUs osmode OS mode: Using Adapter Workflows 77

78 partitionno partitionvalid partitionwidth primaryslot remoteconsoleurl serverproduct serverproductnumber serverserialnumber serverstatus serveruuid slotnumber slotwidth updatingefiversion updatingfwversion updatinglomversion warning wwntype Basic HVM Unknown Partition number Validation of partition Number of server modules in this partition Primary slot number of this partition URL of the remote console Product name Product number Unique number among Hitachi Chassis/Blade/Rack Server status: Running Stopped Unknown UUID (universally unique identifier) Slot number Number of slots in a chassis EFI (extensible firmware interface) versions that are applied after rebooting server Firmware versions that are applied after rebooting server LOM versions that are applied after rebooting server Warning count WWN type: Original Additional Unknown Power Off Server Power Off Server sets the power of a selected server to the off position. Type Required? selectedserver HitachiComputeConnector: Required Selected server HitachiServer 78 Using Adapter Workflows

79 message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Power On Server Power On Server sets the power for a specified server to the on position. Required? serveraddress Required BMC IP address of a server message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Reset Server Reset Server sets the power reset for a Hitachi server. Required? serveraddress Required BMC IP address of a server message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Get Server EFI Settings Get Server EFI Settings obtains the extensible firmware interface (EFI) settings for a specified server. Using Adapter Workflows 79

80 Type Required? selectedse rver HitachiCompute Connector:Hitac hiserver Required Selected server The output type is HitachiComputeConnector:ServerEFISettings. rasconfigurationdeconfigu redmode processorshardwareprefet cherpossiblevalues processorshyperthreading PossibleValues processorshardwareprefet cher operatingmodesddrvoltag elevel rasconfigurationdeconfigu redmodepossiblevalues memorymemoryspeedpos siblevalues memorymemorymodepossi blevalues Value of the deconfigured mode of the reliability, availability, and supportability (RAS) configuration One of the values included in this array can be set to Processors.HardwarePrefetcher. Values depend on EFI firmware versions. One of the values included in this array can be set to Processors.Hyper-Threading. Values depend on EFI firmware versions. Value of the hardware Prefetcher for Processors Value of the DDR voltage level for operating modes Possible values of the deconfigured mode for the reliability, availability, and supportability (RAS) configuration. One of the values included in this array can be set to RASConfiguration.DeconfiguredMode. Values depend on EFI firmware versions. One of the values included in this array can be set to Memory.MemorySpeed. Values depend on EFI firmware versions. One of the values included in this array can be set to Memory.MemoryMode. Values depend on EFI firmware versions. processorshyperthreading Hyperthreading value for processors memorysocketinterleavep ossiblevalues processorsturbomodeposs iblevalues Possible values for the memory socket interleave. One of the values included in this array can be set to Processors.HyperThreading. Values depend on EFI firmware versions. One of the values included in this array can be set to Processors.TurboMode. Values depend on EFI 80 Using Adapter Workflows

81 memorymemoryspeed memorysocketinterleave operatingmodesddrvoltag elevelpossiblevalues memorymemorymode processorsturbomode firmware versions. Memory speed value for memory Value of socket interleave for memory One of the values included in this array can be set to RAS Configuration.DeconfiguredMode. Values depend on EFI firmware versions. Memory mode value for memory Turbo mode value for processors Turn Off Server LID Turn Off Server LID sets the LID light for a specified server to the off position. Type Required? selectedserver HitachiComputeConnecto Required Selected server r:hitachiserver message Turn On Server LID Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Turn On Server LID switches the LID light to an on position. Type Required? selectedserver HitachiComputeConnector: Required Selected server HitachiServer message Message of the result. If it is successfully executed, the message should be Completed. Otherwise, it returns an error message. Using Adapter Workflows 81

82 Get Server LPAR FC Port Information Get Server LPAR FC Port Information retrieves the information of all available Fibre Channel ports for LPARs on a specified Hitachi server. Type Required? selectedserver HitachiComputeConnector: HitachiServer Required The output type is HitachiComputeConnector:ServerLPARFCPort. Selected server serveruniquekey pcino Vendor device formattedslotno slotno portno vfcid wwpn wwnn migrationwwpn migrationwwnn busno devno funcno allocation assignedlparno Server unique key PCI number Vendor Device name Formatted slot number Slot number Port number VFC ID WWPN WWNN Migration WWPN Migration WWNN Bus number Dev number Func number Allocation Assigned LPAR number. (When this FC port is not assigned to any LPAR, the value is set to -1.) Get Server LPAR NIC Port Information Get Server LPAR NIC Port Information gets the information of all available NIC ports for LPARs on a specified Hitachi server. 82 Using Adapter Workflows

83 Type Required? selectedserver HitachiComputeConnector: Required Selected server HitachiServer The output type is HitachiComputeConnector:ServerLPARNICPort. serveruniquekey pcino vendor device formattedslotno slotno portno busno devno funcno allocation assignedlparno sharednicno sharednicsegment packetfilter sriovsupport vfmacaddresseditable vfvlanundeffeditable vfvlantageditable vfvlanuntageditable vfprmthrougheditable vfprmrestricteditable vftxrateeditable vftxratemax vftxratemin Server unique key PCI number Vendor Device name Formatted slot number Slot number Port number Bus number Dev number Function number Allocation Assigned LPAR number. (When this NIC port is not assigned to any LPAR, the value is set to -1.) Shared NIC number Shared NIC segment Packet filter SR-IOV VF MAC Address Editable VF VLAN Undefine Editable VF VLAN Tag Editable VF VLAN Untag Editable VF Promiscuous mode through Editable VF Promiscuous mode restrict Editable Whether transmission rate is editable Maximum transmission rate Minimum transmission rate Using Adapter Workflows 83

84 vftxratestep Incremental step value for transmission rate Get Switch Modules Get Switch Modules obtains information about all active LAN and Fibre Channel switches for a chassis. Type Required? selectedcha ssis HitachiComput econnector:ch assis Required Selected chassis The output type is HitachiComputeConnector:SwitchModuleInfo. chassisuniquekey switchuniquekey defaultgateway firmwareversion healthstatus installstatus ipaddress lidcolor lidstatus maintenancemode modelnumber powerstatus serialnumber slotno subnetmask switchtype Unique key among all managed chassis, servers (blades/racks/generic servers), and switch modules (including third-party vendors) Unique key among all of managed chassis, servers (blades/racks/generic servers), and switch modules including third-party vendors Default gateway Version of the firmware Health status: NORMAL, WARNING, FAIL, UNKNOWN Install status: INSTALL, NOT_INSTALL, NA IP address Lid color: BLUE, GREEN, RED, ORANGE, UNKNOWN Lid status: ON, OFF, BLINKING, SLOW_BLINKING, FAST_BLINKING, UNKNOWN Indicates whether a server is in maintenance mode Options: TRUE, FALSE Model number Power status: ON, OFF, Unknown Serial number of this switch module Slot number of this switch module Subnet mask Examples: 84 Using Adapter Workflows

85 1Gb LAN SW, 1/10Gb LAN SW, 10Gb DCB Switch Module, LAN pass through, 1Gb 40 ports LAN SW, Unknown 8Gb FC SW, Unknown Cold Migrate LPAR Cold Migrate LPAR migrates an LPAR when its host operating system is in shutdown mode. LPAR migration is an operation to transfer an LPAR from one server blade to another one. The LPAR migration maintains server blade resource settings, such as CPU, memory, and Network Interface Card (NIC). The scheduling mode for every controller on the NIC cards mounted on the same slot location is set to the same mode on the source and destination server blades. Supported Server Blade Models The following table details blade models that Cold Migrate LPAR supports. Supported Server Blade Model Platform Supported Model CB2500 CB520H Server Blade B3 CB520X Server Blade B1 CB500 CB520H Server Blade A1, B1, A2, B2, B3 CB520A Server Blade A1 CB540A Server Blade A1, B1 CB520X Server Blade B1 Restrictions The following list details restrictions on resources assigned to LPAR when running Cold Migrate LPAR. Network Interface Card ports are assigned in shared mode. Fibre Channel Host Bus Adapter ports are assigned in shared mode. The Source LPAR status must be in Activate or Deactive mode and not in Fail mode. LPAR cannot be migrated within the same server blade. The migrate operation can be from one blade to another blade. The following list details restrictions for Cold Migrate LPAR. Using Adapter Workflows 85

86 The LPAR name cannot be NO_NAME. No LPARs with the same name can exist on the destination server blade. The following list details general blade environment restrictions when running Cold Migrate LPAR. Source and destination servers have to be the same model, such as A1-A1, B1- B1, etc. The number of physical processors must be matched on both source and destination. Symmetric Multiprocessing (SMP) configurations for the CB520X server blade must match between blades, such as 1-blade to 1-blade, 2-blade SMP to 2- blade SMP, and 4-blade SMP to 4-blade SMP. Requirement of NIC Configuration The following list details requirements for NIC configuration. Every NIC with the same number of ports is installed in a slot with the same PCI device number on the source and destination server blades. The scheduling mode for every controller on the NIC cards mounted on the same slot location is set to the same mode on the source and destination server blades. Requirement of FC HBA Configuration The following items detail requirements for the Fibre Channel Host Bus Adapter configuration. Device FC HBA Type Cards Number of Accompanying Ports Relative Slot Numbers Device on the source matches Device on the destination server blades. Each instance of Device can be confirmed on the Migration Config Viewer window. FC HBA cards, such as a Mezzanine or expansion card, on the source match FC HBA cards on the destination server blades. The number of ports that accompany the FC HBA cards on the source matches the number that accompany the destination server blades. The relative slot numbers on which the FC HBA cards are located on the source match the numbers on the destination server blades. 86 Using Adapter Workflows

87 Hitachi Fibre Channel Firmware Version The following list details Fibre Channel versions supporting Hitachi Fibre Channel boards. Type Hitachi Gigabit Fibre Channel Board 4 Gbps Hitachi Gigabit Fibre Channel Board 8 Gbps Hitachi Fibre Channel FW Version B or higher 3x or higher The following table details input properties. Hot Migrate LPAR Type Required? srcserver HitachiCo Required Source server mputecon nector:hit achiserver srclparno Number Required Source LPAR number destserver HitachiCo Required Destination server mputecon nector:hit achiserver destlparno Number Optional Destination LPAR number. If the user used -1 or blank cpugroupno Number Required Destination CPU group Hot Migrate LPAR migrates an LPAR when its host operating system is in running mode. LPAR migration maintains server blades resource settings such as CPU, memory, NIC, FC HBA, Mac Address, and WWNs that are assigned to the source LPAR. They are transferred along with other configuration data. Supported Server Blade Models The following table details blade models that Hot Migrate LPAR supports. Supported Server Blade Model Platform Supported Model CB2500 CB520H Server Blade A1 CB520X Server Blade B1 CB500 CB520H Server Blade A1, B1, A2, B2, B3 CB520A Server Blade A1 CB540A Server Blade A1, B1 Using Adapter Workflows 87

88 Supported Server Blade Model CB520X Server Blade Platform Supported Model B1 Restrictions The following list details restrictions on resources assigned to LPAR when running Hot Migrate LPAR. The minimum time required for performing Hot Migrate LPAR: LPAR with 4 GB Memory: 5 minutes LPAR with 8 GB memory: 6 minutes Naming restrictions for Hot Migrate LPAR: The LPAR name cannot be NO_NAME No LPARs with the same name exist on the destination server blade Shared Mode operation restrictions: NIC ports are assigned in Shared Mode FC HBA ports are assigned in Shared Mode General restrictions: Source LPAR status must be in Activate mode An LPAR cannot be migrated within the same server blade. The migration can be from one blade to another. The source and destination servers have to be the same model (for example, A1-A1, B1-B1, etc.) The number of physical processors must match across source and destination. NIC Configuration Requirements Every NIC card with the same number of ports is installed in a slot with the same PCI. The device number on the source must match the device number on the destination server blades. Device strings can be confirmed on Migration Config Viewer window. The type of FC HBA card, such as Mezzanine card or expansion card, on the source must match the type on the destination server blades. The number of ports that accompany FC HBA cards on the source must match the number that accompany FC HBA cards on the destination server blades. 88 Using Adapter Workflows

89 The relative slot numbers on which FC HBA cards are located on the source match the relative slot numbers on the destination server blades. The following table details input properties. Type Required? srcserver HitachiComputeCon Required Source server nector:hitachiserver srclparno Number Required Source LPAR number destserver HitachiComputeCon Required Destination server nector:hitachiserver destlparno Number Optional Destination LPAR number. If the user used -1 or blank cpugroupno Number Required Destination CPU group Recover Failed LPAR Migration Recover Failed LPAR Migration recovers from a failed LPAR hot or cold migration. AutoDeploy ESXi Type Required? srcserver HitachiComputerCon Required Source server nector:hitachiserver srclparno Number Required Source LPAR number destserver HitachiComputeCon Required Destination server nector:hitachiserver destlparno Optional Destination LPAR number. If the user used -1 or blank, the LPAR number is ignored. AutoDeploy ESXi deploys VMware ESXI 6.x on a specified blade using VMware AutoDeploy feature. The blade must be in the PowerOff state. Prerequisites AutoDeploy configuration at vrealize Orchestrator 1. Upload and install the AutoDeploy plug-in at vrealize Orchestrator. 2. Ensure that the AutoDeploy service is running at the Orchestrator server. Using Adapter Workflows 89

90 3. From the workflows, run Add an Auto Deploy Host to add the Auto Deploy host to the session. TFTP boot server 1. Install SolarWind TFTP (free) or Windows TFTP features. 2. Install TFTP boot image: add a boot image to your TFTP server root directory. 3. In the vsphere client, click the Auto Deploy plug-in, and then download the TFTP Boot zip. Unzip into the TFTP s root directory. DHCP/DNS server To be able to perform a PXE boot, set option 66 and 67 in your DHCP scope. Open the scope on your DHCP server, and then add the following options. 066 Boot server host name: <TFTP_ipaddress/PXE_bootserver_ipaddress> 067 Boot filename: undionly.kpxe.vmw-hardwired If the system has an option for PXE client (WDS need this option) removes it. Start Auto Deploy service on a Windows server that contains vsphere vcenter. vsphere PowerCLI 1. Install PowerCLI (same version as the vcenter s version) 2. Creates a directory on the vcenter server s machine to store the offline image, such as C:\ESXI-Images. 3. Download and unzip the offline depot from the VMware web site VMware- ESXI depot.zip. 4. Creates a directory on the vcenter server s machine to store Hitachi s ESXI driver, such as C:\HitachiDrivers. 5. Download and unzip the current Hitachi driver package from the VMware web site: VMW-ESX hfcndd zip. 6. Connects to the vcenter using PowerCLI Connect-VIServer server User administrator@vsphere.local Password Hitachi1! 7. Clones a new profile: New-EsxImageProfile CloneProfile ESXI standard SIE Deploy Profile Vendor Hitachi 8. Add Hitachi driver to that profile. 90 Using Adapter Workflows

91 Add-EsxSoftwareDepot C:\HitachiDriver\VMW-ESX hfcndd offline bundle zip Add-EsxSoftwarePackage ImageProfile SIE Deploy Profile SoftwarePackage hfcndd 9. Create a new deploy rule. New-DeployRule HitachiBlade Item SIE Deploy Profile Pattern mac-d4:3d:73:78:f9:f2 Or New-DeployRule HitachiBlade Item SIE Deploy Profile Pattern ipv Activate the new deploy rule. Add-DeployRule HitachiBlade Type Required? Server HitachiComputeCon Required Source server nector:hitachiserve r AutoDeployHost AutoDeploy:AutoDe ploy Required AutoDeploy host DeployProfilename String Required Deploy profile name Add Hitachi Compute Webservice Host Add Hitachi Compute Webservice Host configures the Hitachi Compute plug-in for vro to access its Webservice component (Hitachi Compute Connector Service for vrealize Orchestrator). This workflow is a prerequisite before running any Quanta management workflow. Type Required? IPAddress String Required Hitachi Compute Webservice IP address or Hostname HttpsPort String Required Hitachi Webservice HTTPS Port For connecting to Hitachi UCP Advisor, the default TCP port is Using Adapter Workflows 91

92 Type Required? For connecting to Hitachi Compute Connector, the default TCP port is HttpPort String Required Hitachi Webservice HTTP Port For connecting to Hitachi UCP Advisor, the default TCP port is For connecting to Hitachi Compute Connector, the default TCP port is SSL Boolean Required Configure the web service to use SSL or not Note Hitachi Compute Web Service host software comes with the general installation package. The only external component is CCI which is available from support.hds.com at the following link: ail.html?ppid=1067&d=command-control-interfaceenterprise Get CPU for Quanta Server Get CPU for Quanta Server obtains the CPU information of a Quanta server. Type Required? Selected Server HitachiServer object Required Selected server The output type is PowerShellRemoteObject. It has the following properties: Location Location of the processor (for example, CPU0) Frequency Frequency of the processor (for example, 2400 MHz) Model Model name of the processor (for example, Haswell) Manufacturer Manufacturer name of the processor (for example, Intel) ProcessorIndex Index (from 1) of the processor Status Status of the processor slot (processornotpresent, 92 Using Adapter Workflows

93 processorpresent) Get Fan for Quanta Server Get Fan for Quanta Server obtains the fan information of a Quanta server. Type Required? SelectedSer ver HitachiServe r object Required Selected server The output type is PowerShellRemoteObject. It has the following properties: FanIndex Index (from 1) of the fan device Status Status of the fan device (other, unknown, ok, noncriticalupper, criticalupper, nonrecoverableupper, noncriticallower, criticallower, nonrecoverablelower, failed) Location Location name of the fan device (for example, Fan SYS0 1) Reading Rotation speed of the fan device (for example, 3900). If this value cannot be determined by software, then a value of -99 returns. UpperNonRecov erablethreshold Update Blade firmware Upper NonRecoverable Threshold for the fan sensor. If this value cannot be determined by software, then a value of - 99 returns. Update Blade firmware updates the firmware to a specified blade. It requires you to power off the blade. Type Required? selectedserver HitachiCompu teconnector: Server Required The server the operation to be performed on bladefirmwarefil epath String Required The path of the blade firmware file(smb) Username String Optional The user name for access to Using Adapter Workflows 93

94 Type Required? the SMB share if the firmware is located on an SMB share. Password String Optional The password name for access the SMB share if the firmware is located on an SMB share. Message The message of the result. If it is the successfully executed, the message should be Completed. Otherwise it returns the error message. Update Chassis firmware Update Chassis firmware updates the firmware of the management module to a specified chassis. Type Required? selectedchassis Hitachi Comput econne ctor:ch assis Required The chassis the operation to be performed on chassisfirmwarefil epath String Required The path of the chassisfirmware file(smb only) Username String Optional The user name for access the SMB share if the firmware is located on a SMB share. Password String Optional The password for access the SMB share if the firmware is located on a SMB share. Message The message of the result. If it is successfully executed, the message should be Completed. Otherwise it returns the error message. 94 Using Adapter Workflows

95 Disable Server MAC Address Disable Server MAC Address disables the additional MAC addresses of all NIC ports by resetting them to the original value on a specified server. Type Required? selectedserver HitachiComputeConnector: HitachiServer Required The selected server Message The message of the result. If it is successfully execuated, the message should be Completed. Other wise it returns the error message. Disable Server WWN Disable Server WWN disables the additional WWPN and WWNN of all FC ports by resetting them to the original value on a specified server. Type Required? selectedserver HitachiComputeConnector:Hitac hiserver Required The selected server The output type is. It has the following properties: message The message of the result. If it is successfully executed, the message should be Completed. Other wise it returns the error message. Get Server MAC Address Lastset Get Server MAC Address Lastset enables you to retrieve information that last Set ServerMAC workflow successfully set to the server, although the value might not be actually effective on the EFI. If a user want to retrieve the current MAC addresses on a given server, then use Get-ServerNICPort. Get-ServerMACLastSet is supposed to be used for helping the user to know what value has been successfully set to the server as Using Adapter Workflows 95

96 the additional MAC addresses last time. If it is a new blade, the lastset value can be 0 by default. Type Required? selectedserver String Required The BMC IP address of a server serveruniquekey Unique key among all of managed chassis, servers(blades/racks/generic Computers), and switch modules including 3rd paty vendor's. serverbladenum Blade number which has this NIC card. ber cardslotnumber Slot number cardtype Card Type: MEZZANINE, PCI, ONBOARD controllernumbe Controller number r portnumber Port number macaddress MAC address (i.e., 00:1f:67:0b:02:00) originalmacaddr ess Get Server WWN Lastset The original MAC address. If the nic port is not existed, the value will be null. Get Server WWN Lastset enables the user to retrieve information that the Set Server WWN workflow set to the server. Note the value might not actually be effective on the EFI. If you want to obtain the current WWN on a given server, use Get HBA Ports. If it is a new blade, the lastset value can be 0 by default. Type Required? SelectedSer HitachiComputeConnector Required The selected server ver :HitachiServer 96 Using Adapter Workflows

97 partitionnumber serverbladenum ber cardslotnumber cardtype portnumber wwpn wwnn The partition number of the blade Blade number which has this NIC card. Slot number Card Type: MEZZANINE, PCI, ONBOARD Port number WWPN WWNN Set Server MAC Address Set Server MAC Address sets additional MAC address of all NIC ports regardless if those ports exist on a specified server. Specify the server by typing the server IP address in the cmdlet input parameters. Also, users can specify one new MAC address with the CardSlotNumber, PortNumber and ControllerNumber parameters at a time. Considerations for this workflow are: This workflow sets additional MAC addresses on all NIC ports regardless existence of corresponding devices. You can only specify one MAC address at a time. If you want to specify multiple MAC addresses, run this workflow multiple times. This workflow does not check consistency among MAC addresses. The value set to the NIC port is applied when the server is turned on. The target server must be in power off status when the API is issued. Issue the Get Server MAC Address LastSet workflow to get all MAC addresses that have been set during the last session, then select the MAC address you want to edit. Type Required? selectedserv er controllernu mber HitachiComp uteconnecto r:hitachiser ver Required The selected server string Required The number of the controller of the NIC port Using Adapter Workflows 97

98 Type Required? cardslotnum ber string Required The number of the card slot of the NIC port portnumber number Required The port number of the NIC port macaddress string Required MAC address Message The message of the result. If it is successfully executed, the message should be Completed. Otherwise it returns the error message. Set Server WWN Set Server WWN sets additional WWNs of all FC ports regardless if those ports exist on a specified server. Specify the server by typing the server IP address in the workflow input parameters. Also, you can specify one new WWPN and WWNN with the CardSlotNumber, PortNumber parameters at a time. Considerations for this workflow are: This workflow sets additional WWNs on all FC ports regardless of the existence of corresponding devices. You can only specify one pair of a WWPN and a WWNN at a time. If you want to specify multiple WWNs, please run this cmdlet multiple times. This workflow does not check consistency among WWNs. The value set to the FC port is applied when the server is turned on. The target server must be in power off status when the workflow is issued. Issue the Get-ServerWWNLastSet cmdlet to retrieve all WWNs that have been set during the last session, then select the WWN address you want to edit. Type Required? selectedserv HitachiComp Required The selected server er uteconnecto r:hitachiser ver cardslotnum ber string Required WWPN 98 Using Adapter Workflows

99 Type Required? Wwnn string Required WWNN message The message of the result. If it is successfully executed, the message should be Completed. Otherwise it returns the error message. Remove Chassis Remove Chassis removes the selected chassis from the vro inventory. Type Required? selectedcha Required ssis message Remove Server HitachiComp uteconnecto r:chassis The chassis the operation to be performed on The message of the result. If it is successfully execuated, the message should be Completed. Other wise it returns the error message. Remove Server removes the selected server from the vro inventory. Type Required? selectedserv er HitachiComp uteconnecto r:hitachiser ver Required The selected server message The message of the result. If it is successfully execuated, the message should be Completed. Other wise it returns the error message. Using Adapter Workflows 99

100 100 Using Adapter Workflows

101 Logging and Troubleshooting This chapter includes the following sections: Logging Troubleshooting Logging and Troubleshooting 101

102 Logging Log Files Log Format The Hitachi Compute Connector for vrealize Orchestrator writes to the following log file: HitachiComputeConnectorLog.log The Adapter generates an individual log file. It is created at this location: <VRO installation directory>\appserver\bin\hitachicomputeconnectorlog.log Default path: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\bin\HitachiComputeConnectorLog.log The individual log file records the logging statement of the Adapter. Additionally, log statements are also recorded on vro server.log. Default path: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\logs The server.log file, however, handles the logging statements of all VMware vrealize Orchestrator plug-ins, making it more difficult to get the logging information that belongs only to the Hitachi Compute Connector for VMware vrealize Orchestrator adapter. Hitachi Compute Web Service logs can be found at C:\Program Files\Hitachi\Hitachi Compute Connector for vro\log\hivcenter.log An example of the log format follows: # Hitachi log message format: [ProcessID{:ThreadID}] [Timestamp] [Module IDentifier] [Message Level] [Message Code] {Message source:} Message # Sample [557410] [12/10/14-17:52:24] [WorkflowExecutorPool-Thread-2] INFO [Message Code] HitachivCOServer: ENTER [ Logging and Troubleshooting

103 Log Rotation ](com.hitachi.server.model.hitachiserver::getserverinfo) Generating multiple logs and replacing old logs with new ones is a policy that enables multiple generations of Hitachi Adapter logs to be created. The number of saved logs is limited by a user-specified log size or a system storage default of 5 MB. When the log file HitachiComputeConnectorLog.log exceeds 5_MB (1 MB=1024 bytes), it is renamed HitachiComputeConnectorLog.log.1, and the system creates a new log file <logfilename>. If a file named HitachiComputeConnectorLog.log.1 already exists, the system creates HitachiComputeConnectorLog.log.2 and so on. The maximum number of backup logs is specified by the MaxBackupIndex value in the log configuration file. The default is 4. Log Configuration File Logging Levels Log files for the Hitachi Adapter are configured using the file Log4J.xml. By default, the configuration file is saved at this location: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\conf\ The Hitachi Compute web service supports the following logging levels. Logging Level OFF ERROR INFO DEBUG Severity Level None FATAL ERROR FATAL ERROR WARN INFO FATAL ERROR WARN INFO DEBUG TRACE The adapter can output ERROR, INFO, and DEBUG logging statements. The default log level is INFO. The user can change the logging level to retrieve the Logging and Troubleshooting 103

104 appropriate log statements. For example, users can set the logging level as DEBUG to get the DEBUG statement for troubleshooting purposes. The INFO logging level is sufficient for most cases. Because of the adverse performance impact, using the DEBUG logging level in a production environment is not recommended. Changing the Logging Level To change the logging level, follow these steps: 1. Locate log4j.xml. By default, the file is located here: C:\Program Files\VMware\Infrastructure\Orchestrator\appserver\conf\ 2. Open the log4j.xml file using any text editor. 3. Search for the root category. Change its priority to the required logging level. In the example that follows, the logging level is set to DEBUG: 4. Save the log4j.xml file. 5. Stop, and then restart the VMware vrealize Orchestrator Server service. All subsequent service requests are logged at the DEBUG level. 104 Logging and Troubleshooting