Hitachi Storage Connector for VMware vrealize Orchestrator User s Guide v01.3.0

Transcription

1 Hitachi Storage Connector for VMware vrealize Orchestrator User s Guide v FASTFIND LINKS Platform Support Hardware and Software Requirements Getting Help MK-92ADPTR108-03

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 Contents... 3 Preface Introduction System Requirements Supported Operating Systems...24 Supported Interfaces Installation and Configuration Preliminary steps (all devices)...28 Hitachi vro Connector web service configuration...28 Modular arrays...28 Enterprise arrays...28 Hitachi NAS (HNAS) devices...29 Run Hitachi-vROStorageConnector-setup(01.3.0)-(x64)-01.exe 29 Add the plug-in component to vrealize Orchestrator...29 Configuring Windows Service Access...30 Using HTTPS (Optional)...31 Implementing the certificate...33 Modular Arrays...33 Contents 3 Hitachi Storage Connector for VMware vrealize Orchestrator User's Guide

4 Enterprise Arrays Java Runtime Environment Hitachi Command Control Interface (CCI) Hitachi NAS (HNAS) devices Uninstalling the Hitachi Storage Connector from the Orchestrator Server Upgrading Hitachi Storage connector for vrealize Orchestrator.. 36 Supported Configurations Hitachi Storage Workflows Hitachi vro Connector Web Service Configuration Add Hitachi Storage Web service host Modify Hitachi Storage Web service host Delete Hitachi Storage Web service host Storage Subsystem Profile Add Enterprise Subsystem Profile Add HNAS Profile Add Modular Array Profile Add V2I Server Profile Delete Subsystem Profile Block Storage Configuration Add Modular Array Add Enterprise Array Add Enterprise Subsystem using credential Add Modular Array using Credential Close all Storage Array Connections Add Virtual Storage Array Get Virtual Storage Arrays Get Registered Storage Arrays Block Provisioning Create LU in Parity Group Contents

5 Create LU in Dynamic Pool...50 Create LU in RAID Group...51 Delete LU...52 Present LU...52 Unpresent LU...53 Get LUs...53 Get Hostgroups...54 Get Hostgroups associated with an LU...55 Get Hostgroups associated with a WWN...55 Get WWNs associated with a target port...55 Create Hostgroup...56 Delete HostGroup...57 Add WWN(s) to Hostgroup...57 Remove WWN(s) from Hostgroup...58 Expand LU Size...58 Create Dynamic Pool using LDEV(s)...59 Create Dynamic Pool on Enterprise Array...60 Delete Dynamic Pool Using Pool ID...60 Delete Dynamic Pool Using Pool name...61 Expand Pool Using Pool ID...61 Expand Pool Using Pool Name...62 Shrink Pool Using Pool ID...62 Shrink Pool Using Pool Name...63 Get Storage Pool...64 Create V-VOL...64 Create V-VOL with autogenerated LU ID...65 Get Host Groups for Port...65 Block ShadowImage...66 Create ShadowImage Pair...66 Delete ShadowImage Pair...67 Resync ShadowImage Pair...68 Introduction 5

6 Split ShadowImage Pair Restore ShadowImage Pair Get ShadowImage Pairs Create ShadowImage Pair with Consistency Group Split ShadowImage Group Block Snapshot Backup Create Modular Array Snapshot Pair Create Enterprise Array Snapshot Pair Restore Snapshot Pair Delete Snapshot Pair Resync Snapshot Pair Split Snapshot Pair Create Modular Snapshot Pair: named Delete Snapshot Pair: named Split Snapshot Pair: named Restore Snapshot Pair: named Resync Snapshot Pair: named Get Snapshot Pairs Get Snapshot Pairs: named Create Enterprise Snapshot Pair with Group Name Create Enterprise Snapshot Pair without VVOL Create Modular Snapshot Pair with Consistency Group Split Snapshot Group Delete Snapshot Group using Group name Resync Snapshot Group using Group name Restore Snapshot Group using Group name Split Snapshot Group using Group Name Map HTI Floating Snapshot Volume Unmap HTI Snapshot Volume Block TrueCopy Create TrueCopy Pair Contents

7 Delete TrueCopy Pair...86 Resync TrueCopy Pair...87 Split TrueCopy Pair...88 Get TrueCopy Pairs...88 Create Global Active Device Pair...89 Create Universal Replication Pair...90 Block - iscsi Targets...91 Create iscsi Target...91 Add an Initiator to iscsi Target...92 Remove an Initiator from an iscsi Target...92 Present LU: iscsi...93 Unpresent LU: iscsi...93 Get iscsi Targets...94 HNAS Workflows File/Storage Configuration...94 Add HNAS...94 Add HNAS using credential...95 Get registered HNAS Fileserver...95 HNAS Workflows File/Provisioning...95 Create File Clone...95 Create Filesystem...96 Delete File System...96 Create NFS Export...97 Delete NFS Export...98 Add Root Hosts to NFS Export...99 Add RW hosts to NFS Export Remove Root Hosts from NFS Export Remove RW Hosts from NFS Export Set Filesystem Size Set NFS Export Size Set Filesystem Syslock Get Filesystems Introduction 7

8 Get NFS Exports Get NFS Exports: by Export Name Get NFS Exports: by NFS Client(s) Mount Filesystem Unmount an HNAS Filesystem Create Filesystem snapshot Delete Filesystem Snapshot Get Filesystem Snapshots High-level workflows Backup ESXi Datastore Mount the most recent VM backups Provision ESXi Datastore using HNAS NFS export Smart Provision a LUN/Datastore to a host/cluster Self service VM recovery Supporting Workflows Convert Datastore to a PVOL number Get ESXi Host WWN Provision an NFS export to an ESXi host Hitachi Virtual Infrastructure Integrator V2I Configuration Add V2I Server Connect VIServer using credential Snapshot Backup Clone VM Restore VM to Alternate Backup VM Backup All V2I managed VMs Mount VM UnMount VM Get list of Backups Contents

9 V2I Backup Group Create Backup Group Add Backup group member Get Backup group members Delete Backup Group member Get Backup groups Troubleshooting Hitachi Storage Connector Logs Hitachi Storage Web Service Log Modifying the Log Level Hitachi Log Message Format Error Codes Abbreviations, Terms, and Acronyms Introduction 9

10 Preface Intended Audience Software Version Release Notes Reference Documents Document Conventions Convention for Storage Capacity Values Getting Help Comments Note The use of Hitachi Storage Connector for VMware vrealize Orchestrator and all other Hitachi Data Systems products is governed by the terms of your agreement(s) with Hitachi Data Systems. Preface 10 Hitachi Storage Connector for VMware vrealize Orchestrator User's Guide

11 Intended Audience Release Notes This document is intended for VMware Administrators and Hitachi Storage Administrators familiar with the supported Hitachi subsystems and VMware software, including: VMware vrealize Orchestrator (formerly VMware vcenter Orchestrator) VMware vsphere VMware ESXi Release notes are 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. Reference Documents Hitachi Command Control Interface Installation and Configuration Guide, MK-91DF8306-XX Hitachi Command Control Interface Command Reference, MK-90RD7009- XX Hitachi Command Control Interface User and Reference Guide, MK- 90RD7010-XX Hitachi Virtual Storage Platform G1000/Hitachi Universal Volume Manager User s Guide, MK-92RD8024-XX Hitachi Virtual Infrastructure Integrator Quick Start Guide, MK- 92HNAS Introduction 11

12 Document Conventions This document uses the following typographic conventions: Convention Bold Italic screen/code < > angled brackets [ ] square brackets Description Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a variable, which is a placeholder for actual text provided by you or the system. Example: copy sourcefile target-file Indicates text on screen or that you enter Example: # pairdisplay -g oradb Indicates a variable, which is a placeholder for actual text provided by you or the system. Example: # pairdisplay -g <group> Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important and/or additional information. Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Caution Warns you about adverse conditions and/or consequences (for example, disruptive operations). 12 Preface

13 Icon Label Description WARNING Warns about severe conditions and/or consequences (for example, destructive operations). Convention for Storage Capacity Values We calculate physical storage capacity values (for example, disk drive capacity) 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 We calculate logical storage capacity values (logical device capacity) based on the following values: Logical Capacity Unit Value 1 KB 1,024 (2 10 ) 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 Introduction 13

14 Getting Help Comments 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, please visit the support web site 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, please provide as much information about the problem as possible, including: The circumstances surrounding the error or failure. The exact content of any error message(s) displayed on the host system(s). Please send us your comments on this document: doc.comments@hds.com. Include the document title, number, and revision, and refer to specific section(s) and paragraph(s) whenever possible. Thank you! (All comments become the property of Hitachi Data Systems Corporation.) 14 Preface

15 Introduction 15

16

17 Introduction Overview Conceptual Diagram High-Level Network Diagram Introduction 17

18 Overview Hitachi Storage Connector for VMware vrealize Orchestrator adds workflows to vrealize Orchestrator that automate configuration and provisioning operations on Hitachi storage devices. By combining the workflows provided by this product with those provided by VMware, it is possible to automate provisioning ESXi datastore, end-to-end VM deployments and other operations that include Hitachi storage devices. For example, a Clone VM workflow allows you to clone a virtual machine that is backed up on Hitachi storage. Main Components Hitachi Storage Connector This software installs as an addition to vrealize Orchestrator and adds Hitachi workflows to the Orchestrator library. It sends storage operations triggered by workflows to the web service component to be carried out. This component is represented by a file named o11nplugin-hsc.dar. Hitachi Storage Web Service This is a Windows service named Hitachi Storage Connector Service for vrealize Orchestrator. It communicates with the plug-in using HTTP or HTTPS, and performs storage operations requested by the connector. 18 Introduction

19 Conceptual Diagram Introduction 19

20 High-Level Network Diagram 20 Introduction

21 System Requirements Hardware Requirements Software Requirements Required Pre-operation Distribution Package System Requirements 21

22 Hardware Requirements The table below shows the hardware for the adapter. Note You must use Storage Navigator in Modify mode to perform Universal Volume Manager operations. In View mode, only Universal Volume Manager information is visible. Item Virtual Storage Platform Hitachi Unified Storage Hitachi Unified Storage VM Hitachi NAS Platform Two-Node System Virtual Storage Platform G1000 Virtual Storage Platform Gx00 Minimum Requirements /00 or newer 0980/P-S or newer /00 or newer Version or newer /00 or newer /00 or newer 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. Port Requirements Port Protocol Application / Storage 80 HTTP HNAS 443 HTTPS HNAS 1099 RMI Enterprise Storage Array RMI Enterprise Storage Array RMI Enterprise Storage Array 2000 TCP Modular Storage Array 22 TCP SSH 22 System Requirements

23 Port Protocol Application / Storage 2022 HTTP vro Web Service 2023 HTTPS vro Web Service 9000 TCP HNAS V2I Server 8443 TCP HNAS V2I Server / HNAS 860 TCP iscsi 3260 TCP iscsi Software Requirements The following table provides the support matrix for the storage adapter for the vsphere software suite. VMware vsphere 5.5 and 6.0 VMware vrealize Orchestrator 6.0.x and 7.0 VMware vrealize Automation 6.2.x and 7.0 Java Virtual Machine (JVM) JRE 7 x64 or higher Microsoft Visual C++ Microsoft Visual C SP1 Redistributable Package Hitachi Virtual Infrastructure Integrator 3.0 System Requirements 23

24 Configure Hitachi Virtual Infrastructure Integrator software to support VM management workflows placed under vro workflow Hitachi -> Storage -> File -> Snapshot Backup and V2I Backup Group using HNAS. Supported Operating Systems Windows Server 2008 R2 SP1 x64 Windows Server 2012 Note Windows Server 2012 R2 Hitachi recommends you update Windows with the latest patches for Hitachi Storage Connector for VMware vrealize Orchestrator. Supported Interfaces Hitachi Command Control Interface Version Note /04 Configure the Hitachi CCI to use enterprise array workflows. For more detail on CCI configuration, refer to Hitachi Command Control Interface (CCI) section Required Pre-operation Perform the following storage configuration for the related workflows before using Hitachi Storage Connector for VMware vrealize Orchestrator. Item License P.P. Controller Account Authentication License Dynamic Provisioning License Hitachi Storage Web Configuration The licenses of required P.P.s LUN Manager Account Authentication (optional) Dynamic Provisioning (optional) IP address is assigned for HUS controllers and VSP SVP You must install and enable the Account Authentication license in the subsystems to use the Account Authentication feature. Install and enable the Dynamic Provisioning license (D_PROVISIONING) in the subsystems to use the HDP feature. Install and run the Hitachi Storage Web service on a Windows host in order to access the Hitachi storage. 24 System Requirements

25 Item service Hitachi Virtual Infrastructure Integrator Configuration Install and configure on VMware vsphere web client to run V2I workflows Distribution Package The distribution package for Hitachi Storage Connector for VMware vrealize Orchestrator contains: The installer: Hitachi-vROStorageConnector-setup(01.3.0)- (x64)-01.exe User s Guide and Release Notes System Requirements 25

26 26 System Requirements

27 Installation and Configuration Installing the Connector for VMware vrealize Preliminary Steps Uninstalling the Connector for VMware vrealize Orchestrator Reinstalling the Connector for VMware vrealize Orchestrator Upgrading Hitachi Storage Connector for vrealize Orchestrator Configuring Hitachi UVM with VSP G1000 Supported Storage Functions New Workflows Workflows (Block Storage) Workflows (HNAS) High-level Workflows Installation and Configuration 27

28 Installing the Connector for VMware vrealize Orchestrator The steps required to install and configure Hitachi Storage Connector for VMware vrealize Orchestrator vary depending on the Hitachi storage device family being used: Modular arrays, Enterprise arrays, or Hitachi NAS (HNAS) devices. Preliminary steps (all devices) These preliminary steps are shared across all device families: Run this product s installer (Hitachi-vROStorageConnectorsetup(01.3.0)-(x64)-01.exe) on a supported Windows host Use VMware vrealize Configuration UI to import the plug-in provided by this product s installer <Install dir>\dist\o11nplugin-hsc.darin to vrealize Orchestrator and restart vrealize Orchestrator server to get the plugin installed. Use vrealize Orchestrator workflows provided by the plug-in to configure access between the plug-in and a Hitachi Windows service (also provided by this product s installer) Hitachi vro Connector web service configuration Modular arrays To run Hitachi Storage connector workflows, run Add Hitachi storage webservice host and provide the Hitachi storage connector web service installed IP or DNS name and the V2I installed IP address or DNS name as arguments. Modular family storage arrays are ready for use immediately following the preliminary steps. Enterprise arrays To use Enterprise family storage arrays, perform these additional steps on the same Windows host used to run Hitachi-vROStorageConnectorsetup(01.3.0)-(x64)-01.exe: Install Java Runtime Environment version 7, x64 edition Install and configure Hitachi Command Control Interface (CCI) for inband array management using an LDEV configured as a command device 28 Installation and Configuration

29 Hitachi NAS (HNAS) devices Most of the HNAS workflows work without requiring additional configuration. To allow all HNAS workflows to be used including those listed in the Snapshot Backup and V2I Backup Group folder: Preliminary Steps Install and configure Hitachi Virtual Infrastructure Integrator (V2I) on a Windows host supported by V2I Use the Connect VIServer workflow provided under Hitachi -> Storage - > File -> Storage Configuration to use Snapshot group and V2I Backup Group workflows Run Hitachi-vROStorageConnector-setup(01.3.0)-(x64)-01.exe On a supported Windows host, install Hitachi Storage Connector for VMware vrealize Orchestrator by running Hitachi-vROStorageConnectorsetup(01.3.0)-(x64)-01.exe. The installer adds two main components: the plug-in and a Windows service. The plug-in is a file located in C:\Program Files\Hitachi\vROStorageConnector\dist. The Windows service is named Hitachi Storage Connector Service for vrealize Orchestrator. Add the plug-in component to vrealize Orchestrator The plug-in component is represented by a file, and added to vrealize Orchestrator using VMware vrealize configuration UI. By default, the plug-in file is named o11nplugin-hsc.dar, and located in C:\Program Files\Hitachi\vROStorageConnector\dist. VMware vrealize Orchestrator is distributed in several different forms, including a Windows application and a Virtual Appliance. These instructions correspond to the Windows application. To install the plug-in to the Virtual Applicance, refer to VMware s documentation. 1. Copy the o11nplugin-hsc.dar plug-in file to the Windows host running vrealize Orchestrator, if necessary. 2. Start the VMware vsphere Orchestrator Configuration service. 3. Open the vcenter Orchestrator Home Page start menu item. 4. You will see a Getting Started with vcenter Orchestrator page. Click on the Orchestrator Configuration link. Installation and Configuration 29

30 5. You ll be prompted to log in. The default post-install credentials are vmware/vmware. 6. From the left-hand pane, select Plug-ins. 7. Scroll to the bottom of the right-hand pane, and find a text entry box labeled Plug-in file, with a magnifying glass icon next to it. Click on the magnifying glass icon, browse to o11nplugin-hsc.dar, and click Upload and install. 8. Once the plug-in has been installed, re-start the VMware vcenter Orchestrator Server service. 9. If an older version of the plug-in was already installed prior to these steps, you may see a message similar to this: 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 storage array 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. (Support for HTTPS is new in version v ) After the plug-in is installed in to vrealize Orchestrator, it is necessary to configure it to access the Windows service component (Hitachi Storage Connector Service for vrealize Orchestrator). Prior to version v of this product, this configuration was done using the VMware vcenter Orchestrator Web-based configuration interface. Beginning with v01.1.0, this configuration is done using vrealize Orchestrator workflows provided by the plug-in. 30 Installation and Configuration

31 1. Open the vcenter Orchestrator Client application from the start menu. 2. You will be prompted to log in. The default post-install credentials are vcoadmin/vcoadmin. 3. In the left-hand pane, select the blue Workflows tab. 4. Browse to Library -> Hitachi -> Storage -> Web service configuration. 5. Run the Add Hitachi Storage Web service host workflow. Notes on this workflow: This workflow only needs to be used one time after installing Hitachi Storage Connector for VMware vrealize Orchestrator. It is a one-time operation. It is only necessary to populate the HNAS V2I IP Address field if this product will be used to manage HNAS devices, and the specific workflows requiring V2I are desired (including those found in the Snapshot Backup and V2I Backup Group folder). To populate the Log Level field, choose Not set, then search for NORMAL to yield a value for the field. Other options are VERBOSE and MINIMAL. If HTTPS communication between the plug-in and Windows service is desired, choose Yes from the SSL radio-button. Note Additional steps are required before HTTPS communication will function. It is necessary to create an SSL certificate and configure vrealize Orchestrator to use it. Please see the Using HTTPS section for more information. Using HTTPS (Optional) Version v or later of this product added support for HTTPS communication between the plug-in and Windows service components. To use HTTPS support: 10. Choose SSL support while using the Add Hitachi Storage Web service host workflow (see the Configuring Windows service access section, above, for more information). 11. Obtain an SSL certificate. If the use of a self-signed certificate is desired, here is one way to generate one, using IIS: Installation and Configuration 31

32 Generating an SSL certificate 1. Start Internet Information Services (IIS) Manager. 2. Select the left-hand pane object representing the computer. 3. Open Server Certificates. 4. From the right-hand pane, select Create Self-Signed Certificate. 5. Provide an arbitrary friendly name and click OK. 6. Expand the left-hand pane object representing the computer, then select sites> Default Web Site. 7. Choose Bindings from the right-hand pane. 8. Click on Add, select https from the Type select-box and enter port 2023 (or any non-default HTTPS port number supplied to the Add Hitachi Storage Web service host workflow). 9. Select the self-signed certificate from the SSL certificate select-box and click OK. 10. Close the Site Bindings dialog box. 11. Enter mmc in the Run menu to open an initial MMC window. 12. Choose File > Add/Remove Snap-in. 13. Choose Certificates and click Add >. 14. Choose Computer Account, then Local Computer, and click OK. Exporting a certificate 1. Browse to Console Root > Certificates (Local Computer) > Personal > Certificates. The newly created certificate should appear in the right-hand pane. 2. Right-click on the newly created certificate and choose All Tasks> Export. 3. When prompted, choose No, do not export the private key, then choose to export a DER-encoded binary X.509 (.CER). 4. Click Finish to export the certificate. 32 Installation and Configuration

33 Implementing the certificate Modular Arrays 1. If necessary, copy the certificate to the computer where vrealize Orchestrator resides. 2. Log in to the vrealize Orchestrator Web-based configuration interface (the same interface used to add this product s plug-in component to vrealize Orchestrator). 3. Choose Network from the left-hand pane. 4. Select SSL Trust Manager from the right-hand pane. 5. Click on the magnifying glass icon next to Select a file to import, browse to the certificate file, and choose Import. 6. Re-start both the VMware vcenter Orchestrator Server and the Hitachi Storage Connector Service for vrealize Orchestrator services, to ensure that the SSL configuration takes full effect. No additional steps are necessary to use this product with Modular storage arrays. Enterprise Arrays Before using this product with Enterprise storage arrays, it is necessary to install a specific Java Runtime Environment, and to install Hitachi CCI. Java Runtime Environment Java Runtime Environment version 7, x64 edition should be installed on the same Windows host running the Hitachi Windows service (Hitachi Storage Connector Service for vrealize Orchestrator). Note The x64 JRE edition is specifically required. The more common 32-bit JRE edition will not work. Hitachi Command Control Interface (CCI) Prior to using this product with Enterprise storage arrays, Hitachi Command Control Interface (CCI) must be installed, configured and running. CCI is used to perform in-band array management on behalf of this product s workflows. CCI should exist on the same Windows host running the Hitachi Windows service (Hitachi Storage Connector Service for vrealize Orchestrator). Installation and Configuration 33

34 CCI supports several scenarios and its configuration can become complex. These notes may help you to get started quickly, and should yield a configuration sufficient for many of this product s workflows. For in-depth CCI configuration information, please refer to CCI s documentation. 1. Install CCI on the Windows host running this product s Windows service. 2. Edit the Windows TCP/IP services file to define a CCI service associated with UDP port 1000, by adding this single line to C:\Windows\system32\drivers\etc\services. horcm 1000/udp horcm 3. Choose (or create) an LDEV on the Enterprise storage array to act as a command device. 4. Configure the LDEV to be a command device, as shown by this screenshot: 5. Present the LDEV to the Windows host upon which the Hitachi Windows service is running. Ask the Windows host to re-scan, and ensure that the host sees the new LDEV. 6. Create a CCI configuration file named C:\Windows\horcm0.conf, containing these four lines. Replace with the Windows host s IP address, and \\.\PHYSICALDRIVE1 with the drive name corresponding to the command device. HORCM_MON horcm HORCM_CMD \\.\PHYSICALDRIVE1 34 Installation and Configuration

35 Note If it is difficult to determine which PHYSICALDRIVE device name corresponds to the command device LDEV, try this command in a Windows cmd window: C:\> wmic diskdrive list brief /format:list 7. Start a CCI process (instance). Supplying a zero to horcmstart asks CCI to create instance number zero. The CCI instance number is used as an input to some workflows provided by this product. C:\HORCM\etc\>horcmstart 0 8. If CCI fails to start, or to determine its status in detail, look at its log files in this folder. C:\HORCM\log0\curlog\ Hitachi NAS (HNAS) devices Many of the HNAS workflows will function without requiring any further configuration, yet some have additional dependencies (including those in the Snapshot Backup folder). For full use of all HNAS-related workflows, install and configure Hitachi Virtual Infrastructure Integrator (V2I) on the same Windows host configured to run the Hitachi Windows service. Uninstalling the Hitachi Storage Connector from the Orchestrator Server To remove the software from the Windows host: 1. Open the Windows Control Panel. 2. Choose Uninstall a program from Programs. 3. Select Hitachi Storage Connector for VMware vrealize Orchestrator and click Uninstall. This action removes the Hitachi Storage Web Service from the Windows host. This process cannot uninstall the vrealize Orchestrator plug-in. Uninstall the Orchestrator plug-in manually by deleting the.dar file from the Orchestrator server and restarting the Orchestrator Server. Please follow the VMware vrealize Orchestrator documentation in order to perform this operation. Installation and Configuration 35

36 Reinstalling the Connector for VMware vrealize Orchestrator To re-install the connector: 1. Copy the new.dar file to the Orchestrator server. 2. Follow the same process to install this new file. 3. The Connector file can be overwritten without uninstalling the old file. Upgrading Hitachi Storage connector for vrealize Orchestrator Hitachi does not support upgrades from an older version of a Hitachi Storage connector for vrealize Orchestrator to the current version. When you attempt to install a newer version this connector, Hitachi Storage connector for vrealize Orchestrator displays the following message: To install the current version of Hitachi Storage connector for vrealize Orchestrator, perform the following steps 1. Uninstall the older version. 2. Remove the plugin from vrealize Orchestrator manually. 3. Install the latest version of the storage connector. Configuring Hitachi UVM with VSP G1000 Hitachi Storage Connector for VMware vrealize Orchestrator supports Hitachi Universal Volume Manager, which works with the VSP-G1000 platform. When a system consists of multiple storage subsystems, a single host must usually connect to each subsystem. As a system administrator, you typically 36 Installation and Configuration

37 connect each system to the hosts, a process that may require several different types of procedures. With Hitachi UVM, you configure the connection from the host to the VSP G1000 storage system, then manipulate mapped volumes in an external storage system in the same way as volumes in the VSP G1000 storage system. Orchestrator among storage systems can also involve varied procedures. However, with Universal Volume Manager, you perform them with the same Hitachi software as when you use VSP G1000 systems. Supported Configurations This section outlines the Hitachi UVM configurations currently supported by the adapter. For further information, see Hitachi Virtual Storage Platform VG1000/Hitachi Universal Volume Manager User s Guide, MK-92RD8024-XX. Installation and Configuration 37

38 38 Installation and Configuration

39 Supported Storage Functions The Storage Connector supports FC for all supported storage arrays. It supports NFS for HNAS. It supports Block Device for all arrays and File Systems, File System snapshots, Virtual Volumes and NFS Exports for the HNAS device. The Storage Connector also supports orchestration of tasks such as automatic backup and restore of VMs on HNAS and vrealize environment through V2I management APIs. Installation and Configuration 39

40 40 Installation and Configuration

41 Hitachi Storage Workflows Hitachi vro Connector Web Service Configuration To run Hitachi Storage connector workflows, run Add Hitachi storage webservice host first and provide the Hitachi storage connector web service installed IP or DNS name and the V2I installed IP address or DNS name as arguments. Add Hitachi Storage Web service host This workflow add the web service configuration. This workflow is required to run once after new install or upgrade of the plugin. IP or hostname string IP or FQDN hostname of the web service machine HTTPS port string HTTPS port Default value is 2023 HTTP port string HTTP port Default value is 2022 SSL Boolean Use SSL over Default is True HTTP or not HNAS V2I IP string IP or FQDN or HNAS V2I service LogLevel Workflow object LOG_LEVEL object On Success: A message indicating success is returned. On Failure: An exception is thrown. Installation and Configuration 41

42 Modify Hitachi Storage Web service host This workflow modify the web service configuration. IP or hostname string IP or FQDN hostname of the web service machine HTTPS port string HTTPS port Default value is 2023 HTTP port string HTTP port Default value is 2022 SSL Boolean Use SSL over Default is True HTTP or not HNAS V2I IP string IP or FQDN or HNAS V2I service LogLevel Workflow object LOG_LEVEL object On Success: a message indicating success is returned. On Failure: an exception s thrown. Delete Hitachi Storage Web service host This workflow delete the web service configuration. On Success: a message indicating success is returned. On Failure: an exception s thrown. Storage Subsystem Profile users will be given a choice of storage class profiles that tie the user to specific resources such as storage pool, array ports, etc. Such Information as subsystem Serial number, user ID, password, horcminst, port, etc. will be stored in each profile and will be loaded using the Add Subsystem credential. This will reduce entering storage information every time to run the Add Subsystem workflows Add Enterprise Subsystem Profile This workflow adds an Enterprise Profile object to Orchestrator s repository, using the provided enterprise subsystem information. 42 Installation and Configuration

43 Library\Hitachi\Storage\Storage Subsystem Profile Name string Profile name This profile name has to be unique which will be used later on Subsystem Serial Number string Serial Number of the RAID subsystem that needs to be used (E.g for VSP) Hostname string Hostname of the IP NA address of the storage array Subsystem UserID string Account on the array NA Subsystem Password HorcmInst Secure string number Horcm instance number that is configured on the Windows web service host Dynamic Pools string A list of dynamic pools assigned to the profile by the storage admin RAID Group string A list of RAID groups assigned to this profile by the storage administrator NA NA NA Optional: If this field is blank, all dynamic pools in the system will be available to the profile. Optional: If this field is blank, all RAID groups in the system will be available to the profile. On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Installation and Configuration 43

44 Add HNAS Profile This workflow adds an HNAS profile object to Orchestrator s repository using the provided modular subsystem info. Library\Hitachi\Storage\Storage Subsystem Profile Name string Profile name This credential names has to be unique, which will be used later on. Controller1 IP Address Controller2 IP Address string string Controller 1 IP Address Controller 2 IP Address UserID string Account on HUS Password SecureString Subsystem password On Success: A message indicating success is returned. On Failure: An exception is thrown. Add Modular Array Profile This workflow adds a modular array profile to Orchestrator s repository, using the provided modular subsystem information. Library\Hitachi\Storage\Storage Subsystem Profile Name string Profile name The string must be unique. It will be used in future sessions. Controller1 IP string Controller 1 IP 44 Installation and Configuration

45 Address Controller2 IP Address string Address Controller 2 IP Address UserID string Account on HUS Password secure string Subsystem password Dynamic Pools string A list of dynamic pools assigned to the profile by the storage administrator RAID Group string A list of RAID groups assigned to this profile by the storage administrator. Optional. If this field is blank, all dynamic pools in the system will be available to the profile. Optional. If this field is blank, all RAID groups in the system will be available to the profile. On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Add V2I Server Profile This workflow adds a vcenter Profile object to the Orchestrator s repository using the provided vcenter information. Library\Hitachi\Storage\Storage Subsystem Profile Name string Profile name This credential names has to be unique which will be used later on. IP Address of the vcenter Server string IP Address of HNAS File Server Installation and Configuration 45

46 UserID string UserID to connect to the vcenter Server Password string Password of the vcenter Server Port Number Default is 443 if not specified On Success: A message indicating success is returned. On Failure: An exception is thrown. Delete Subsystem Profile Optional This workflow deletes the saved profile object in the Orchestrator s repository. Library\Hitachi\Storage\Storage Subsystem Profile Select Profile Name workflow object Profile object On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Block Storage Configuration Add Modular Array Add Modular Array is the first workflow that needs to be invoked. This workflow registers the provided subsystem with Orchestrator and returns a subsystem JavaScript object. This object s added as an inventory object in the Orchestrator client. Subsequent storage management operations can be performed using this object. 46 Installation and Configuration

47 Library\Hitachi\Storage\Block\Storage Configuration Controller1_IP_Addres s Controller2_IP_Addres s string string Controller 1 IP Address Controller 2 IP Address UserID string Account on HUS Password SecureStrin Password g On Success: a message confirms that the operation was successful. On Failure: an exception is thrown, and an error message indicates the possible cause of the problem. Add Enterprise Array This workflow registers an Enterprise array and returns a subsystem object for use with subsequent workflows. Library\Hitachi\Storage\Block\Storage Configuration SubsystemSerialNumb string Array serial number er SubsystemUserID string Array account SubsystemPassword Securestrin Array password g Subsystem string IP address:port associated with the array HorcmInst string CCI instance number On Success: a message confirms that the operation was successful. On Failure: an exception is thrown, and an error message indicates the possible cause of the problem. Installation and Configuration 47

48 Add Enterprise Subsystem using credential This workflow registers the provided subsystem with Orchestrator and returns a subsystem JavaScript object. This object is added as an inventory object in the Orchestrator client. Subsequent storage management operations can be performed using this object. Library\Hitachi\Storage\Block\Storage Configuration Credential workflow object Credential object On Success: The subsystem object is returned. On Failure: An exception is thrown. Add Modular Array using Credential This workflow registers the provided subsystem with Orchestrator and returns a subsystem JavaScript object. This object is added as an inventory object in the Orchestrator client. Subsequent storage management operations can be performed using this object. Library\Hitachi\Storage\Block\Storage Configuration Name workflow object Credential object On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Close all Storage Array Connections This workflow closes all the currently connected subsystems objects including vcenter and HNAS. This workflow does not require any parameters. 48 Installation and Configuration

49 Add Virtual Storage Array This workflow registers a virtual storage array and returns a subsystem object for use with subsequent workflows. Library\Hitachi\Storage\Block\Storage Configuration SubsystemSerialNumber string Virtual Storage Array serial number Prior to using this workflow, use Add Enterprise Array to register the physical array associated with the virtual array. If you use this workflow register a virtual storage array, and a physical array that has the same serial number is later registered, the physical array overrides the virtual array. Get Virtual Storage Arrays This workflow retrieves Hitachi virtual storage array objects. Library\Hitachi\Storage\Block\Storage Configuration Get Registered Storage Arrays This workflow retrieves information about registered arrays. Library\Hitachi\Storage\Block\Storage Configuration Block Provisioning Create LU in Parity Group This workflow creates an LU in a parity group. It applies to Enterprise family storage arrays. Installation and Configuration 49

50 Library\Hitachi\Storage\Block\Provisioning Subsystem HitachiStorag econnector:s ubsystem Hitachi storage array ParityGroup string Parity group within which to create the LU This can be a virtual storage subsystem object in which case, the LU is created on the virtual storage array Example: 2-4 Size string LU size (in GB) NA StripeSize HitachiStorag econnector:s TRIPE_SIZE LU stripe size Example: STRIPESIZE_64KB metaresourc eserial string Meta Resource serial number (applies to Virtual Storage Arrays) LdevName string The name to be assigned to the LDEV Applies to a virtual storage array. This parameter identifies the meta resource number on which the LU is created. If specified, the LU is created on the physical storage subsystem identified by the meta resource. If not specified, the connector throws an error for a virtual storage array Optional parameter On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Create LU in Dynamic Pool This workflow creates an LU in a DP pool. 50 Installation and Configuration

51 Library\Hitachi\Storage\Block\Provisioning Subsystem HitachiStora geconnector :Subsystem Hitachi storage array DynamicPool string DP pool number NA Size string LU size (in GB) NA StripeSize HitachiStora geconnector :STRIPE_SIZ E LU stripe size For example, STRIPESIZE_64KB MetaResourceSer ialnumber string Meta Resource serial number (applies to Virtual Storage Arrays) LdevName string The name to be assigned to the LDEV NA Applies to a virtual storage subsystem. This parameter identifies the meta resource number on which the LU is created. Optional parameter On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. Create LU in RAID Group This workflow creates an LU in a RAID group. It applies to modular family storage arrays. Library\Hitachi\Storage\Block\Provisioning Subsyste m RaidGrou p HitachiStorageConnect or:subsystem Hitachi storage array string RAID group The numerical representation of a Installation and Configuration 51

52 Delete LU Present LU size string LU Size (in GB) StripeSiz e HitachiStorageConnect or:stripe_size RAID group LU stripe size For example, STRIPESIZE_64KB On Success: A message confirms that the operation was successful. The newly created LU s LUN is returned. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. This workflow removes a Logical Unit. Library\Hitachi\Storage\Block\Provisioning Subsystem HitachiStorageCon nector:subsystem Hitachi storage array Lun string LU to delete Ensure that the LUN is supplied using decimal On Success: A message confirms that the LU has been deleted successfully. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. This workflow presents an LU by adding it to an existing host group. Library\Hitachi\Storage\Block\Provisioning Name Type Description Comment s 52 Installation and Configuration

53 Unpresent LU Get LUs Name Type Description Comment s Subsystem HitachiStorageConnector:Subs ystem Hitachi storage array Lun string LU Supply the LUN in decimal, not hex HostGroupNa string Host group me Port string Array target port On Success: A message confirms that the operation was successful. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. This workflow unpresents an LU by removing it from a host group. Library\Hitachi\Storage\Block\Provisioning Subsyste m HitachiStorageConnector :Subsystem Hitachi storage array Lun string LU Specify the LUN using decimal, not hex HostGrou string Host group pname Port string Array target port On Success: A success message appears, indicating that the LU has been unpresented. On Failure: An exception is thrown, and an error message indicates the possible cause of the problem. This workflow retrieves LU information. Installation and Configuration 53

54 When this workflow is used with Virtual Storage Arrays, LUs from all resource groups with the same array serial number are returned. A maximum of five hundred LUs can be returned by each invocation of this workflow. To allow all LUs on an array to be returned, this workflow supports the ability to specify a LUN range. For instance, LUNs in the range [ ] can be returned by specifying 1000 and 1300 for the BeginLun and EndLun parameters. Get Hostgroups Library\Hitachi\Storage\Block\Provisioning Subsystem HitachiStorageConnector:Subsystem Hitachi storage array BeginLun string LU range: lower limit (LUN >= value) EndLun string LU range: upper limit (LUN <= value) This workflow retrieves host group information from the specified subsystem. A host group is represented as a separated object in vcenter Orchestrator. Register the subsystem using the Add Modular Enterprise Array workflow before running this workflow. Provide a subsystem object input parameter in the workflow using the inventory definition in the Orchestrator client. Library\Hitachi\Storage\Block\Provisioning Subsystem Workflow object Subsystem object 54 Installation and Configuration

55 Get Hostgroups associated with an LU This workflow retrieves a host group with which an LU is associated from the specified subsystem. Register the subsystem using the Add Modular Enterprise Array workflow prior to running this workflow. Library\Hitachi\Storage\Block\Provisioning Subsystem Workflow object Subsystem LU number LU number Get Hostgroups associated with a WWN This workflow retrieves the host groups with which a WWN is associated from the specified subsystem. Register the subsystem using the Add Modular Enterprise Array workflow prior to running this workflow. This wokflow requires the subsystem object and a list of WWNs as an input parameter. Library\Hitachi\Storage\Block\Provisioning Subsystem Workflow object Subsystem object Target port string Subsystem s target port Get WWNs associated with a target port This workflow retrieves the WWNs associated with the specified target port from the specified subsystem. The subsystem needs to be registered using Add Modular Enterprise Array prior to running this workflow. This workflow requires the Subsystem object and a target port as an input parameter. Library\Hitachi\Storage\Block\Provisioning Subsystem Workflow object Subsystem object Target port string Subsystem s Installation and Configuration 55