Hitachi Storage Provider for VMware vCenter (VASA · PDF fileHitachi Storage Provider for...

Virtual Storage Platform G series, F series,and NAS Platform

Hitachi Storage Provider for VMwarevCenter (VASA Provider) for Block

StorageDeployment Guide

Release 3.3.2

MK-90ADPTR010-16

© 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronicor mechanical, including copying and recording, or stored in a database or retrieval system forcommercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any suchcopy is: (i) created as an essential step in utilization of the Software as licensed and is used in noother manner; or (ii) used for archival purposes. Licensee may not make any other copies of theMaterials. “Materials” mean text, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi Data Systems Corporation.

By using this software, you agree that you are responsible for:1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from

authorized employees and other individuals to access relevant data; and2. Verifying that data continues to be held, retrieved, deleted, or otherwise processed in

accordance with relevant laws.

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

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

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

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vistaare registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots arereprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website are propertiesof their respective owners.

2Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

https://support.hds.com/en_us/contact-us.html

Contents

Preface................................................................................................. 7Audience................................................................................................................. 8Product version........................................................................................................8Referenced documents.............................................................................................8Release notes.......................................................................................................... 8Document conventions............................................................................................. 9Conventions for storage capacity values...................................................................10Accessing product documentation........................................................................... 10Getting help...........................................................................................................11Comments.............................................................................................................11

1 Overview.............................................................................................13About the VASA Provider.........................................................................................14VASA Provider deployment architecture................................................................... 14Key terms and concepts..........................................................................................15Overview of VASA Provider Setup............................................................................ 15

2 System requirements........................................................................... 17Hardware requirements.......................................................................................... 18Software requirements........................................................................................... 18Supported protocol.................................................................................................19Restrictions and considerations............................................................................... 19

3 Installing the VASA Provider................................................................. 21Installation overview.............................................................................................. 22Obtaining the VASA Provider................................................................................... 22Installing vSphere Client Integration Plug-in.............................................................22Deploying the OVF................................................................................................. 24Installing the VASA Provider using the RHEL installer................................................ 26

Prerequisite software installation and setting...................................................... 26Upgrading the VASA Provider (v3.2.1 or earlier)....................................................... 28Upgrading the VASA Provider (v3.3.0 or later)..........................................................30


4 Verifying the installation....................................................................... 31Starting the VM......................................................................................................32Logging in to the Web UI........................................................................................32

5 Setting up the VASA Provider................................................................35Setting up the Hitachi Command Suite.....................................................................36Managing storage system....................................................................................... 37

Registering storage systems in the VASA Provider............................................... 37Viewing storage systems managed by the VASA Provider.....................................37Removing storage systems managed by the VASA Provider..................................38

Setting Multi-vCenter..............................................................................................38Setting up High Availability......................................................................................39

Setting up High Availability................................................................................ 39Monitoring a virtual machine and application...................................................... 39

Database Protection for VASA Provider.....................................................................40Virtual machine backup.....................................................................................40Setting up database resiliency........................................................................... 40

VASA Provider migration......................................................................................... 44Changing VASA Provider credentials........................................................................ 45Renewing an SSL authentication file........................................................................ 45

For using Web UI..............................................................................................45For using script.................................................................................................46

Restarting the VASA Provider service....................................................................... 46Managing Logs.......................................................................................................46

Downloading the VASA Provider log................................................................... 46Configuring log output settings.......................................................................... 47

Registering the Remote site.................................................................................... 48

6 Setting up the VVol environment...........................................................49Setting up the VAAI (VMware vStorage APIs for Array Integration)............................ 50Storage Policy Based Management.......................................................................... 51VASA Provider management for VMware vSphere..................................................... 51

Registering the VASA Provider in VMware vSphere.............................................. 52Removing the VASA Provider from VMware vSphere............................................ 53

Deploying a VVol datastore..................................................................................... 53

A Troubleshooting...................................................................................55Collecting log data..................................................................................................56Storage Provider is offline....................................................................................... 56VVol datastore is inactive........................................................................................ 57VM is inaccessible...................................................................................................57Additional troubleshooting information.....................................................................58

B Open source and third-party software licenses....................................... 59Apache Axis2......................................................................................................... 60Apache Tomcat...................................................................................................... 60Oracle Linux.......................................................................................................... 60PostgreSQL............................................................................................................62


Apache 2.0 license ................................................................................................ 63VMware vSphere Software Development Kit License................................................. 67



PrefaceThis manual provides information for Hitachi Storage Provider for VMwarevCenter Deployment Guide.

□ Audience

□ Product version

□ Referenced documents

□ Release notes

□ Document conventions

□ Conventions for storage capacity values

□ Accessing product documentation

□ Getting help

□ Comments

Preface 7Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

AudienceThis document is intended for:• vSphereTM system administrators• System engineers

Readers of this document should be familiar with the basic operation of thefollowing:• Virtual Storage Platform G1000 storage system• Hitachi Virtual Storage Platform G200, G400, G600, G800 VSP

G1500storage systems• VMware vCenter• VMware vSphere 5.1/5.5/6.0/6.5• VSP F400, F600, F800VSP F1500• Device Manager• Oracle Linux 7.2

Product versionThis document revision applies to 3.3.2.

Referenced documentsThe documents referenced are listed here:• Hitachi Virtual Storage Platform Provisioning Guide for Open Systems,

MK-90RD7022• Provisioning Guide for Open Systems, MK-92RD8014• Hitachi Command Suite User Guide, MK-90HC172

VMware documents

For details of VMware vSphere, see the documentation provided by VMwareat:

https://www.vmware.com/support/pubs/

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document. Release notes areavailable on Hitachi Data Systems Support Connect: https://knowledge.hds.com/Documents.

8 PrefaceHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide


https://knowledge.hds.com/Documents


Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold • Indicates text in a window, including window titles, menus, menu options,buttons, fields, and labels. Example:Click OK.

• Indicates emphasized words in list items.

Italic • Indicates a document title or emphasized words in text.• Indicates a variable, which is a placeholder for actual text provided by the

user or for output by the system. Example:

pairdisplay -g group

(For exceptions to this convention for variables, see the entry for anglebrackets.)

Monospace Indicates text that is displayed on screen or entered by the user. Example:pairdisplay -g oradb

< > angle brackets Indicates variables in the following scenarios:• Variables are not clearly separated from the surrounding text or from

other variables. Example:

Status-<report-name><file-version>.csv

• Variables in headings.

[ ] square brackets 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 youmust 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 or additional information.

Tip Provides helpful information, guidelines, or suggestions for performingtasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (forexample, disruptive operations, data loss, or a system crash).


Icon Label Description

WARNING Warns the user of a hazardous situation which, if not avoided, couldresult in death or serious injury.

Conventions for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) arecalculated based on the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (10 3) bytes

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical capacity values (for example, logical device capacity) are calculatedbased on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KB

Open-systems:• OPEN-V: 960 KB• Others: 720 KB

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://knowledge.hds.com/Documents. Check this site for themost current documentation, including important updates that may havebeen made after the release of the product.



Getting helpHitachi Data Systems Support Connect is the destination for technical supportof products and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contactinformation: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is the destination to get answers, discover insights, and makeconnections. Join the conversation today! Go to community.hds.com,register, and complete your profile.

CommentsPlease send us your comments on this document to [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!


https://knowledge.hds.com/

https://support.hds.com/en_us/contact-us.html

https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]


1Overview

This chapter provides an overview of the VASA Provider.

□ About the VASA Provider

□ VASA Provider deployment architecture

□ Key terms and concepts

□ Overview of VASA Provider Setup

Overview 13Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

About the VASA ProviderVASA Provider enables policy-based datastore operations.

In the policy-based datastore operation, you can create a datastore byselecting a Storage Container without any special knowledge of the storagesystem. You can create a virtual machine (VM) by setting policies (such ashigh IOPS and reliability) and can also verify whether the VM complies withthese policies.

As in previous releases, the usual event and alarm notifications provide thenecessary information for policy-based datastore operations.

VASA Provider deployment architectureThe following diagram depicts how the VASA Provider functions.

14 OverviewHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Key terms and conceptsThis topic describes key terms and VMware environment objects relevant tothe VASA Provider.

The term vSphere is a collective name for the VMware-based virtualenvironment, which includes the VMware vSphere software, VMware vCenterServer software, VMware ESXi clusters and hosts managed by the vCenterServer, and the virtual machines (VMs) and vApps hosted on those ESXiclusters.

The following table describes key terms and objects.

For details about these concepts, see the Hitachi Command Suite User Guideand the VMware documentation at https://www.vmware.com/support/pubs/.

Term Description

Block Abbreviation for Block Storage. This indicates storage systems other than HNAS.

DRS vSphere Distributed Resources Scheduler. DRS allows automatic movement of thevirtual machine during maintenance without the need for suspending service. Formore information, see https://www.vmware.com/products/vsphere/features-drs-dpm.

OVF Open Virtualization Format. This standard format enables the exchange of imagefiles of virtual machine image files across different virtualization software.

VASA Abbreviation for VMware vSphere Storage APIs for Storage Awareness. This functionindicates the overall storage management functions of vSphere. See VMwaredocuments at https://www.vmware.com/support/pubs/.

Overview of VASA Provider SetupSetting up the VASA Provider requires two operations:• Registering the storage system in the VASA Provider• Registering the VASA Provider in VMware vSphere

Additional operations described in this manual should be performed asneeded.

You can use the Web UI to configure VASA Provider settings as described inthe following table.

Operation Function Description

Management Add ConfiguredHardware

Lists managed storage systems or selects thestorage system to be managed by the VASAProvider after collecting the storage systeminformation from Hitachi Command Suite.

Overview 15Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide


https://www.vmware.com/products/vsphere/features-drs-dpm

https://www.vmware.com/products/vsphere/features-drs-dpm


Operation Function Description

View ConfiguredHardware

Lists the storage systems managed by theVASA Provider. You can also remove storagesystems from the VASA Provider with thisfunction.

Change Credentials Change the maintenance user accountpassword (default maintenance user accountand password are system and manager).

Update Software Update VASA Provider.

Maintenance Single Sign-On Setting Registers or updates vCenter Single Sign Oninformation.

Download Logs Downloads log files generated by the VASAProvider.

Troubleshooting Guide Displays the Troubleshooting Guide.

Update Certificate Update certification file for vCenter Server

Restart Service Restart VASA Provider.

For storage system, storage container, and protocol endpoint settings usingDevice Manager, see the Hitachi Command Suite User Guide.

For an overview of VVol configuration after VASA Provider is complete, see Setting up the VVol environment on page 49.

For the operations and specifications of VMware, see https://www.vmware.com/support/pubs/.

16 OverviewHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide



2System requirements

This chapter describes the requirements for configuring the VASA Provider.For the operations and specifications of VMware, see https://www.vmware.com/support/pubs/.

□ Hardware requirements

□ Software requirements

□ Supported protocol

□ Restrictions and considerations

System requirements 17Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide



Hardware requirementsThe following table lists the supported models and storage systemrequirements.

Component Requirement

Virtual Storage Platform G1000 80-03 or later

VSP G200, G400, G600, G800 83-02 or later

VSP F400, F600, F800 83-02 or later

VSP G1500 80-05 or later

VSP F1500 80-05 or later

Host bus adapter HBAs must support the "Secondary LUNID" feature to useVVols

Refer to the http://www.vmware.com/resources/compatibility/search.php?deviceCategory=io&details=1&pFeatures=206&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&bookmark=1 web page (highlight "Secondary LUNID (Enables VVols)"in the Features list).

VMware ESXi host to deploy VASAProvider

• CPU: vCPU (4)• Main memory: 8G• HDD capacity: 100 GB• Ethernet: 1 Gbps or more is recommended

Display for Web UI • Display resolution: 1600 x 900 or higher (recommended)• Color depth: 24 bit or higher (recommended)

Software requirementsThis topic lists software requirements for the VASA Provider. For moreinformation on VMware requirements, see https://www.vmware.com/support/pubs/.

Software Requirements

VMware VMware vCenter Server 6.0 / 6.0 update 1 / 6.0 update 2

VMware ESXi Server 6.0 / 6.0 update 1 / 6.0 update 2

VMware vCenter Server 6.5

VMware ESXi 6.5

Multipath software Native VMware NMP or Dynamic Link Manager (8.2.0-01 orlater)

Browser Microsoft Internet Explorer 10.0.19 and later

Mozilla Firefox 34 and later

18 System requirementsHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

http://www.vmware.com/resources/compatibility/search.php?deviceCategory=io&details=1&pFeatures=206&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc&bookmark=1







Software Requirements

Google Chrome 39 and later

VASA Provider - PostgreSQL 9.3

- Oracle Linux 7.2 (This is included in OVF file. Please contactsupport at Oracle for any question. You may have to purchasesupport service from Oracle. Not recommended to updateOracle Linux itself.)

- Red Hat Enterprise Linux 6.8 or 7.2 (If you are using RHELinstaller)

Supported protocolThe FC/iSCSI protocol is used to connect the ESXi Server and the storagesystem.

Restrictions and considerationsThe following restrictions apply when using the VASA Provider.

Provided service (operation)

VASA Provider only supports policy-based datastore operation.

Fastclone operations

VMware Horizon View and VMware vRealize Automation deployments usingLinked cloned operations (fastclone) are not supported in this release. Thesefunctions will return an error indicating it is unsupported.

LDEVs and SLU attribute

Creating and deleting LDEVs with the SLU attribute can only be managedusing VMware vCenter Server. Attempting such an operation without usingVMware vCenter Server can disrupt the storage system configuration.

Storage vMotion for VM of the snapshot configuration with branch

Storage vMotion for a VM of a snapshot configuration with branch mayappear to fail. However, the data of the virtual machine of the source are notaffected. When using Storage vMotion, execute the operation after creatingthe snapshot configuration with no branch.

System requirements 19Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

VM disk format

Only Thin Provision Disk format is supported. You can choose Thick ProvisionLazy Zeroed or Thick Provision Eager Zeroed, but data are stored on thestorage system in Thin Provision format.

Cancelling a Storage vMotion migration task

When a VM migration task with Storage vMotion has started, do not cancelthe task. Such a cancellation may fail depend on the timing. However, the VMremains on normal status even though the task failed and you can continueto use it.

Cancelling a VM snapshot

Once a snapshot process starts, do not attempt to cancel the task. Instead,delete the snapshot data after the task completes.

Cancelling a task during the revert processing of snapshot

If you cancel the task during revert processing of a snapshot for a VM, thetask fails but some revert processes may not complete. Retry the operationand make certain the task completes properly.

File upload to VVol Datastore

File upload to the VVol Datastore using VMware vSphere is not recommendedbecause it may fail.

Multiple VASA Providers

You can register multiple VASA Providers in the VMware vCenter server.However, registering the same storage system in multiple VASA Providers isnot supported.

Restarting the VASA Provider

Depending on the timing of a storage failure, you might not be able to accessthe datastore or VM created on the SC. Wait for a while after the failurerecovery and, if re-scanning the VASA Provider does not restore access,restart the VASA Provider.

After restarting the VASA Provider, it will take time to clear the VM accessfailure status.

20 System requirementsHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

3Installing the VASA Provider

This chapter describes how to install and perform the initial configuration ofthe VASA Provider.

□ Installation overview

□ Obtaining the VASA Provider

□ Installing vSphere Client Integration Plug-in

□ Deploying the OVF

□ Installing the VASA Provider using the RHEL installer

□ Upgrading the VASA Provider (v3.2.1 or earlier)

□ Upgrading the VASA Provider (v3.3.0 or later)

Installing the VASA Provider 21Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Installation overviewThe VASA Provider is distributed as an Open Virtualization Format (OVF) fileand is deployed on VMware vSphere as a packaged virtual machine (VM).(The VM includes not only the VASA Provider but all the dependencies.)

The procedure for deploying the VASA Provider is as follows.

Note: An Open Virtualization Appliance (OVA) .tar package includes the OVF.

1. Install the VASA Provider using the OVF deployment function of theVMware vSphere or RHEL installer.

2. From the VASA Provider web UI, change VASA Provider settings asneeded.

3. Register the VASA Provider in VMware vSphere.

OVF deployment target

Connect to the vCenter Server in which the ESXi Server that becomes thedeployment target of the VASA Provider is registered by vSphere Web Client.

Obtaining the VASA ProviderThe VASA Provider OVF can be obtained from the following sources:• The VASA Provider distribution media• Download from VMware• Download from HDS Support Portal• Your Hitachi account representative

Installing vSphere Client Integration Plug-inThe vSphere 6 software features the vSphere Web Client, a thin-clientversion of the software. Confirm that the VMware Client Integration Plug-insoftware is installed in the vSphere Web Client interface or install it beforeyou deploy the OVF.

The Client Integration Plug-in enables you to access a virtual machine'sconsole and connect virtual devices to virtual machines through the vSphereWeb Client. You only need to install the Client Integration Plug-in once.

Before you begin

Note: The following links are valid at time of publication. Should a link notrespond, go to https://www.vmware.com/support/pubs/ and navigate to

22 Installing the VASA ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide


Support Resources > Documentation > VMware vSphere 6 > vSphereInstallation and Setup Guide > Deploying the vCenter Server Appliance >Install the Client Integration Plug-In.

• Have the Client Integration Plug-in software requirements met. See http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-C17B5998-1B86-4E15-9E59-6DD969B07247.html for details.

• Have the Client Integration Plug-in software. The installer is located at http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe.

• Have administrator privileges.• Have the browser closed.

Important: If the machine is a shared administration system,confirm that other users of the system do not have a browser open.

Procedure

1. Right-click the downloaded Client Integration Plug-in software, and selectRun As administrator.

2. Test the installation of the Plug-in by launching a browser and logginginto the vSphere Web Client software.

The Launch Application dialog displays when the browser opens.

In the Launch Application dialog, perform the following steps:a. In the Choose an application field, select the path to the vmware-

csd.exe file.b. Select the checkbox for Remember my choices for vmware-csd

links.c. Click OK to confirm.


http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.install.doc/GUID-C17B5998-1B86-4E15-9E59-6DD969B07247.html



http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe

http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.exe

You can now proceed to deploying the OVF.

Deploying the OVFDeploying the OVF installs the Storage Provider software to the location youspecify. Use these steps to install the Storage Provider software.

Before you beginCheck the following:• OVF package is available.• vSphere 6 environment is installed and running.• Software and version requirements are met for vSphere Web Client. Using

the required versions can help avoid possible instability of the vSphereWeb Client running in the browser. See Software requirements on page 18for details.

• When deploying with the vSphere Web Client, have the vSphere ClientIntegration Plug-in installed and successfully tested.

• Have an VMFS/NFS datastore provisioned. This will be the datastore thatthe VM appliance installs on during deployment.

• Have the IP address of the ESXi host upon which you want to deploy theOVF.

Procedure

1. Locate the OVF package files to a storage location that is local to theclient system on which you want to launch the Web browser and log in tothe vCenter Server.

Note: Referencing the files from another location may be possible,but if the client is transferring the file over the network, then theinstall time can be severely impacted.

2. Launch a browser and log in to the vSphere Web Client interface.3. In the Navigator pane at the left side of the screen, perform the

following steps:a. Select vCenter Home > vCenter Inventory Lists.b. Select Virtual Machines.c. In the Virtual Machines pane at the right side of the screen, click the

Deploy OVF template icon ( ).4. In the Select source screen, browse to the location where the OVF is

located, then click Next.5. In the Review details screen, verify the OVF template details, then click

Next.6. In the Select name and folder screen, perform the following steps:

a. Enter a name for the appliance.


b. Select a datacenter location for the appliance.c. Click Next.

7. In the Select a resource screen, select the host or cluster on which todeploy the OVF, then click Next.

8. In the Select storage screen, perform the following steps:a. From the Select virtual disk format drop-down list, select applicable

disk format.b. From the VM Storage Policy drop-down list, select Datastore

Default.c. In the table of datastores, select the destination storage on which you

want the OVF to deploy.

Note: This datastore is typically the VMFS/NFS datastore youpreviously provisioned.

d. Click Next.9. In the Setup networks screen, from the Destination drop-down list,

select the network that you want the deployment to use, then click Next.10. In the two Customize template screens, perform the following steps:

Important: Complete all of the properties fields in both of theCustomize template screens or the deploy operation fails.

a. Enter a value for each deployment property.b. Click Next.c. Click the Systems Configuration drop-down icon, and arrow down to

see the remaining three fields.

Item Description

Network Configuration

IP Address IP address for the Storage Provider

DNS Server IP address for the DNS server

Gateway IP address for the default gateway

Netmask Netmask for the interface

SSO Server Configuration

FQDN or IP Address The FQDN or IP address for vCenter Single Sign-On Server

HTTPS Port The HTTPS Port Number for vCenter Single Sign-On Server

System Configuration

Domain Name Fully qualified domain name

Host Name or IP address Host name for this VM (displays after you register your StorageProvider). We recommend you use Hitachi VP for the HostName. If the host name has not been created in DNS, use theIP address. If you supply an invalid host name, vSphere does


Item Description

not assign an IP address. You will need to redeploy the OVF witha proper host name.

NTP NTP server name

11. In the Ready to Complete screen, confirm your settings, then clickFinish.

The vCenter software deploys the OVF template and installs the StorageProvider software.

Installing the VASA Provider using the RHEL installerWhen you install VASA Provider for Red Hat Enterprise Linux(RHEL), youmust use the RHEL installer.

This procedure describes the entire process of RHEL installation.1. Prepare RHEL, Configure network setting.2. Follow Prerequisite software installation and setting.3. Install VASA Provider.

Prerequisite software installation and settingThe software packages listed here must be installed and configured asdescribed before installing the VASA Provider.

For installation and setting

Item Description

Hitachi

Command Suite

8.5.0 or later

Follow Hitachi Command Suite Installation and Configuration Guide to install

HCS. Configure VVOL by following Hitachi Command Suite Administrator Guide.

OpenJDK 1.8 • Installation command example for yum command.# yum install java-1.8.0-openjdk-devel

• Run the following command to change the setting to prioritize the version ofthe installed JDK:alternatives --config javaalternatives --config javac

• Edit /etc/profile and add these lines to the bottom of the file:JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64export JAVA_HOME

• Use command# source /etc/profile to reflect environmental variable.

PostgresSQL 9.3 • Download the RPM installer for RHEL from the PostgreSQL website. For RHEL6: http://yum.postgresql.org/9.3/redhat/rhel-6-x86_64/repoview/postgresqldbserver93.group.htmlFor RHEL 7:http://yum.postgresql.org/9.3/redhat/rhel-7-x86_64/repoview/postgresqldbserver93.group.html

• The file is in RPM format. The file name will be similar to this example:


http://yum.postgresql.org/9.3/redhat/rhel-6-x86_64/repoview/postgresqldbserver93.group.html




Item Description

For RHEL 7:postgresql93-9.3.14-1PGDG.rhel7.x86_64.rpmpostgresql93-libs-9.3.14-1PGDG.rhel7.x86_64.rpmpostgresql93-server-9.3.14-1PGDG.rhel7.x86_64.rpmFor RHEL 6: Install these three PostgreSQL files.postgresql93-9.3.14-1PGDG.rhel6.x86_64.rpmpostgresql93-libs-9.3.14-1PGDG.rhel6.x86_64.rpmpostgresql93-server-9.3.14-1PGDG.rhel6.x86_64.rpmrpm command examples are following.# rpm -ivh postgresql93-libs-9.3.14-1PGDG.rhel7.x86_64.rpm# rpm -ivh postgresql93-9.3.14-1PGDG.rhel7.x86_64.rpm# rpm -ivh postgresql93-server-9.3.14-1PGDG.rhel7.x86_64.rpm

For Settings

Item Description

sudo VASA Provider uses sudo command at reinstallation. Use visudo command toedit /etc/sudoers to activate reinstallation function.• Adding a user

<Before the change>Defaults requiretty<After the change># Defaults requirettyDefaults:vptomcat !requiretty

• Setting authority<After noting>## Allow root to run any commands anywhereroot ALL=(ALL) ALLvptomcat ALL=(ALL) NOPASSWD: ALL

External communication setting

Item Description

Port number • Tomcat HTTP connection port: 50000 (TCP)• Tomcat HTTPS connection port: 50001 (TCP)• Tomcat Shutdown port: 50004 (TCP)• PostgreSQL connection port: 50003 (TCP)

Host name

resolutions

To enable the host name resolution, edit the /etc/hosts file as in this example:

127.0.0.1 <HostName>.<DomainName>

The VASA provider will not function properly if the IP address of the local host isnot set.

Installing the VASA Provider package

Procedure

1. Log into the VASA Provider server as root.


2. Copy the installer to the VASA Provider server and extract the files.3. Move to the extracted folder and start the installer using the command

line:

# ./StorageProviderforVMwarevCenter_Linux_install.sh4. Enter y or Y when the confirmation message is displayed.5. When the installation completion message appears, the procedure is

completed

6. Create a credential to use for the SSL communication.a. Open the SSL certificate setting file (/usr/local/hitachivp-b/

openssl.cnf) with a text editor such as vi, and then change the value0.0.0.0 to the IP address of the VASA Provider server.

b. At the command prompt, enter the following:

# cd /usr/local/hitachivp-b# ./createCertifications.sh

7. Restart the VASA Provider's VM machine.

Upgrading the VASA Provider (v3.2.1 or earlier)If you are running a previous version of the VASA Provider, please follow theupgraded procedure below.

Before you begin• The OVF or RHEL installer is available on the local system.• The prerequisite software files are available on the local system.• vSphere 6.0/6.5 is installed and running.

Procedure

1.Caution: Upgrade the HCS to 8.5 when you are upgrading theVASA Provider to v3.3.2

1. Remove the previous VASA Provider version from VMware vSphere.a. Log in to the vSphere Web Client.b. In the Navigator, click Home.c. Click vCenter Inventory Lists.d. On the Resources tab, click vCenter Servers.e. Select vCenter Server > Manage > Storage Providers.f. Select the previous version of the VASA Provider, then click the

removal icon (×).2. Remove the virtual machines managed by the previous version of the

VASA Provider from the inventory:a. Login to the vSphere Web Client.


b. In the Navigator, click Home.c. Click VMs and Templates.d. Select the virtual machine(s) managed by the previous version of the

VASA Provider.e. Right-click, then choose Remove from Inventory from the Action

menu.3. Unmount the datastores managed by the previous version of the VASA

Provider:a. Log in to the vSphere Web Client.b. In the Navigator, click Home.c. Log in Storage.d. Select the datastore(s) managed by the previous version of the VASA

Provider.e. Right-click, then choose Unmount Datastore from the Action menu.

4. Install the current version of the VASA Provider according to theprocedure described in Installing the VASA Provider on page 21.

5. Migrate the database from the Device Manager server used by theprevious version of the VASA Provider to the HDvM included in theHitachi Storage Provider v3.3.2.a. Export the data in the HDvM database used by the previous version of

the VASA Provider.b. Log in to the VASA Provider server. (user name: root; password:

password).c. Import the data into the HDvM database included with the current

version of the VASA Provider.

Note: The HDvM is included in the VASA Provider v03.3.0 andlater. See VASA Provider deployment architecture on page 14 and Setting up the Hitachi Command Suite on page 36. For detailsabout migrating data, see the Hitachi Command SuiteAdministrator Guide.

6. Register the storage system as described in Registering storage systemsin the VASA Provider on page 37.

7. Create a VVol datastore as described in Deploying a VVol datastore onpage 53. Be sure to select the same storage container used by theprevious version of the VASA Provider.

8. Register the virtual machine(s) managed by the previous version of theVASA Provider:a. Log in to the vSphere Web Client.b. In the navigator, click Home.c. Click Storage.d. Right-click to select Register VM.e. Select the .vmx configuration file for the Virtual Machine.f. Set Name and Location.g. Select Host/Cluster.


h. Click Finish.

Upgrading the VASA Provider (v3.3.0 or later)Use the Storage Provider Web UI to update the Storage Provider software orthe Web UI software as needed.

Before you begin

Caution: Upgrade the HCS to 8.5 when you are upgrading the VASA Providerto v3.3.2

This procedure only applies to VASA Provider v3.3.0 and later.

Note: Proceed only when there are no running tasks.

The software comes packaged in a zipped tar archive file. The file is named:

file_name_xxx.tar.gz

Where xxx is the version of the file. For example:

HitachiStorageProvider-3.3.2_update_patch.tar.gz

Procedure

1. Follow the procedure in Removing the VASA Provider from VMwarevSphere on page 53.

2. From the Web UI list of options, select Update Software.3. Click the appropriate Browse button to locate the software to update.4. Select the .tar.gz file, then use the following steps to upload and apply

it:a. Browse to the location where you want to upload the file.b. Transfer the file to the VASA provider.

Important: Do not close or refresh your browser during thedata transfer.

c. After the upload is complete, click Apply.5. Follow the procedure in Registering the VASA Provider in VMware

vSphere on page 52.


4Verifying the installation

This chapter describes the settings you should verify after installation.

□ Starting the VM

□ Logging in to the Web UI

Verifying the installation 31Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Starting the VMAfter successful OVF deployment, a new VM is automatically created basedon the configuration you provided during the deployment process.

Important: You must start the newly created VM before you can login.

Procedure

1. In the vSphere Web Client, start the newly created VM. For details onstarting a VM, see the VMware documentation at https://www.vmware.com/support/pubs/.

2. Follow the procedure below to verify that you can login to the VM andthat the VASA Provider is running.a. Login to the vSphere Web Client.b. Navigate to vCenter Inventory Lists > Virtual Machines.c. Select Open console to open a command window.d. Enter the following credentials:

• user name: root• password: password

Logging in to the Web UIAfter installing the VASA Provider, start the browser and enter the URL of theVASA Provider server to verify that you can log in. Use a PC that can beconnected to the VM where the VASA Provider is deployed.

Procedure

1. In a browser, enter the following URL:https://VASA-Provider-IP-Address:50001/

2. In the Web UI window, enter vCenter SSO Username and password(default setting issystem and manager) as the user ID and passwordand click Login.The VASA Provider information is displayed on the Web UI main window.

Item Description

Service Name Service name of the VASA Provider

Service PortNumber

Communication port number of VMware vSphere and the VASA provider

Database PortNumber

Communication port number of the VASA Provider and DBMS

32 Verifying the installationHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

https://www.vmware.com/support/pubs

https://www.vmware.com/support/pubs

Item Description

Service Version VASA Provider version

VASA Version VASA API version

Supported Model Model name of the storage system

Verifying the installation 33Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

34 Verifying the installationHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

5Setting up the VASA Provider

This chapter describes for procedures for setting up and maintaining theVASA Provider.

□ Setting up the Hitachi Command Suite

□ Managing storage system

□ Setting Multi-vCenter

□ Setting up High Availability

□ Database Protection for VASA Provider

□ VASA Provider migration

□ Changing VASA Provider credentials

□ Renewing an SSL authentication file

□ Restarting the VASA Provider service

□ Managing Logs

□ Registering the Remote site

Setting up the VASA Provider 35Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Setting up the Hitachi Command SuiteThe VASA Provider links to storage systems using Hitachi Command Suite(HCS); therefore HCS must be set up before using the VASA Provider. Thebasic settings needed to use VVols are described here.

Before you begin

Make certain that:• VASA Provider is installed• A storage system is available for use and the VVol setup is complete

Before you begin

For details, see the following documentation:• Hitachi Command Suite User Guide• Hitachi Command Suite Administrator Guide

Procedure

1. Access the HCS included in the VASA Provider.

URL:http://VASA-Provider-IP-Address:22015/DeviceManagerWebService/index.jsp

User ID: system

Password: manager2. Register the license in HCS.3. Create a user in HCS.4. Create a user group in HCS.5. Register the user that you created in the step 3 and resource groups to

the user group that you created in the step 4.6. Register the storage system in HCS.7. Create a storage container.

The HCS included with the VASA Provider is to be used only within theVVol environment.

Use the normal HCS or Storage Navigator to manage storage systemoutside of the VVol environment.

When registering storage systems in the HCS, separate them per HCSuser resource. (Multiple logins by the same user may cause VVol-relatedoperations to fail.)

36 Setting up the VASA ProviderHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Managing storage systemThis section describes how to register, view and remove storage systems.

Registering storage systems in the VASA ProviderYou must register storage systems in the VASA Provider to pass informationto VMware vSphere.

Procedure


2. Type vCenter SSO Username and password as the user ID andpassword and click Login.

3. In the Web UI main window, click Add Configuration Hardware.4. Enter the following information to discover the storage system from

Hitachi Command Suite:• Network IP address - Do not use loopback address (127.0.0.1)• HCS user name and password

5. Click Discover/Update HDvM Credentials.A list of storage systems is displayed. (Only storage systems supportedby the VASA Provider are shown.)

6. Select a storage system to be managed, and click Add.

Note: Whenever you change the user ID or password for HitachiCommand Suite, you must repeat this procedure.

Viewing storage systems managed by the VASA ProviderView the list of managed storage systems.

Procedure


2. In the Web UI Login window, enter vCenter SSO Username andpassword as the user ID and password and click Login.

3. In the Web UI main window, click View Configured Hardware.

The list of managed storage systems is displayed with the followinginformation:• Serial Number• Name


• Model• Microcode• Status• Capacity (Total, Used, and Free)

Note: If Microcode, Status, Total Capacity, Used Capacity, or FreeCapacity are displayed as "-" (hyphen), the connection to DeviceManager has failed. Check the connection and repeat theprocedure.

Removing storage systems managed by the VASA ProviderRemove storage systems managed by the VASA Provider.

Procedure

1. Enter the following URL in your browser:https://VASA-Provider-IP-Address:50001

2. In the Web UI Login window, enter vCenter SSO Username andpassword and click Login.

3. In the Web UI main window, click View Configured Hardware.4. Select the storage system to be removed, and then click Remove.

Confirm your choice when prompted.The list of the storage systems is updated accordingly.

Note: When you remove storage systems, you cannot operate anexisting VM created on the target storage. Make certain the VM nolonger exists before removing a storage system.

Setting Multi-vCenterFollow the procedure listed below to register the VASA Provider on multiplevCenter servers. If a VASA Provider is not registered on a vCenter server,then perform Steps 2-3 only. After registering a VASA Provider on a vCenterserver, perform all of the steps in the procedure to set the settings formultiple vCenter servers.

Procedure

1. Delete any VASA Provider registrations that are on the vCenter Server.2. Login to the VASA Provider server as the root user.3. Open the VasaProvider.properties file with vi or other text editor, then

set the value for multipleVcSupport to true. TheVasaProvider.properties file is located in the following


directory: /usr/local/hitachivp-b/tomcat/webapps/VasaProvider/META-INF

4. Run the createCertifications.sh script.5. Restart the VASA Provider by restarting the operating system or the VM.6. Register the VASA Provider with the vCenter Server.

Note: Whenever you change the value of a property, you mustrestart the VASA Provider.

Setting up High AvailabilityThis section describes how to set up High Availability and monitor a virtualmachine and application.

Setting up High AvailabilityThe VASA Provider can secure High Availability through the VMware vSphereHigh Availability (vSphere HA) or VMware vSphere Fault Tolerance (vSphereFT) functions. Since the VVol environment may become unavailable if anerror occurs with the VASA Provider, we recommend that you create a HighAvailability setup. For details on using VMware, see https://www.vmware.com/support/pubs/.

Note:• Unexpected errors occurring with the VASA Provider may prevent normal

recovery. Periodically backing up the VASA Provider environment (VM) toanother environment is recommended.

• The use of vSphere FT may cause a reduction in performance. See http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf.

Subsequently, if an error occurs, set the environment using the followingprocedure provided by VMware: http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html.• Lower the number of run operations in the VVol environment.• Change the VASA Provider ESXi host to a CPU or Disk with better

performance.

Monitoring a virtual machine and applicationThe VASA Provider enables monitoring of the application level under thevSphere HA configuration. By enabling the Monitoring of the virtual machineand application option of vSphere HA, the virtual machine will automaticallyrestart when the VASA Provider service stops.




http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf

http://www.vmware.com/files/pdf/techpaper/VMware-vSphere6-FT-arch-perf.pdf

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.avail.doc/GUID-63F459B7-8884-4818-8872-C9753B2E0215.html



Before you begin• VMware Tools have been applied to the virtual machine of the VASA

Provider.• The monitoring of vSphere HA, virtual machines has been configured.

For more information, see the VMware documents at https://www.vmware.com/support/pubs/.

Procedure

1. Log in to the VASA Provider server as root.2. Open the VasaProvider.properties file with a text editor such as vi,

and then set the value of thevasaprovider.highavailability.isEnabledApplicationMonitoringproperty to true.The VasaProvider.properties file is located in the following directory:

/usr/local/hitachivp-b/tomcat/webapps/VasaProvider/META-INF

Note: Whenever you change the value of a property, you mustrestart the VASA Provider.

Database Protection for VASA Provider

Virtual machine backupVASA Provider's database can be protected by backing up the entire virtualmachine.

Please see the following articles for virtual machine backup.• Hitachi V2I software for VM backup/recovery:

https://www.hds.com/en-us/products-solutions/application-solutions/virtual-infrastructure-integrator.htmlhttps://www.hds.com/en-us/pdf/datasheet/hitachi-datasheet-virtual-infrastructure-integrator.pdf

• UCP 2000 with V2I:https://www.hds.com/en-us/pdf/white-paper/protect-hitachi-unified-compute-platform-2000-for-vmware-vsphere-lab-validate-report.pdf

Setting up database resiliencyThe VASA Provider stores VVOL information in its database, and thisdatabase is periodically output as a backup file. Database resiliency isincreased by outputting this backup file from the virtual disk (OS disk) wherethe OS and VASA Provider are installed to a virtual disk (backup disk) in adatastore on a separate storage system. If a problem occurs on a storage




https://www.hds.com/en-us/products-solutions/application-solutions/virtual-infrastructure-integrator.html

https://www.hds.com/en-us/products-solutions/application-solutions/virtual-infrastructure-integrator.html

https://www.hds.com/en-us/pdf/datasheet/hitachi-datasheet-virtual-infrastructure-integrator.pdf

https://www.hds.com/en-us/pdf/datasheet/hitachi-datasheet-virtual-infrastructure-integrator.pdf

https://www.hds.com/en-us/pdf/white-paper/protect-hitachi-unified-compute-platform-2000-for-vmware-vsphere-lab-validate-report.pdf

https://www.hds.com/en-us/pdf/white-paper/protect-hitachi-unified-compute-platform-2000-for-vmware-vsphere-lab-validate-report.pdf

system where the VASA Provider is installed and you lose the database, youcan recover it from the backup file (database resiliency). If you lose theoriginal database, you will not be able to recover the existing VVOLenvironment; therefore configuring for database resiliency is recommended.

Follow the procedure listed below to configure database resiliency.

Procedure1. Prepare a datastore on a storage system that is separate from the

datastore on the virtual disk where the OS and VASA Provider areinstalled.

2. Relocate the backup destination to the new datastore.For OVA VASA Provider version: When deployed, the OS disk andbackup disk are stored in a single datastore. After deployment, relocatethe target storage by redirecting the backup destination to the newdatastore.

Note: The OVF VASA Provider may limit the backup disk volumewhen the numbers of VVOL VM is more than 1000. Adjust thebackup disk volume accordingly. For how to estimate the volume,see Hitachi Command Suite Administrator Guide. For adjusting VMmachine disk, see VMware manual or Oracle Linux.


For Installer version: After installing the VASA Provider and/or HCS,relocate the target storage by redirecting thebackup destination to the new datastore.

For vSphere Web Client operation: See VMware manuals.

For HCS operation: See Hitachi Command Suite AdministratorGuide.

For OS operation: See Red hat Enterprise Linux manuals.

Relocating the backup disk to a datastore on a separate storage system (OVFversion)

Before you begin• Prepare a datastore on a separate storage system for backup disk storage.• Deploy the VASA Provider.• Power off the VASA Provider virtual machine.

Procedure1. Login to the vSphere Web Client.2. Select VMs and Templates.3. Right-click on the VASA Provider VM, select Migrate.4. In the Migrate wizard, select Change Storage only, click Next.5. Click Advanced.6. Change Storage for Hard Disk 2 to the datastore on the separate

storage system where the backup file is to be stored. Click Next.7. Verify the settings, click Finish.8. After relocating the virtual machine, restart the VASA Provider.

Relocating the backup disk to a datastore on a separate storage system(Installer version)

Use the following procedure if you installed the VASA Provider using aninstaller.

Procedure1. Add a virtual backup disk to the VASA Provider VM.2. Specify the location of the datastore on the separate storage system that

you prepared for backup.3. Configure the format and mount for the added backup disk so that it can

be accessed from the OS.4. Save the settings for the backup directory and unload directory locations

to the added virtual disk according to the steps listed in theHitachiCommand Suite Administrator Guide for the vvoladaptersetup tool.

Restoring the backup file

Before you begin


• Verify you have the backup disk used in the existing VVOL environment.• Prepare a VASA Provider that is the same version as the VASA Provider

used when the problem occurred. The items listed below must be the sameas the original.○ OS (Installer version only)○ HCS version○ Time zone○ IP address and host name○ Time

• Power off the VASA Provider virtual machine.

Procedure1. Login to the vSphere Web Client.2. Select VMs and Templates.3. Right-click on the VASA Provider VM, select Edit Settings.4. Hover your pointer over Hard Disk 2. Select the X that appears to

delete the disk.5. Click OK, close the Edit Settings window.6. Select Edit Setting with right click on VASA Provider’s VM machine after

Reconfigure virtual machine task is completed.7. Select Existing Hard Disk from the New device list, click Add.8. In the Select File window, select the backup disk (VMDK file) for the

VASA Provider that had the problem, click OK.9. Click OK to close the Edit Settings window.

10. Restart the VASA Provider.11. Login to the VASA Provider as a root user.12. Stop the HCS service with the following command:

# /opt/HiCommand/Base64/bin/hcmds64srv -stop13. Restore the database with the following command:

# /opt/HiCommand/HiCommandServer/tools/databaserestore.sh -restoretime <YYYYMMDD_hhmmss>

Note: For example, enter 20160810_120000 for<YYYYMMDD_hhmmss>. If you want to restore the database to apoint prior to the time the problem occurred, set the time to themost recent backup time as shown by the directory name(<YYYYMMDDhhmmss>) at /opt/VVolDataBackup/Backup

14. Start the HCS service with the following command:# /opt/HiCommand/Base64/bin/hcmds64srv -start

15. Login to the HCS webpage.16. Update the information for the storage system.


VASA Provider migrationIf you restore or reconfigure the virtual machine (VM) on which the VASAProvider is, you must migrate the data containing the VVOL information.Follow the procedure described below to migrate the data.

Caution: Do not operate the VM during the VASA Provider data migration.The VM will be online, however, you will not be able to operate it.

Procedure

1. Remove the registration of the VASA Provider that is the source of thedata migration from VMware vSphere according to the steps listed in Removing the VASA Provider from VMware vSphere on page 53

2. As a root user, login to the virtual machine of the VASA Provider that isthe migration source.

3. Export the data with the following commands:

# mkdir /root/HCSwork# cd /opt/HiCommand/Base64/bin# ./hcmds64dbtrans -export -workpath /root/HCSwork -file /root/db_dump.zip -auto

4. Migrate the resulting data file (db_dump.zip) to the destination VASAProvider virtual machine using SCP or other tool.

5. As a root user, login to the destination VASA Provider6. Import the data with the following commands:

# mkdir /root/HCSwork# cd /opt/HiCommand/Base64/bin# ./hcmds64dbtrans -import -workpath /root/HCSwork -file /root/db_dump.zip -type ALL -auto

7. Open the two destination VASA Provider files listed below with a texteditor. Set the value for server.base.initialsynchro to True.• /opt/HiCommand/HiCommandServer/config/server.properties• /opt/HiCommand/TieredStorageManager/conf/server.properties

8. Start HCS with the following commands:

# cd /opt/HiCommand/Base64/bin# ./hcmds64srv -start

9. Reopen the two destination VASA Provider files listed below with a texteditor. Set the value for server.base.initialsynchro back to False.• /opt/HiCommand/HiCommandServer/config/server.properties• /opt/HiCommand/TieredStorageManager/conf/server.properties


10. Register the destination VASA Provider with the vCenter Server accordingto the steps listed in Registering the VASA Provider in VMware vSphere.

Changing VASA Provider credentialsBefore you begin

The maximum number of characters for credentials is 255. The supportedcharacters are:

A-Z a-z 0-9 ! # $ % & ' { } * + - . = @ ^ | ~ / ? `

You can change the user ID and password to be entered when you registerthe VASA Provider in VMware vSphere.

Procedure


2. In the Web UI Login window, enter vCenter SSO Username andpassword and click Login.

3. In the Web UI main window, click Change Credentials.4. Provide the following information:

• Current User Name and Password (currently logged in)• New User Name and Password• Confirm New Password

5. Click Change Credentials.

Renewing an SSL authentication fileSSL certificates have an expiration date. To extend an expiration date youmust recreate the certificate. There are two ways to reproduce theauthentication file. One is to use Web UI and the another is to use script.

For using Web UI

Procedure


2. Web UI login page will be displayed by entering information for this URL:https://VASA-Provider-IP-Address:50001

3. Enter User ID(or system) and password(or manager) for vCenter SSO,click Login.

4. Click Update Certificate in the Web UI main page.5. Select IP address for VASA Provider's WebUI, click Update.


6. Click OK in the verification display. VASA Provider will restart.7. Follow the Registering the VASA Provider in VMware vSphere on

page 52

For using script

Procedure


2. Log in to the VASA Provider server as root (User ID: root, Password:password).

3. At the root prompt, enter the following commands:cd/usr/local/hitachivp-b./createCertifications.sh

4. Restart the VASA Provider.5. Follow the procedure in Registering the VASA Provider in VMware

vSphere on page 52.

Restarting the VASA Provider serviceFollow the procedure listed below to restart the VASA Provider services. Afterconfiguring the settings, you may need to restart the VASA Provider service.

Procedure


2. In the Web UI window, enter vCenter SSO Username and passwordor system and manager, and click Login. 　 The VASA Providerinformation is displayed on the Web UI main window.

3. Select Restart Service from the Maintenance menu.4. Click Restart.5. Click OK to confirm. VASA Provider services will restart. You can access

the Web UI after it restarts.

Managing LogsThis chapter introduces how to download log files and configure log outputsettings.

Downloading the VASA Provider logDownload the log files created by the VASA Provider in compressed (ZIP)format.


https://VASA-Provider-IP-Address:50001/

https://VASA-Provider-IP-Address:50001/

File Description

CLP Common Landing Page log file

Others Tomcat log file

VP VASA Provider log file

WebUi WebUI log file

OVA OVA version file

Systems System log file

InstallerLog Installer log file

Procedure


2. In the Login window, enter vCenter SSO Username and password(default setting is system and manager) as the user ID and passwordand click Login.

3. In the Web UI main window. click Download Logs.4. Download the log files according to the instructions in your browser.

Configuring log output settingsYou can change the maximum number of file generations to be retained andthe rotation size for log files generated by the VASA Provider(StorageProvider.log) and the VASA Provider WebUI (VasaWebUi.log).

Before you begin• The VASA Provider has been installed.• The VM has been powered on.• Network settings have been configured.• SSL files have been created.

Procedure

1. Log into the VASA Provider server (default user name: system,password: manager.)

2. Start the root Terminal (default password: password)3. Edit the hilogger.config file as desired to change the following

parameters.

Item Description

MaxBackupIndex Indicates the generation number. Range: 1-255. Default value:20. (Any value outside the range is treated as the default.)


Item Description

MaxFileSize Indicates the log rotation size. Range: 1-100. Default value: 50MB. (Any value outside the range is treated as the default.)

The hilogger.config file is stored in the following locations:

For VASA Provider: /usr/local/hitachivp-b/tomcat/webapps/VasaProvider/WEB-INF/conf

For VASA Provider WebUI: /usr/local/hitachivp-b/tomcat/webapps/VasaProviderWebUi/WEB-INF/conf

For VASA Provider Common Landing Page: /usr/local/hitachivp-common/tomcat/webapps/CommonLandingPage/WEB-INF/conf

Refer to Downloading the VASA Provider log on page 46 for a descriptionof the log files.

4. Restart the VASA Provider for your changes to take effect.

Registering the Remote siteYou can consolidate landing pages as a remote site after registering filestorage from a block storage VASA Provider.

Procedure of registering a remote site is followed.

Procedure


2. In the Setup Web URL window, select the Setup tab.3. Enter the remote site IP address inNetwork IP Address.4. Enter the remote site Port Number5. Click Set.

Note: If you see an SSL certificate caution message and you areunable to access the VASA Provider's file storage through thelanding page, you must register the VASA Provider file storage URLas an exception in the web browser settings.


6Setting up the VVol environment

This chapter introduces additional configuration steps necessary to implementVVol in your environment. For full details on how to perform each task, seethese manuals:• Hitachi Command Suite User Guide (MK-90HC172)• Hitachi Command Suite Administrator Guide (MK-90HC175)

□ Setting up the VAAI (VMware vStorage APIs for Array Integration)

□ Storage Policy Based Management

□ VASA Provider management for VMware vSphere

□ Deploying a VVol datastore

Setting up the VVol environment 49Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

https://download.hds.com/download/epcra/hc17222.pdf

https://download.hds.com/download/epcra/hc17522.pdf

Setting up the VAAI (VMware vStorage APIs for ArrayIntegration)

Within the VVols environment, offload VMware ESXi host processing to thestorage system using VAAI (VMware vStorage APIs for Array Integration).Perform the following settings to enable VAAI.

Before you begin• Host with VMware ESXi 6.0/6.5 installed.• vSphere CLI is installed or SSH access to VMware ESXi is available.

Procedure

1. Log in to the VMware ESXi. Access to the ESXi host by following VMwareprocedure.• If using vSphere CLI: https://pubs.vmware.com/vsphere-60/topic/

com.vmware.vcli.examples.doc/cli_overviews.3.7.html• If using SSH ： http://pubs.vmware.com/vsphere-60/topic/

com.vmware.vcli.getstart.doc/cli_run_local.5.3.html2. Verify the VAAI_FILTER claimrule:

# esxcli storage core claimrule list --claimrule-class=Filter | grep HITACHI

Filter 65434 runtime vendor VAAI_FILTER vendor=HITACHI model=* false false 0

Filter 65434 file vendor VAAI_FILTER vendor=HITACHI model=* false false 0

3. Delete the VAAI_FILTER claimrule:

esxcli storage core claimrule remove --claimrule-class=Filter --rule=65434

4. Verify the VAAI claimrule:

# esxcli storage core claimrule list --claimrule-class=VAAI | grep Extra I

VAAI 65434 runtime vendor VMW_VAAIP_HDS vendor=HITACHI model=* false false 0

VAAI 65434 file vendor VMW_VAAIP_HDS vendor=HITACHI model=* false false 0

50 Setting up the VVol environmentHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

https://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.examples.doc/cli_overviews.3.7.html

https://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.examples.doc/cli_overviews.3.7.html

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.getstart.doc/cli_run_local.5.3.html

http://pubs.vmware.com/vsphere-60/topic/com.vmware.vcli.getstart.doc/cli_run_local.5.3.html

5. Delete the VAAI claimrule:

#esxcli storage core claimrule remove --claimrule-class=VAAI --rule=65434

6. Restart the VMware ESXi host.

Storage Policy Based ManagementOne of the prerequisites for configuring a VMware VVol environment involvesdefining the Storage Policy Based Management (SPBM). An SPBM is astructure that is based on a defined VM storage policy, where the VASAprovider and Hitachi Command Suite (HCS) automatically select the storageresources that meet the VM storage policy, and creates VVols.

After DP pools (or Thin Image pools) have been specified and grouped (or,file systems have been specified when working with VVols for file storage),they can be defined as a storage container, for which a capability profile canbe set. A capability profile defines the capabilities of a storage container (forexample, IOPS, Latency, Availability). Afterward, both the storage containerand associated capability profile can be disclosed to the VM administrator.

Note: After you change the configuration of a DP pool for block storage or afile system for file storage, check and if needed, change the capability profile.

The following steps outline the general task workflow for creating an SPBMstructure. The tasks that apply to the VMware vSphere administrator (VMadministrator) are noted in parenthesis:1. Define capability profiles. Set the capability profile in the storage

container for each DP pool for block storage and for each file system, forfile storage.

2. Define VM Storage Policies (applies to the VM administrator). Createvirtual machine storage policies based on the contents of the capabilityschema. The content that is defined in the capability schema can beviewed as the data service from vCenters.

3. Check storage policy compatibility (applies to the VM administrator).The vCenter reports whether storage containers exist that meet thepolicy criteria. This is done by comparing the capability profiles and VMstorage policies.

4. Create a VVol (applies to the VM administrator).

VASA Provider management for VMware vSphereThis section describes how to register and remove VASA Provider.


Registering the VASA Provider in VMware vSphereTo register the Storage Provider, you must manually add the Storage Providerto the vCenter Server by using the vSphere Web Client.

This registration makes the vCenter application aware of the Storage Providerand establishes communication between them.

Note: If you cannot register the VASA provider with the vCenter Server, thecertificate may have expired. Verify the expiration date of the vCenter Servercertificate.

Procedure

1. Log in to the vSphere Web Client, and perform the following steps:a. In the Navigator, select Storage.b. In the right pane, select the Manage tab, then Storage Providers.See the VMware documentation at https://www.vmware.com/support/pubs/ for more details.

2. Click the + icon to register a new storage provider.3. In the New Storage Provider dialog, enter values for the following

fields.4. Click OK. If the Security Alert window appears, click Yes.

Item Description

Name Any name (example: VASA Provider for block)

URL The URL of the VASA Provider:

https://VASA-Provider-IP-Address:50001/version.xmlUser name vCenter SSO Username

(example:vsphere.local\Administrator)Password vCenter SSO Password

Note: When the VASA provider is registered for the first time, thefollowing error is displayed by VMware vSphere: A problem wasencountered while registering the provider. Thecertificate is not trusted.

If the VASA provider registration completes and goes online, themessage can be ignored.

5. Confirm that the registration was successful by viewing the following:• The Storage Providers section in the vSphere Web Client displays the

newly added Storage Provider.• The Storage Provider indicates the storage array name with which it is

communicating.




Next steps

The system is now configured. Further confirm successful configuration byproceeding with creating a VVol datastore and provisioning a VM.

Removing the VASA Provider from VMware vSphereRemove the VASA Provider associated with the vCenter server.

Procedure

1. In the VASA Provider Registration window, select the VASA Provider andclick the x icon located in the middle of the window.

2. In the Removal Confirmation window, click Yes.

Deploying a VVol datastoreAfter you have successfully registered the Storage Provider, you can deploy aVVol datastore.

Before you begin

• Have the filesystem and a storage container already available on thestorage array.

• See the VMware documentation at https://www.vmware.com/support/pubs/ for more details about VVols.

Procedure

1. Log in to the vSphere Web Client and select Home in the Navigator.2. Under the Inventory List, select the datacenter where you want to deploy

the VVol datastore.3. In the action pane at the right side, click Actions, and then right-click

Storage > New Datastore.The New Datastore screen shows the Location with the datastore youselected.

4. In the Location screen, click Next.5. In the Type screen, select VVOL and then click Next.6. In the Name and container selection screen, select your datastore

from those listed in the Backing Storage section, and then click Next.7. In the Select hosts accessibility screen, select the check boxes to add

the hosts that you want to associate with your datastore, and then clickNext.

8. In the Ready to complete screen, review your settings, and then clickFinish.You are returned to the Home screen, where the new VVol datastorenow displays under your datacenter in the Inventory List.





ATroubleshooting

This appendix includes troubleshooting information for the VASA Provider(block and file).

□ Collecting log data

□ Storage Provider is offline

□ VVol datastore is inactive

□ VM is inaccessible

□ Additional troubleshooting information

Troubleshooting 55Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Collecting log dataBefore contacting support personnel, you should collect the log informationlisted here.

Component Document Topic

VASA Provider(block)

- Downloading the VASA Provider log onpage 46

HCSfor VASAProvider v3.3.1 andearlier

Hitachi Command SuiteAdministrator Guide

Acquiring maintenance information on themanagement server (hcmds64getlogscommand)

Log in to the VASA Provider Server as rootand execute the following command:

/opt/HiCommand/Base64/bin/hcmds64getlogs

Send all of the generated jar files listedbelow as attachments:• HiCommand_log_64.jar• HiCommand_log_64.hdb.jar• HiCommand_log_64.db.jar• HiCommand_log_64.csv.jar

vCenter/ESXi VMware Knowledge Base http://kb.vmware.com/kb/653

Storage SystemLogs

Hitachi Command Suite AuditLog Reference Guide

Downloading syslog files

Maintenance Manual (DKC810I) Collect Dump/Log

Storage Provider is offlineWhen the Storage Provider is offline, the connection with the StorageProvider may have failed.

Procedure

1. Rescan the Storage Provider to confirm whether the status hasrecovered.

2. Confirm whether the Storage Provider time setting matches the vCentertime.

3. Confirm whether the Storage Provider, the storage systems, and thestorage management software are suspended or an error has occurred.

4. Update the SSL certificate of the Storage Provider, and confirm whetherthe status has been recovered.

5. Confirm whether the storage systems have been registered in thestorage management software.

56 TroubleshootingHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

http://kb.vmware.com/kb/653

6. If the related hardware or the software does not have any problems,collect the log of the Storage Provider to confirm that the ERROR is notoutput.If the ERROR is displayed, take the countermeasure which iscorresponding to the ID.

7. If no problem is found, allow some time for the internal processes of thevCenter to complete, then confirm again

VVol datastore is inactiveWhen a VVol datastore is inactive, the datastore is not in a usable state.

Procedure

1. Confirm the Protocol Endpoint information from the summary of StorageContainer.When it is not displayed, a problem may have occurred in the connectionbetween ESXi and the storage system.

2. Rescan the Storage Device to confirm whether the status is recovered.3. Rescan the Storage Provider to confirm whether the status is recovered.4. Confirm whether the Storage Provider, the storage systems, and the

storage management software are suspended or an error has occurred.5. If the related hardware or the software does not have any problems,

collect the log of the Storage Provider to confirm that the ERROR is notoutput.

6. If ERROR is displayed, take the countermeasure that corresponds to theID.

7. If no problem is found, confirm again after waiting a while as the internalprocess of vCenter is running.

VM is inaccessibleWhen the VM is inaccessible, the VM is not usable.

Procedure

1. Rescan the Storage Device to confirm whether the status is recovered.2. Rescan the Storage Provider to confirm whether the status is recovered.3. Confirm whether the Storage Provider, the storage systems, and the

storage management software are suspended or an error occurred.4. Confirm whether the status recovers by restarting the VM for Storage

Provider.5. If the related hardware or the software does not have any problems,

collect the log of the Storage Provider to confirm that ERROR is notoutput.When there is an error, take the action that corresponds to the ID.

Troubleshooting 57Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

6. If no problem is found, confirm again after waiting a while as the internalprocess of vCenter is running.

Additional troubleshooting informationFor the block Storage Provider, click the Help link in the Web Setup UI todisplay troubleshooting scenarios and error codes.

58 TroubleshootingHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

BOpen source and third-party software

licensesThis appendix includes the copyrights and licenses for Open Source and third-party software used by the VASA Provider.

□ Apache Axis2

□ Apache Tomcat

□ Oracle Linux

□ PostgreSQL

□ Apache 2.0 license

□ VMware vSphere Software Development Kit License

Open source and third-party software licenses 59Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Apache Axis2This product includes software developed by The Apache Software Foundation(http://www.apache.org/).

Portions Copyright 2006 International Business Machines Corp.

Portions Copyright 2005-2007 WSO2, Inc.

This product also includes schemas and specification developed by:

- the W3C consortium (http://www.w3c.org)

This product also includes WS-* schemas developed by InternationalBusiness Machines Corporation, Microsoft Corporation, BEA Systems, TIBCOSoftware, SAP AG, Sonic Software, and VeriSign.

This product also includes a WSDL developed by salesforce.com

- Copyright 1999-2006 salesforce.com, inc.

Portions of the included xmlbeans library were originally based on thefollowing:

- software copyright (c) 2000-2003, BEA Systems, <http://www.bea.com/>.

Please read the different LICENSE files present in the lib directory of thisdistribution.

http://axis.apache.org/axis2/java/core/

Apache License, Version 2.0: Apache 2.0 license on page 63

Apache TomcatCopyright 1999-2014 The Apache Software Foundation

This product includes software developed at The Apache Software Foundation(http://www.apache.org/).

http://tomcat.apache.org/

Apache License, Version 2.0: Apache 2.0 license on page 63

Oracle LinuxORACLE LINUX LICENSE AGREEMENT

"We," "us," "our" and "Oracle" refers to Oracle America, Inc. "You" and "your" refers to the individualor entity that has acquired the Oracle Linux programs. "Oracle Linux programs" refers to the Linuxsoftware product which you have acquired. "License" refers to your right to use the Oracle Linuxprograms under the terms of this Oracle Linux License Agreement (the "Agreement") and the licensesreferenced herein. This Agreement shall be governed by and construed in accordance with Californialaw, except for that body of California law concerning the conflict of laws, and you and Oracle agree

60 Open source and third-party software licensesHitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

http://axis.apache.org/axis2/java/core/

http://tomcat.apache.org/

to submit to the exclusive jurisdiction of, and venue in, the courts of San Francisco or Santa Claracounties in California in any dispute arising out of or relating to this Agreement.

We are willing to provide a copy of the Oracle Linux programs to you only upon the condition that youaccept all of the terms contained in this Agreement. Read the terms carefully and indicate youracceptance by either selecting the "Accept" button at the bottom of the page to confirm youracceptance, if you are downloading the Oracle Linux programs, or continuing to install the OracleLinux programs, if you have received this Agreement during the installation process. If you are notwilling to be bound by these terms, select the "Do Not Accept" button or discontinue the installationprocess.

1. Grant of Licenses to the Oracle Linux programs. Subject to the terms of this Agreement, Oraclegrants to you a license to the Oracle Linux programs under the GNU General Public License version2.0. The Oracle Linux programs contain many components developed by Oracle and various thirdparties. The license for each component is located in the licensing documentation and/or in thecomponent's source code. In addition, a list of components may be delivered with the Oracle Linuxprograms and the Additional Oracle Linux programs (as defined below) or accessed online at http://oss.oracle.com/linux/legal/oracle-list.html. The source code for the Oracle Linux Programs and theAdditional Oracle Linux programs can be found and accessed online at https://oss.oracle.com/sources/. This Agreement does not limit, supersede or modify your rights under the license associatedwith any separately licensed individual component.

2. Licenses to Additional Oracle Linux programs. Certain third-party technology (collectively the"Additional Oracle Linux programs") may be included on the same medium or as part of the downloadof Oracle Linux programs you receive, but is not part of the Oracle Linux programs. Each AdditionalOracle Linux program is licensed solely under the terms of the Mozilla Public License, Apache License,Common Public License, GNU Lesser General Public License, Netscape Public License or similar licensethat is included with the relevant Additional Oracle Linux program.

3. Ownership. The Oracle Linux programs and their components and the Additional Oracle Linuxprograms are owned by Oracle or its licensors. Subject to the licenses granted and/or referencedherein, title to the Oracle Linux programs and their components and the Additional Oracle Linuxprograms remains with Oracle and/or its licensors.

4. Trademark License. You are permitted to distribute unmodified Oracle Linux programs orunmodified Additional Oracle Linux programs without removing the trademark(s) owned by Oracle orits affiliates that are included in the unmodified Oracle Linux programs or unmodified AdditionalOracle Linux programs (the "Oracle Linux Trademarks"). You may only distribute modified OracleLinux programs or modified Additional Oracle Linux programs if you remove relevant imagescontaining the Oracle Linux Trademarks. Certain files, identified in http://oss.oracle.com/linux/legal/oracle-list.html, include such trademarks. Do not delete these files, as deletion may corrupt theOracle Linux programs or Additional Oracle Linux programs. You are not granted any other rights tothe Oracle Linux Trademarks, and you acknowledge that you shall not gain any proprietary interest inthe Oracle Linux Trademarks. All goodwill arising out of use of the Oracle Linux Trademarks shall inureto the benefit of Oracle or its affiliates. You may not use any trademarks owned by Oracle or itsaffiliates (including "ORACLE") or potentially confusing variations (such as, "ORA") as a part of yourlogo(s), product name(s), service name(s), company name, or domain name(s) even if suchproducts, services or domains include, or are related to, the Oracle Linux programs or AdditionalOracle Linux programs.

5. Limited Warranty. THE ORACLE LINUX PROGRAMS AND ADDITIONAL ORACLE LINUX PROGRAMSARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. WE FURTHER DISCLAIM ALLWARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

6. Limitation of Liability. IN NO EVENT SHALL WE BE LIABLE FOR ANY INDIRECT, INCIDENTAL,SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE,DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION INCONTRACT OR TORT, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.OUR ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED ONE HUNDREDDOLLARS (U.S.).

7. No Technical Support. Our technical support organization will not provide technical support, phonesupport, or updates to you for the materials licensed under this Agreement. Technical support, ifavailable, may be acquired from Oracle or its affiliates under a separate agreement.

8. Relationship Between the Parties. The relationship between you and us is that of licensee/licensor.Neither party will represent that it has any authority to assume or create any obligation, express orimplied, on behalf of the other party, nor to represent the other party as agent, employee, franchisee,or in any other capacity. Nothing in this Agreement shall be construed to limit either party's right toindependently develop or distribute programs that are functionally similar to the other party"sproducts, so long as proprietary information of the other party is not included in such programs.

9. Entire Agreement. You agree that this Agreement is the complete Agreement for the Oracle Linuxprograms and the Additional Oracle Linux programs, and this Agreement supersedes all prior orcontemporaneous Agreements or representations. If any term of this Agreement is found to be invalid


http://oss.oracle.com/linux/legal/oracle-list.html


https://oss.oracle.com/sources/




or unenforceable, the remaining provisions will remain effective. Neither the Uniform ComputerInformation Transactions Act nor the United Nations Convention on the International Sale of Goodsapplies to this Agreement.

You can find a copy of the GNU General Public License version 2.0 in the "copying" or "license" fileincluded with the Oracle Linux programs or here: http://oss.oracle.com/licenses/GPL-2.

OFFER TO PROVIDE SOURCE CODE

For software that you receive from Oracle in binary form that is licensed under an open source licensethat gives you the right to receive the source code for that binary, you can obtain a copy of theapplicable source code from https://oss.oracle.com/sources/ or http://www.oracle.com/goto/opensourcecode. Alternatively, if the source code for the technology was not provided to you with thebinary, you can also receive a copy of the source code on physical media by submitting a writtenrequest to:

Oracle America, Inc.

Attn: Associate General Counsel

Development and Engineering Legal

500 Oracle Parkway, 10th Floor

Redwood Shores, CA 94065

Or, you may send an email to Oracle using the form linked from http://www.oracle.com/goto/opensourcecode. Your written or emailed request should include:

* The name of the component or binary file(s) for which you are requesting the source code

* The name and version number of the Oracle product

* The date you received the Oracle product

* Your name

* Your company name (if applicable)

* Your return mailing address and email

* A telephone number in the event we need to reach you.

We may charge you a fee to cover the cost of physical media and processing. Your request must besent (i) within three (3) years of the date you received the Oracle product that included thecomponent or binary file(s) that are the subject of your request, or (ii) in the case of code licensedunder the GPL v3, for as long as Oracle offers spare parts or customer support for that product modelor version.

Last updated 29 September 2015

PostgreSQLPortions Copyright (c) 1996-2013, PostgreSQL Global Development Group

Portions Copyright (c) 1994, The Regents of the University of California

http://www.postgresql.org/download/linux/debian/

PostgreSQL Database Management System

(formerly known as Postgres, then as Postgres95)

Portions Copyright (c) 1996-2013, PostgreSQL Global Development Group

Portions Copyright (c) 1994, The Regents of the University of California

Permission to use, copy, modify, and distribute this software and itsdocumentation for any purpose, without fee, and without a writtenagreement is hereby granted, provided that the above copyright notice andthis paragraph and the following two paragraphs appear in all copies.


http://oss.oracle.com/licenses/GPL-2


http://www.oracle.com/goto/opensourcecode




http://www.postgresql.org/download/linux/debian/

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANYPARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THISSOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OFCALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS,AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDEMAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

Apache 2.0 licensehttp://www.apache.org/licenses/LICENSE-2.0

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, anddistribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by thecopyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entitiesthat control, are controlled by, or are under common control with that entity.For the purposes of this definition, "control" means (i) the power, direct orindirect, to cause the direction or management of such entity, whether bycontract or otherwise, or (ii) ownership of fifty percent (50%) or more of theoutstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercisingpermissions granted by this License.

"Source" form shall mean the preferred form for making modifications,including but not limited to software source code, documentation source, andconfiguration files.

"Object" form shall mean any form resulting from mechanical transformationor translation of a Source form, including but not limited to compiled objectcode, generated documentation, and conversions to other media types.


http://www.apache.org/licenses/LICENSE-2.0

"Work" shall mean the work of authorship, whether in Source or Object form,made available under the License, as indicated by a copyright notice that isincluded in or attached to the work (an example is provided in the Appendixbelow).

"Derivative Works" shall mean any work, whether in Source or Object form,that is based on (or derived from) the Work and for which the editorialrevisions, annotations, elaborations, or other modifications represent, as awhole, an original work of authorship. For the purposes of this License,Derivative Works shall not include works that remain separable from, ormerely link (or bind by name) to the interfaces of, the Work and DerivativeWorks thereof.

"Contribution" shall mean any work of authorship, including the originalversion of the Work and any modifications or additions to that Work orDerivative Works thereof, that is intentionally submitted to Licensor forinclusion in the Work by the copyright owner or by an individual or LegalEntity authorized to submit on behalf of the copyright owner. For thepurposes of this definition, "submitted" means any form of electronic, verbal,or written communication sent to the Licensor or its representatives,including but not limited to communication on electronic mailing lists, sourcecode control systems, and issue tracking systems that are managed by, or onbehalf of, the Licensor for the purpose of discussing and improving the Work,but excluding communication that is conspicuously marked or otherwisedesignated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalfof whom a Contribution has been received by Licensor and subsequentlyincorporated within the Work.

2. Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable copyright license to reproduce, prepare Derivative Works of,publicly display, publicly perform, sublicense, and distribute the Work andsuch Derivative Works in Source or Object form.

3. Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free,irrevocable (except as stated in this section) patent license to make, havemade, use, offer to sell, sell, import, and otherwise transfer the Work, wheresuch license applies only to those patent claims licensable by suchContributor that are necessarily infringed by their Contribution(s) alone or bycombination of their Contribution(s) with the Work to which suchContribution(s) was submitted. If You institute patent litigation against anyentity (including a cross-claim or counterclaim in a lawsuit) alleging that theWork or a Contribution incorporated within the Work constitutes direct or


contributory patent infringement, then any patent licenses granted to Youunder this License for that Work shall terminate as of the date such litigationis filed.

4. Redistribution.

You may reproduce and distribute copies of the Work or Derivative Worksthereof in any medium, with or without modifications, and in Source orObject form, provided that You meet the following conditions:

1. You must give any other recipients of the Work or Derivative Works a copyof this License; and

2. You must cause any modified files to carry prominent notices stating thatYou changed the files; and

3. You must retain, in the Source form of any Derivative Works that Youdistribute, all copyright, patent, trademark, and attribution notices from theSource form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

4. If the Work includes a "NOTICE" text file as part of its distribution, thenany Derivative Works that You distribute must include a readable copy of theattribution notices contained within such NOTICE file, excluding those noticesthat do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of theDerivative Works; within the Source form or documentation, if provided alongwith the Derivative Works; or, within a display generated by the DerivativeWorks, if and wherever such third-party notices normally appear. Thecontents of the NOTICE file are for informational purposes only and do notmodify the License. You may add Your own attribution notices withinDerivative Works that You distribute, alongside or as an addendum to theNOTICE text from the Work, provided that such additional attribution noticescannot be construed as modifying the License. You may add Your owncopyright statement to Your modifications and may provide additional ordifferent license terms and conditions for use, reproduction, or distribution ofYour modifications, or for any such Derivative Works as a whole, providedYour use, reproduction, and distribution of the Work otherwise complies withthe conditions stated in this License.

5. Submission of Contributions.

Unless You explicitly state otherwise, any Contribution intentionally submittedfor inclusion in the Work by You to the Licensor shall be under the terms andconditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify theterms of any separate license agreement you may have executed withLicensor regarding such Contributions.

6. Trademarks.


This License does not grant permission to use the trade names, trademarks,service marks, or product names of the Licensor, except as required forreasonable and customary use in describing the origin of the Work andreproducing the content of the NOTICE file.

7. Disclaimer of Warranty.

Unless required by applicable law or agreed to in writing, Licensor providesthe Work (and each Contributor provides its Contributions) on an "AS IS"BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, eitherexpress or implied, including, without limitation, any warranties or conditionsof TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR APARTICULAR PURPOSE. You are solely responsible for determining theappropriateness of using or redistributing the Work and assume any risksassociated with Your exercise of permissions under this License.

8. Limitation of Liability.

In no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberateand grossly negligent acts) or agreed to in writing, shall any Contributor beliable to You for damages, including any direct, indirect, special, incidental, orconsequential damages of any character arising as a result of this License orout of the use or inability to use the Work (including but not limited todamages for loss of goodwill, work stoppage, computer failure ormalfunction, or any and all other commercial damages or losses), even ifsuch Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose tooffer, and charge a fee for, acceptance of support, warranty, indemnity, orother liability obligations and/or rights consistent with this License. However,in accepting such obligations, You may act only on Your own behalf and onYour sole responsibility, not on behalf of any other Contributor, and only ifYou agree to indemnify, defend, and hold each Contributor harmless for anyliability incurred by, or claims asserted against, such Contributor by reason ofyour accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplatenotice, with the fields enclosed by brackets "[]" replaced with your ownidentifying information. (Don't include the brackets!) The text should beenclosed in the appropriate comment syntax for the file format. We alsorecommend that a file or class name and description of purpose be includedon the same "printed page" as the copyright notice for easier identificationwithin third-party archives.


Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License"); you may notuse this file except in compliance with the License. You may obtain a copy ofthe License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributedunder the License is distributed on an "AS IS" BASIS, WITHOUTWARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. Seethe License for the specific language governing permissions and limitationsunder the License.

VMware vSphere Software Development Kit LicenseVMware vSphere Software Development Kit License Agreement

VMware, Inc. (“VMware”) provides the VMware vSphere SoftwareDevelopment Kit (collectively the “Software”) to you subject to thefollowing terms and conditions. By downloading, installing, or usingthe Software, you (the individual or legal entity) agree to be boundby the terms of this license agreement (the “Agreement”). If youdisagree with any of the following terms, then do not use theSoftware.

1. The Software contains a variety of materials, interface definitions,documentation, sample utility applications and sample code regardingprogramming interfaces to one or more VMware products that are referencedin such materials (the referenced products, “VMware Products”). ThisSoftware is intended to be used to develop software that interacts with theVMware Products.

2. Use Rights: Subject to the restrictions below, you may download andmake a reasonable number of copies of the Software for your use solely forthe purpose of creating software that communicates with VMware Products(your software, “Developer Software”). Some code may be designated as“distributable code” and/or “modifiable code” at http://www.vmware.com/go/vwssdk-redistribution-info. You may use and merge all or portions of the“distributable code” with your Developer Software. Any merged portion ofany “distributable code” is subject to this Agreement. Additionally, you maymodify or create derivative works of all or portions of the “modifiable code.”You are permitted to re-distribute the “distributable code” and the modifiedor derivative works of the “modifiable code” only as part of your DeveloperSoftware for non-commercial or commercial use; provided that you shall onlydistribute such code subject to a license agreement that protects VMware’sand its licensors’ interests consistent with the terms contained in thisAgreement. Open source software components provided with the Softwareare licensed to you under the terms of the applicable license agreements


http://www.vmware.com/go/vwssdk-redistribution-info

http://www.vmware.com/go/vwssdk-redistribution-info

included with such open source software components. The open sourcesoftware licenses can be found in the open_source_licenses.txt file, othermaterials accompanying the Software, the documentation or correspondingsource files available at http://www.vmware.com/download/open_source.html.

3. Restrictions: You agree that you will not (1) use the Software to create,design or develop anything other than Developer Software; (2) make anymore copies of the Software than are reasonably necessary for the authorizeduse and backup and archival purposes; (3) modify, create derivative worksof, reverse engineer, reverse compile, or disassemble the Software except asexpressly permitted in Section 2; (4) distribute, sell, lease, rent, lend, orsublicense any part of the Software to any third party except as expresslypermitted in Section 2; or (5) use the Software in any manner to (a)circumvent any technical restrictions of VMware Products or violate anyadditional licensing terms applicable to VMware Products that VMwareprovides through product documentation, email notification on the VMwarewebsite or in the terms of the End User License Agreements; (b) disable,remove, over-ride or modify the display of any VMware Product End UserLicense Agreements that the VMware Products present to the end customers;or (c) upload or otherwise transmit any material containing software virusesor other computer code, files or programs designed to interrupt, destroy, orlimit the functionality of any software or hardware.

The restrictions in this Section 3 shall not apply if and to the extent theycontradict mandatory local law (including, but not limited to, lawimplementing the EC Software Directive).

4. VMware retains ownership of the Software and all intellectual propertyrights embodied in the Software, including without limitation all copyrights,trade secrets and patents. You may not remove, delete or modify any ofVMware copyright statements in the Software. ALL RIGHTS NOT EXPRESSLYGRANTED HEREUNDER ARE RESERVED TO VMWARE.

5. You may not use VMware’s name, trademarks or service marks inconnection with your Developer Software in a way that suggests yourDeveloper Software is certified or endorsed by VMware.

6. You are not entitled under this Agreement to receive any VMware supportor subscription services for the Software or any other services from VMwarein connection with the Software. If you have purchased support and/orsubscription services for a VMware product, such support and/or subscriptionservices shall not apply to the Software or your use of the Software.

7. Term, Termination and Changes: This Agreement shall continue as longas you are in compliance with the terms specified herein or until otherwiseterminated. You or VMware each may terminate this Agreement for anyreason at any time. You agree, upon termination, to destroy all copies of theSoftware within your possession or control. The Confidential Information,


http://www.vmware.com/download/open_source.html

http://www.vmware.com/download/open_source.html

Limitations of Warranties and Liability, and Indemnification sections set out inthis Agreement shall survive any termination or expiration of this Agreement.

8. Confidential Information: “Confidential Information” means anyinformation disclosed by VMware to you pursuant to this Agreement that ismarked “Confidential,” “Proprietary,” or in some similar manner and anyinformation which you knew or reasonably should have known to beconfidential. You shall treat as confidential all Confidential Information ofVMware and shall not use such Confidential Information except to exerciseyour rights or perform your obligations under this Agreement. You will protectConfidential Information from unauthorized use, access, or disclosure in thesame manner as you protect your own confidential or proprietary informationof a similar nature but with no less than reasonable care. You shall notdisclose such Confidential Information to any third party during or after theterm of this Agreement. This paragraph will not apply to any ConfidentialInformation that: (a) was rightfully in your possession prior to receipt of suchConfidential Information from VMware; (b) is or becomes a matter of publicknowledge through no fault of you; (c) is rightfully received from a thirdparty without a duty of confidentiality; (d) is independently developed by youwithout breach of any confidentiality obligations; (e) is disclosed by you withVMware’s prior written approval; or (f) you are required to disclose byapplicable law or court order, provided that you notify VMware of suchrequired disclosure promptly in writing and cooperate with VMware in anylawful action to contest or limit the scope of such required disclosure. Youacknowledge that breach of this Section 8 will cause irreparable damage toVMware for which monetary damages will be an inadequate remedy.Accordingly, VMware will be entitled to seek and obtain injunctive and anyother relief (legal or equitable) to restrain any breach or anticipated breach ofthis Section 8.

9. Limitations of Warranties and Liability: THE SOFTWARE IS PROVIDED“AS IS” WITHOUT ANY WARRANTIES OF ANY KIND. TO THE MAXIMUMEXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ANY IMPLIEDWARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSEAND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENTWILL VMWARE BE LIABLE FOR ANY LOST PROFITS OR BUSINESSOPPORTUNITIES, LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF DATA,OR ANY OTHER INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES ARISING OUT OF THE SOFTWARE OR YOUR USE OF THESOFTWARE, UNDER ANY THEORY OF LIABILITY, WHETHER BASED INCONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE.BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION ORLIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES,THE PRECEDING LIMITATION MAY NOT APPLY TO YOU.


VMWARE’S LIABILITY ARISING OUT OF THIS AGREEMENT AND THESOFTWARE PROVIDED HEREUNDER WILL NOT, IN ANY EVENT, EXCEED US$100.00.

THE FOREGOING LIMITATIONS SHALL APPLY TO THE MAXIMUM EXTENTPERMITTED BY APPLICABLE LAW, REGARDLESS OF WHETHER VMWARE HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND REGARDLESSOF WHETHER ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE.

10. Indemnification: You agree to defend, indemnify and hold harmlessVMware, and any of its directors, officers, employees, affiliates and agents,from and against any and all claims, losses, damages, liabilities and otherexpenses (including reasonable attorneys’ fees), arising from yourmodification of the “modifiable code,” the distribution or use of yourDeveloper Software by you or anyone else, and your breach of thisAgreement.

11. Export Control: You acknowledge that the Software is of United Statesorigin, is provided subject to the U.S. Export Administration Regulations, maybe subject to the export control laws of the applicable territory, and thatdiversion contrary to applicable export control laws is prohibited. Yourepresent, warrant and covenant that (1) you are not, and are not acting onbehalf of, (a) any person who is a citizen, national, or resident of, or who iscontrolled by the government of any country to which the United States hasprohibited export transactions; or (b) any person or entity listed on the U.S.Treasury Department list of Specially Designated Nationals and BlockedPersons, or the U.S. Commerce Department Denied Persons List or EntityList; and (2) you will not permit the Software to be used for any purposesprohibited by law, including, any prohibited development, design,manufacture or production of missiles or nuclear, chemical or biologicalweapons.

12. Data Privacy:

(a) Consent for Collection and Use of Technical Data. You agree that VMwaremay periodically collect, process and store technical and related informationabout your device, system, application, peripherals and your use of theSoftware, including without limitation: internet protocol address, hardwareidentification, operating system, application software, peripheral hardware,number of active plugins and software development kits, the successfulinstallation and launch of Software, and Software usage statistics(collectively, “Technical Data”). VMware will use Technical Data for internalstatistical and analytical purposes to facilitate support, invoicing or onlineservices, the provisioning of updates, and the development of VMwareproducts and services. VMware may transfer Technical Data to othercompanies in the VMware worldwide group of companies from time to time.

(b) Log Files. You acknowledge that correspondence and log files generatedin conjunction with a request for support services may contain sensitive,confidential or personal information. You are solely responsible for taking the


steps necessary to protect such data, including obfuscating the logs orotherwise guarding such information prior to sending it to VMware.

13. These terms are governed by the laws of the State of California and theUnited States of America without regard to conflict of laws principles. TheUnited Nations Convention for the International Sale of Goods shall not apply.You may not assign this Agreement. Any attempted assignment by you shallbe void. These terms constitute the entire agreement between you andVMware with respect to the Software and supersede all prior written or oralcommunications, understandings and agreements. Any waiver of these termsmust be in writing and signed by the waiving party to be effective. If anyprovision of these terms is found to be invalid or unenforceable, theremaining terms will continue to be valid and enforceable to the fullest extentpermitted by law.



Hitachi Storage Provider for VMware vCenter (VASA Provider) for Block Storage Deployment Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0) 1753 [email protected]

Asia Pacific+852 3189 [email protected]

Contact Uswww.hds.com/en-us/contact.html

MK-90ADPTR010-16

http://www.hds.com

MAILTO:[email protected]



Date post:	26-Mar-2018
Category:	Documents
Upload:	phungkien
View:	266 times
Download:	8 times