VMware vSphere 6.

5 Virtual Volume Environment

Deployment in Hitachi Virtual Storage Platform

Implementation Guide

By Tsuyoshi Inoue

July 2017
Feedback
Hitachi Data Systems welcomes your feedback. Please share your thoughts by sending an email message to
SolutionLab@hds.com. To assist the routing of this message, use the paper number in the subject and the title of this
white paper in the text.

Revision History

Revision Changes Date

AS-608-00 Initial release July 19, 2017
Table of Contents
VMware vSphere Virtual Volume Overview.............................................................................................................. 2
Tested Solution Components ..................................................................................................................................... 4
Solution Implementation ........................................................................................................................................... 10
Required Software Components .................................................................................................................................. 10
Prerequisites for Installation ......................................................................................................................................... 11
Deploy the Open Virtualization Format (OVF) File for Hitachi Storage Provider for VMware vCenter .......................... 12
Configure the Storage System Settings Using Hitachi Command Suite for the VMware Virtual Volumes
Environment .................................................................................................................................................................. 13
Set the Storage System Using Hitachi Storage Provider for VMware vCenter for the VMware Virtual Volumes
Environment Configuration ........................................................................................................................................... 24
Edit a PE (ALU) and a Storage Container ..................................................................................................................... 26
Edit a PE (ALU) LUN Path ............................................................................................................................................. 30
Delete a PE (ALU) or a Storage Container .................................................................................................................... 31
Create a Virtual Machine............................................................................................................................................... 37
Uninstall the VMware Virtual Volumes Environment ..................................................................................................... 46
Terms and Abbreviations............................................................................................................................................ 51
Reference Documents ................................................................................................................................................ 52
1

VMware vSphere 6.5 Virtual Volume Environment

Deployment in Hitachi Virtual Storage Platform
Implementation Guide

Use this implementation guide to deploy VMware vSphere Virtual Volumes with these Hitachi Virtual Storage Platform
(VSP) models in software defined storage:

 VSP Gx00

 VSP G1000

 VSP G1500

 VSP F1500

 VSP Fx00

This guide shows how to use with the following software for your VMware storage solutions:

 VMware vSphere APIs for Storage Awareness (VASA)

 Hitachi Storage Provider for VMware vCenter

 Hitachi Command Suite (HCS) as an index for each component document.

For details on each procedure, refer to these product guides:

 Hitachi Storage Provider for VMware vCenter Deployment Guide

 Hitachi Command Suite User Guide

 Hitachi Command Suite Installation and Configuration Guide

 Hitachi Command Suite Administrator Guide

 Provisioning Guide for Open Systems

 Hitachi Virtual Storage Platform G1000 and VSP G1500

 Hitachi Virtual Storage Platform F1500
 Provisioning Guide

 Hitachi Virtual Storage Platform G200, VSP G400, VSP G600, VSP G800
 Hitachi Virtual Storage Platform F400, VSP F600, VSP F800
 Hitachi Thin Image User Guide

 Hitachi Virtual Storage Platform G1000 and VSP G1500

 Hitachi Virtual Storage Platform F1500
 Hitachi Virtual Storage Platform G200, VSP G400, VSP G600, VSP G800
 Hitachi Virtual Storage Platform F400, VSP F600, VSP F800

1
2

This implementation guide is intended to be used by IT administrators charged with the storage deployment, or
administration of VMware vSphere infrastructures on Hitachi Virtual Storage Platform. It assumes familiarity with storage
area network (SAN)-based storage systems, VMware vSphere, Hitachi data replication technologies, and common IT
storage practices.

The screen shots in this guide to integrate VMware VASA with Hitachi storage were acquired using Virtual Storage
Platform G1500 and Virtual Storage Platform G600 (for iSCSI).

Note — These procedures were developed in a lab environment. Many things affect production environments beyond
prediction or duplication in a lab environment. Follow recommended practice by conducting proof-of-concept testing
for acceptable results before implementing this solution in your production environment. Test the implementation in a
non-production, isolated test environment that otherwise matches your production environment.

VMware vSphere Virtual Volume Overview

VMware vSphere Virtual Volume is based on an integration and management framework between VMware vSphere and
the storage system, as introduced by vSphere 6.0.

There is incompatibility between VMware vSphere and the virtual machine management for the storage array between
both primary units. An example incompatibility are the virtual disks (VMDK files) for the virtual machines and LUNs for the
storage array.

Solving this incompatibility can require sacrificing service level agreements for virtual machines. For example, virtual
machines that reside on the same data store (LUN) are forced to use the same RPO leveraging storage replication, in spite
of different recovery point objectives required for each virtual machine.

With VMware Virtual Volumes, the virtual disk becomes the primary unit of data management at the storage system level.

It is possible to do the following:

 Execute storage operations with granularity

 Provision native storage systems-based data services to individual virtual machines (VMs)

Figure 1

2
3

Regarding the management framework, VMware introduced a new policy-driven framework called storage policy based
management (SPBM) that interacts with the storage array. The SPBM framework allows for the following in the form of
logical templates (VM storage policies):

 Advertising of storage capabilities

 Capture of storage service-level requirements (capacity, performance, availability, and so forth).

SPBM automates virtual machine placement by identifying an available virtual volume (VVol) datastore that matches the
specified policy requirements. When coupled with VMware Virtual Volumes, SPBM can dynamically instantiate the
necessary data services when required. Policy-driven management allows for automated provisioning of virtual machines
and quicker adjustment to business changes.

Figure 2

With VMware Virtual Volumes and virtual volume implementation by Hitachi, virtual machine operations, such as VM
power on or off, VMware snapshot, virtual machine clone, and migration, are integrated with storage arrays using the
following:

 VMware vCenter

 A Hitachi out-of-band operation that includes Hitachi Storage Provider for VMware vCenter and Hitachi Virtual
Storage Platform

3
4

For example, virtual machine clone and VMware snapshot are offloaded to storage arrays using VMware vCenter,
leveraging either Hitachi ShadowImage Heterogeneous Replication or Hitachi Thin Image (HTI),. This allows effective
physical resource use in the virtual infrastructure within the data center.

Figure 3

Tested Solution Components

Hitachi Storage Provider for VMware vCenter and VMware Virtual Volumes with Hitachi Command Suite (HCS) was
distributed as a single open virtualization format (OVA) file. It was deployed on VMware vSphere as a single packaged
virtual machine (VM).

From version 3.4, VMware Virtual Volumes fully integrates with the Hitachi Command Suite user interface into the Storage
Provider for VMware vCenter web user interface. This improves manageability and usability by using a single pane of
glass.

Virtual volume implementation by Hitachi has an option to create and manage the storage objects by using Hitachi
Command Suite or Hitachi Storage Navigator, depending on your environment.

These enhancements provide you with faster deployment, ease of use, and operational flexibility.

This document describes using Hitachi Command Suite for creation and management of storage objects. Regarding other
options such as multiple components with multiple vCenter instances and combinations, please refer to Hitachi
Command Suite documentation.

4
5

Figure 4 shows the system configuration for a virtual volume (VVol) environment deployment on Hitachi Virtual Storage
Platform G1000, VSP G1500, or VSP F1500.

Figure 4

Figure 5 on page 6 shows the system configuration for a VVol environment deployment using these Hitachi Virtual Storage
Platform models:

 VSP G200

 VSP G400

 VSP G600

 VSP G800

 VSP F400

 VSP F600

 VSP F800

5
6
Figure 5
Table 1 shows the role of each system component for VMware Virtual Volume delivery.
TABLE 1. SYSTEM COMPONENT ROLES
Item
VMware vSphere Web Client
VMware vCenter Server
Hitachi Storage Provider for
VMware vCenter web user
interface.
Hitachi Storage Provider for
VMware vCenter
Hitachi Command Suite Web
Client
Hitachi Command Suite
Role
The virtual machine administrator uses this console to manage the virtual
environment.
Application to execute the integrated management of the VMware
vSphere environment. In addition, it executes the operation of VVol for VM
via VASA.
The storage administrator uses this console to manage Storage Provider
for VMware vCenter.
This retrieves and relays the Hitachi storage system information
requested by the VASA API from VMware vCenter Server and VMware
ESXi hosts. It also manages following VMware Virtual Volume objects.
 Storage container
 Storage policy based management (SPBM)
 VVol metadata
The storage administrator uses this console to manage the storage
environment
In the VMware Virtual Volume environment, Hitachi Command Suite
carries out storage settings at the time of the construction or disposal of
the Virtual Volume environment.
6
7

TABLE 1. SYSTEM COMPONENT ROLES (CONTINUED)

Item Role
Hitachi Virtual Storage Managing and providing PE (ALU).
Platform:
Managing and providing SLU (VMware Virtual Volume).
 VSP G1000
Storing SLU (VMware Virtual Volume) metadata.
 VSP G1500

 VSP F1500

 VSP G200

 VSP G400

 VSP G600

 VSP G800

 VSP F400

 VSP F600

 VSP F800
SVP The SVP is a management server that attaches to VSP Gx00 and VSP
Fx00 systems using Hitachi Command Suite or Hitachi Storage Navigator.

Configuration of Hitachi Storage Provider for VMware vCenter comprises the out-of-band interaction with VMware
vCenter that is the key design element for considering the number of virtual machines and the number of concurrent job
executions in the VMware Virtual Volume environment.

Do the following when deploying Storage Provider for VMware vCenter:

 Deploy Storage Provider for VMware vCenter in a management cluster as a VM

 Deploy Storage Provider for VMware vCenter on the host using high-performance CPU and memory

 Deploy Storage Provider for VMware vCenter on non-VVol datastores (VMFS/NFS) using high speed devices such as
SSDs or external storage

The system configuration described in Table 2, “VMware Virtual Volume Configuration,” on page 8 is based on the result
of tests using the VMware Virtual Volume certification kit. Management servers in which the Hitachi Storage Provider for
VMware vCenter virtual machine resides are verified as follows for each virtual machine operation:

 Power on with 200 virtual machines simultaneously

 Power off, create, or delete VMware snapshot and creation or deletion of virtual machine clone operations could be
executed simultaneously with 32 virtual machines respectively.

When a timeout occurs during operation of VMware Virtual Volumes, check the environment’s configuration, referring to
Table 2.

7
8

TABLE 2. VMWARE VIRTUAL VOLUME CONFIGURATION

Major Component Item Specifications

Server CPU Intel Xeon E5-2660 v3 processor @ 2.60 GHz

 The number of CPUs: 2

 The number of cores for each CPU: 10

 Hyperthreading: Valid

 The number of the logic processors: 40 (2 × 10 × 2)

Main Memory 128 GB
Network 1 Gb/s Ethernet
HBA Emulex LPe12000 8 Gb/s Fibre Channel Host Adapter (Inbox driver)
Virtual Appliance for The number of 4 cores
Hitachi Storage Provider logic cores
for VMware vCenter Memory 8 GB

Note — This system configuration does not guarantee the number of virtual machines that you can operate
simultaneously. If the operation fails, reduce the number of virtual machines that are executing a process
simultaneously.

Ensuring high availability for the following are key in the out-of-band design of a block environment for VMware Virtual
Volumes form an operational standpoint:

 Hitachi Storage Provider for VMware vCenter

 The SVP required for Hitachi Virtual Storage Platform Gx00 and VSP Fx00 .

 When one of these components is unavailable, only storage management operations related to VVol object metadata
manipulation will be impacted

 Clone

 Snapshot

 Power on

 Power off

8
9

The out-of-band communication on this Hitachi block implementation of Virtual Volumes in a down situation does not
affect virtual machine I/O, as the I/O flows through the data path (PEs).

 For Hitachi Storage Provider for VMware vCenter that is packed in an open virtual appliance (OVA) and deployed as a
single virtual machine, the following are supported from Storage Provider for VMware vCenter version 3.3 or later:

 VMware vSphere Fault Tolerance

 VMware vSphere High Availability
The recommendation is to enable vSphere Fault Tolerance or vSphere High Availability with Storage Provider for
VMware vCenter deployed as a single virtual machine for continuous Virtual Volume operations.

 Deploying the external SVP required for Hitachi Virtual Storage Platform Gx00 and VSP Fx00 in a management
cluster as a virtual machine is supported starting with storage micro code version 83-03-23/00. Also, enabling
VMware vSphere Fault Tolerance with the external SVP virtual machine is supported and recommended for
continuous Virtual Volume operations. Enabling VMware vSphere High Availability with the external SVP will be
supported in a later release.

If an error occurs, set the environment, as follows:

 Lower the number of run operations in the Virtual Volumes environment.

 Change the host to a CPU or disk with better performance.

Note — VMware Fault Tolerance provides zero-downtime, zero-data-loss continuous availability for any application
without the cost or complexity of traditional solutions. On the other hand, one of the most common performance
observations of virtual machines under Fault Tolerance protection is a variable increase in the network latency of the
virtual machine. Some applications that are highly sensitive to network latency have a higher performance cost under
Fault Tolerance protection. Take into account both the benefits and costs when you adopt either VMware vSphere
Fault Tolerance or VMware vSphere High Availability for Hitachi Storage Provider for VMware vCenter and SVP. Refer
to the related VMware document.

9
10

Solution Implementation
This describes how to deploy VMware vSphere Virtual Volumes with Hitachi Storage Provider for VMware vCenter.

Required Software Components

Table 3 shows the software requirements required to implement a VMware Virtual Volumes environment.

TABLE 3. SOFTWARE PREREQUISITES

Component Purpose or Where Used Remarks

VMware software VMware vSphere Web Client Use the version
compatible with VMware
vCenter Server.
VMware vCenter Server 6.0 or later

VMware vCenter Server Appliance 6.0 or later

VMware ESXi Server 6.0 or later *3 *4
Hitachi Command VSP G1500 Hitachi Device Manager This guide is based on
Suite *1 8.5.0-00 or later Device Manager 8.5.0-00
VSP F1500
VSP G1000 Hitachi Device Manager
8.2.0-01 or later
VSP Gx00 Hitachi Device Manager
8.2.1-00 or later
VSP Fx00
Hitachi Storage VSP G1500 Storage Provider for This guide is based on
Provider for VMware vCenter 03.3.2 Storage Provider for
VMware vCenter *2 VSP F1500 or later VMware vCenter 03.4.0
VSP G1000 Storage Provider for Exception: iSCSI
VMware vCenter 03.1.0
validation described in this
or later
guide is based on Storage
VSP Gx00 Storage Provider for Provider for VMware
VMware vCenter 03.2.0 vCenter 03.3.0 with VSP
VSP Fx00 or later G600 and VMware
vSphere 6.0.

10
11

TABLE 3. SOFTWARE PREREQUISITES (CONTINUED)

Component Purpose or Where Used Remarks

Storage *4 *5 VSP G1500 80-05 or later This guide is based on
microcode 80-05 with VSP
Hitachi Virtual VSP F1500 G1500
Storage Platform VSP G1000 80-03 or later
Exception: iSCSI
VSP Gx00 83-02 or later validation described in this
document is based on
VSP Fx00
VSP G600 microcode 83-
03.
Hitachi Storage Virtualization Operating System
(SVOS)
Hitachi Local Replication Software:

 Hitachi ShadowImage

 Hitachi Thin Image

*1 For other detailed requirements such as hardware requirements for Hitachi Command Suite, see the Hitachi Com-
mand Suite system requirements.

*2 For other detailed requirements, such as hardware requirements for Hitachi Storage Provider for VMware vCenter,
see the Hitachi Storage Provider for VMware vCenter Deployment Guide.

*3 For end-to-end VMware Virtual Volumes support, the VMware ESXi hosts must have Virtual Volumes-aware HBA
drivers. Refer to the list of I/O devices and drivers that support the Virtual Volumes feature from VMware Compatibility
Guides.

*4 Confirm the following settings for the virtual volumes on the Hitachi storage, and VMware vSphere 6.0 or VMware
vSphere 6.5:

 Enable host mode option 63.

 Disable the VAAI Plugin. See the Hitachi Storage Provider for VMware vCenter Deployment Guide to see
how to disable the VAAI plugin.
*5 There is support for Fibre Channel and iSCSI with VSP G1000, VSP G1500, VSP F1500, VSP Gx00, and VSP Fx00
as a VMware Virtual Volumes-supported protocol.

Prerequisites for Installation

Table 4, “Installation Prerequisites,” on page 12 shows the software requirements necessary to install Hitachi Command
Suite and Hitachi Storage Provider for VMware vCenter.

11
12

TABLE 4. INSTALLATION PREREQUISITES

Software Name Remarks

Hitachi Command Suite See the Hitachi Command Suite System Requirements
Hitachi Storage Provider See the Hitachi Storage Provider for VMware vCenter Storage Provider for VMware
for VMware vCenter Deployment Guide vCenter is distributed as a single
open virtualization format (OVF) file.
Web Microsoft® Internet Explorer® 10.0.19 and later A web browser is used for VMware
browser Mozilla Firefox 34 and later vCenter.

Google Chrome 39 and later

Deploy the Open Virtualization Format (OVF) File for Hitachi Storage Provider for
VMware vCenter
Figure 6 shows the workflow for deploying the open virtualization format file (OVF) which installs Hitachi Storage Provider
for VMware vCenter.

Figure 6

For details regarding the VMware-specific procedures, refer to documentation from VMware.

To deploy the open virtualization format file, do the following:

 From the VMware vSphere Web Client, under Virtual Machines, on the Objects tab, click Deploy OVF Template.
See Figure 7.

Figure 7

12
13

Configure the Storage System Settings Using Hitachi Command Suite for the
VMware Virtual Volumes Environment
Configure the storage system settings for the VMware Virtual Volumes environment using Hitachi Command Suite.

After configuring the storage system for the Virtual Volumes environment, execute the storage settings using Hitachi
Storage Provider for VMware vCenter.

For details regarding this procedure, see “Reference Documents” on page 52.

Figure 8 on page 13 shows the workflow for configuring the storage system settings using Hitachi Command Suite.

Figure 8

To configure the storage system settings from Hitachi Command Suite, do the following.

1. Change the property device manager server to use a function of VMware Virtual Volumes.
2. Set up a user for access control.
 To create a user, on the Users and Permissions window, click Add User. See Figure 9 on page 14.

13
14

Figure 9

3. Register a storage system.

 To add the target storage system, under Storage Systems, click Add Storage System.

Figure 10

14
15

4. Create a dynamic provisioning pool.

This operation is based on a prerequisite that a pool volume has been created already.

(1) Under General Tasks, click Create Pool.

Figure 11

15
16

(2) Under Create Pool, do the following to select the parity group that was used when creating the dynamic
provisioning pool volume:
i. From the Storage System list, click the target storage system.
ii. For Pool Type, click the HDP option.
iii. Click Add Parity Groups.

Figure 12

5. Create a Hitachi Thin Image pool.

This operation is based on the prerequisite that a pool volume has already been created.

Note — To use a VMware snapshot or virtual machine clone from VMware vCenter in a VMware Virtual Volumes
environment with Hitachi Virtual Storage Platform storage, create a Hitachi Thin Image pool and register it in Resource
Group (Storage Container). Otherwise, snapshot operations will fail. Thin Image pools also can be added to the
Resource Group after creating the storage container.

(1) In Hitachi Command Suite, open the Pools window.

(2) To create a Hitachi Thin Image pool, click Create Pools.

16
17

Figure 13

(3) On Create Pools, do the following:

i. From the Pool Type list, click Thin Image.
ii. Click Select Pool VOLs to select the Hitachi Thin Image pool volume that was previously created.

Figure 14

6. Create a resource group

(1) Under Resource Groups, click Create Resource Group.

17
18

Figure 15

(2) Under Create Resource Group, from Storage System, click the target storage system.
(3) Register the dynamic provisioning pool and Hitachi Thin Image pool. Specify the following:
 From DP Pools tab, the dynamic provisioning pool
 From LDEV IDs tab, the LDEV ID of the pool volume for Thin Image pool
(4) Register the unused LDEV ID in the resource group. This unused LDEV ID is used on demand for virtual volumes
provisioned by VMware operations, such as virtual machine creation.

Figure 16

18
19

7. Add a user group.

(1) Click Create User Group to create a user group.
(2) Register the user created previously.
(3) Register the resource group created previously.

Figure 17

8. On the Configuration (Block Storage) tab, create a host group or an iSCSI target to allocate PE (ALU).
(1) Select the target storage system.
(2) Click Set Protocol Endpoints. The Set Protocol Endpoints window opens.

19
20

Figure 18

(3) To create a host group or an iSCSI target to allocate PE (ALU), on the Set Protocol Endpoints window, under
Create Host Groups, click Create Host Groups.

Figure 19

(4) On the Create Host Groups window, do the following:

i. For Host Mode, click 21[VMware Extension].
ii. Under Host Mode Options, select the check box for Mode No. 63.
In a Fibre Channel environment, the Create Host Groups window looks like Figure 20 on page 21.

20
21

Figure 20

In an iSCSI environment, the Create iSCSI Targets window looks like Figure 21.

Figure 21

21
22

9. Create PE (ALU) and allocate PE (ALU).

(1) To create PE (ALU) and allocate PE (ALU), on the Configuration Block Storage tab, do the following:
i. Click the check box of the target storage system.
ii. Click Set Protocol Endpoints. The Set Protocol Endpoints window opens.

Figure 22

(2) To create PE (ALU) and then allocate the PE (ALU) to the host group, on the Set Protocol Endpoints window,
click Allocate ALUs.

Figure 23

22
23

(3) On the Create LDEVs window, for the Provisioning Type, click ALU.

Figure 24

(4) On the Logical Devices window, do the following to set the LUN path of the PE (ALU):
i. Select the check box of the target PE (ALU).
ii. Click Add LUN Paths.

Figure 25

23
24

Set the Storage System Using Hitachi Storage Provider for VMware vCenter for the
VMware Virtual Volumes Environment Configuration
After setting the storage system to build the VMware vSphere Virtual Volumes environment using Hitachi Command Suite,
execute storage settings to build the Virtual Volumes environment using Hitachi Storage Provider for VMware vCenter.

Figure 26 shows the workflow to set the storage system using Storage Provider for VMware vCenter for the VMware
Virtual Volumes environment configuration.

Figure 26

For details regarding this procedure, see “Reference Documents” on page 52.

To set the storage system using Hitachi Storage Provider for VMware vCenter for the VMware Virtual Volumes
environment, do the following.

1. Register a storage system.

(1) Log on to the Hitachi Storage Provider for VMware vCenter web user interface with the VMware vCenter single
sign on account.
(2) To register a storage system, under Manage Storage Systems, click Add Storage Systems.

Figure 27

24
25

2. Create a storage container and define a storage capability profile.

(1) To create a storage container, under Manage Storage Containers, click Create Storage Container.

Figure 28

(2) Under Create Storage Container, do the following to define a storage capability profile:
i. Under Step 1, click the target from the Storage System list.
ii. Under Step 1, click the group from the Resource Group list.
iii. Under Step 2, select the check box for a dynamic provisioning pool.
iv. Under Step 2, click Define Profile.

Note — A storage container used for VMware Virtual Volume implementation can comprise multiple dynamic
provisioning pools. You can also define multiple storage capabilities for each pool in a single storage container. When
you define storage capabilities for each pool in a storage container, Hitachi Thin Image pools added to the resource
group (storage container) automatically reflects the snapshot capability and capacity of the snapshot capacity for the
storage container.

Figure 29

25
26

(3) If needed to define a default profile, under Create Storage Container, click the Advanced Options link (under
the Capability Profiles table). The Default Profiles table opens for you to set the advanced options.

Figure 30

Edit a PE (ALU) and a Storage Container

This is how to edit a PE (ALU) and a storage container.

Edit a Storage Container by Expanding a Dynamic Provisioning Pool or a Hitachi Thin Image Pool
You can edit a storage container using Hitachi Command Suite by expanding a dynamic provisioning pool or a Hitachi
Thin Image pool .

The pool volume has must been previously created before using this procedure.

Figure 31 shows the workflow to edit storage containers by expanding a dynamic provisioning pool or a Hitachi Thin
Image pool.

Figure 31

For details regarding this procedure, see “Reference Documents” on page 52.

26
27

To edit a storage container by expanding a dynamic provisioning pool or Hitachi Thin Image pool, do the following.

1. Expand a dynamic provisioning pool in Hitachi Command Suite.

(1) On the Resources tab, under DP Pools, on the DP Pools tab, select the check box of the target dynamic
provisioning pool.
(2) To expand a dynamic provisioning pool, click Expand Pool.

Figure 32

2. (Optional) Expand a Hitachi Thin Image pool in Hitachi Command Suite.

(1) Using Hitachi Command Suite, open the Pools window of Hitachi Storage Navigator,
(2) Select the check box of the target Hitachi Thin Image pool.
(3) To expand the pool, click Expand Pool.

27
28

Figure 33

(4) After you expand the Thin Image pool, update the information of the target storage system.

Edit a Storage Container by Editing a Storage Capability Profile

You can edit a storage container by editing a storage capability profile using Hitachi Storage Provider for VMware vCenter.

Figure 34 shows the workflow to edit a storage container by editing a storage capability profile.

Figure 34

For details regarding the procedures in this section, see “Reference Documents” on page 52.

28
29

To edit a storage container by editing a storage capability profile, do the following.

1. Log on to the Hitachi Storage Provider for VMware vCenter web user interface with the vCenter single sign on
account.
2. Under Management, click Manage Storage Containers.
3. Under Manage Storage Containers, click Edit Storage Container.
4. Edit the storage capability profile.

Figure 35

5. To edit the storage capability profile, under Edit Storage Container, select the check box for the pool profile to edit
and click Define Profile.

Figure 36

29
30

Edit a PE (ALU) LUN Path

This describes editing a PE (ALU) LUN path using Hitachi Command Suite.

Figure 37 shows the workflow for editing a PE (ALU) LUN path.

Figure 37

For details regarding the procedures in this section, see “Reference Documents” on page 52.

To edit a PE (ALU) LUN path, do the following.

1. Using Hitachi Command Suite, on Hitachi Storage Navigator, open the Logical Devices window.
2. Select the check box of the target PE (ALU).
3. To edit a PE (ALU) LUN path, click the LUN path operation.
 To add a LUN path to an existing PE (ALU), click Add LUN Paths.

Figure 38

30
31

Delete a PE (ALU) or a Storage Container

This describes how to delete a PE (ALU) and a storage container using Hitachi Command Suite, Hitachi Storage
Navigator, and Hitachi Storage Provider for VMware vCenter.

This operation requires that the virtual machine has been deleted previously. In an iSCSI environment, this operation
requires that dynamic or static iSCSI targets have been deleted previously.

Figure 39 shows the workflow for deleting a PE (ALU) and a storage container.

Figure 39

For details regarding the procedures in this section, see “Reference Documents” on page 52.

31
32

To delete a PE (ALU) or a storage container with Hitachi Command Suite, Hitachi Storage Navigator, and Hitachi Storage
Provider for VMware vCenter, do the following.

1. Deallocate a PE (ALU) and delete a PE (ALU)

(1) Using Hitachi Command Suite, in Hitachi Storage Navigator, open the Logical Devices window.
(2) From Storage Navigator, on the Logical Devices window, under LDEV, select the check box of the target PE
(ALU) for deletion.
(3) To delete a LUN path, from the More Actions menu, Click Delete LUN Paths.

Figure 40

(4) From Storage Navigator, on the Logical Devices window, under LDEVs, select the check box of the target PE
(ALU) for deletion.
(5) To delete a PE (ALU), from the More Actions menu, click Delete LDEVs.

32
33

Figure 41

2. Delete a host group or an iSCSI target.

(1) Using Hitachi Command Suite, in Hitachi Storage Navigator, open the Port/Host Groups/iSCSI Targets
window.
(2) Select the check box for a target host group or an iSCSI target for deletion.
(3) To delete the host group or iSCSI target, from the More Actions menu, click one of the following:
 For Fibre Channel environments, Delete Host Groups.
 For iSCSI environments, Delete iSCSI Targets.

33
34

Figure 42

Figure 43

34
35

3. Delete a storage container.

(1) Log on to the web user interface for Hitachi Storage Provider for VMware vCenter using the VMware vCenter
single sign on account.
(2) Select the check box of the storage container to be deleted.
(3) To delete the storage container from the Manage Storage Containers window, click Delete Storage
Container.

Figure 44

4. Delete a dynamic provisioning pool.

(1) Select the check box of the target dynamic provisioning pool for deletion.
(2) Click Delete Pools.

Figure 45

35
36

5. Delete a Hitachi Thin Image pool.

(1) In Hitachi Storage Navigator, open the Pools window.
(2) Select the check box of the target Thin Image pool for deletion.
(3) From the More Actions menu, click Delete Pools.

Figure 46

(4) After you delete ALU or Hitachi Thin Image pools, update the information of the target storage system.
6. Delete a resource group.
(1) Select the check box of the target resource group for deletion.
(2) Click Delete Resource Groups.

36
37

Figure 47

Create a Virtual Machine

This describes how to create a virtual machine.

Figure 48 shows the workflow for creating a virtual machine.

Figure 48

37
38

For details regarding these procedures, see “Reference Documents” on page 52.

For details regarding the procedures for VMware products, follow VMware documentation.

To create a virtual machine with VMware vCenter Server, do the following.

1. Register the Hitachi Storage Provider for VMware vCenter in VMware vCenter Server.
(1) In the VMware vSphere Web Client, on the Configure tab, under Storage Providers, click the Register a new
storage provider button (looks like a plus sign).
(2) Register Hitachi Storage Provider for VMware vCenter in the VMware vCenter Server.

Figure 49

38
39

2. (Fibre Channel environments only) Rescan storage.

 To discover a PE (ALU) as a storage device with the VMware vSphere Web Client, click Rescan Storage.

Figure 50

39
40

3. (iSCSI environments only) Set up dynamic discovery for iSCSI.

(1) From the VMware vSphere web client, on the Storage Adapters tab, select the iSCSI host adapter.
(2) Click Dynamic Discovery.
(3) Click Add.
The Add Send Target Server window opens.

Figure 51

40
41

(4) On the Add Send Target Server window, in the iSCSI Server text box, type the IP address of the iSCSI port of
the storage system.

Figure 52

(5) To discover a PE (ALU) as a storage device, from the VMware vSphere Web Client, click Rescan Storage.

Figure 53

41
42

4. Create a datastore.
(1) To create a datastore, from the VMware vSphere Web Client, on the Actions menu, click Storage, and then click
New Datastore. The New Datastore window opens.

Figure 54

(2) On the New Datastore window, for Type, click the VVol option.

Figure 55

42
43

(3) On the New Datastore window, for Name and container selection, do the following:
i. In the Datastore name text box, type the datastore name.
ii. Under Backing Storage Container, select the target storage container from the list of storage containers.

Figure 56

(4) On the New Datastore window, for Select Host Accessibility, select the check box of the host that requires
access to the datastore.

Figure 57

43
44

5. Define a virtual machine storage policy.

(1) To define a virtual machine storage policy, from the VMware vSphere Web Client, on the VM Storage Policies
tab, click Create a new VM storage policy. The Create a New VM Storage Policy window opens.

Figure 58

(2) On the Create a New VM Storage Policy window, for Name and description, do the following:
i. From the vCenter Server list, click the IP address of the server.
ii. In the Name text box, type the name of the virtual machine storage policy.

Figure 59

44
45

(3) On the Create a New VM Storage Policy window, for 2b Rule-Set 1, do the following:
i. Select the Use rule sets in the storage policy check box.
ii. From the Storage Type menu, click com.hitachi.storageprovider.vvol.
iii. Set a rule on one or more storage classes by selecting the check box.

Figure 60

6. Create a virtual machine.

(1) To create a new virtual machine, from the VMware vSphere Web Client, under Datacenter, on the Summary tab,
from the Actions menu, click New Virtual Machine, and then click New Virtual Machine. The New Virtual
Machine window opens.

Figure 61

45
46

(2) On the New Virtual Machine window, for 2c Select storage, do the following:
i. From the VM storage policy list, click the storage policy for the virtual machine.
ii. Under Compatible, select a datastore matching the virtual machine storage policy.

Figure 62

Uninstall the VMware Virtual Volumes Environment

This describes how to uninstall the VMware Virtual Volumes environment.

Figure 63 on page 47 shows the workflow for uninstalling the Virtual Volumes environment.

46
47

Figure 63

For details regarding these procedures, see “Reference Documents” on page 52.

For details regarding the VMware procedures, see the VMware documentation.

47
48

To uninstall the VMware Virtual Volumes environment, do the following.

1. Delete the virtual machine.

(1) From the VMware vSphere Web Client, under Navigator, Select the virtual machine to be deleted.
(2) From the Actions menu, click Delete from Disk.

Figure 64

2. Unmount (delete) a datastore.

(1) From the VMware vSphere Web Client, select the datastore to be unmounted (deleted).
(2) From the Actions menu, click Unmount Datastore.

48
49

3. (iSCSI only) Remove the dynamic and static iSCSI targets.

(1) To remove one or more dynamic iSCSI targets, do the following.
i. From the VMware vSphere Web Client, under Navigator, select the iSCSI adapter.
ii. On the Manage tab, under Adapter Details, click Dynamic Discovery.
iii. Select one or more iSCSI servers for deletion.
iv. Click Remove.

Figure 65

(2) To remove one or more static iSCSI targets, do the following.

i. From the VMware vSphere Web Client, under Navigator, select the iSCSI adapter.
ii. On the Manage tab, under Adapter Details, click Static Discovery.
iii. Select one or more iSCSI servers for deletion.
iv. Click Remove.

49
50

Figure 66

(3) From the VMware vSphere Web Client, click the Rescan Storage button (Figure 67).

Figure 67

50
51

4. Delete Hitachi Storage Provider for VMware vCenter.

(1) (Recommended step) Delete the virtual volumes environment on VMware vCenter Server before the uninstalling
Hitachi Storage Provider for VMware vCenter. This is a recommendation from Hitachi Data Systems.
(2) Delete the virtual machine for Hitachi Storage Provider for VMware vCenter.
5. Return a server property in Hitachi Device Manager to its original state.
 Return the setting of a server property in Device Manager that was changed to return a VMware Virtual Volumes
function back to its original state.
6. Deallocate the PE (ALU) and delete the PE (ALU).
 See the first step of “Delete a PE (ALU) or a Storage Container” on page 31.
7. Delete the host group.
 See the second step of “Delete a PE (ALU) or a Storage Container” on page 31.
8. Delete the dynamic provisioning pool.
 See the fourth step of “Delete a PE (ALU) or a Storage Container” on page 31.
9. Delete the Hitachi Thin Image pool.
 See the fifth step of “Delete a PE (ALU) or a Storage Container” on page 31.
10. Delete the resource group.
 See the sixth step of “Delete a PE (ALU) or a Storage Container” on page 31.

Terms and Abbreviations

Table 5 lists terms and abbreviations used in this implementation guide.

TABLE 5. TERMS AND ABBREVIATIONS

Term Description
ALU This is the abbreviation for administrative logical unit.

This indicates a volume that is an access pointer for a virtualization server. An ALU must be
allocated to a virtualization server to use virtual volumes. With the virtual machine, an ALU is
equivalent to a PE.
HCS This is the abbreviation for Hitachi Command Suite.

Hitachi Command Suite consists of many storage management software products used for
managing storage resources in large-scale and complex SAN environments.

Command Suite uses Hitachi Device Manager, which is a base product for storage management
in the VMware Virtual Volumes environment.
PE This is the abbreviation for protocol endpoint.

This indicates a volume with ALU attributes.

51
52

TABLE 5. TERMS AND ABBREVIATIONS (CONTINUED)

Term Description
SLU This is the abbreviation for subsidiary logical unit.

This indicates a volume that stores the data of the virtual machine. When creating a virtual
machine, an SLU is created from a dynamic provisioning pool or Hitachi Thin Image pool, and it is
bound (using path allocation) to an ALU. With the virtual machine, SLU is equivalent to a virtual
volume.
SPBM This is the abbreviation for storage policy-based management.

Based on the volume requirements (virtual machine storage policy) that the virtual machine
administrators define, Hitachi Storage Provider for VMware vCenter automatically chooses the
storage resources suitable for the requirements and either creates or allocates volumes by SPBM.
Storage Container This is a set of resources, such as dynamic provisioning pools or Hitachi Thin Image pools, used
to make a virtual machine, snapshot, and a clone.
VASA Abbreviation for VMware vSphere API for Storage Awareness.

This indicates the overall storage management functions of vSphere.

Hitachi Storage This indicates the implementation by Hitachi of VMware vSphere API for Storage Awareness.
Provider for VMware
vCenter This software performs various processing for the storage system, based on the VASA API from
VMware vCenter Server and VMware ESXi.
VVols Abbreviation for virtual volumes.

This indicates a volume that can be used in policy-based datastore operation, which is a function
that is available with Hitachi Virtual Storage Platform storage.

Reference Documents
Table 6 lists reference documents for the procedures in this implementation guide.

TABLE 6. REFERENCE DOCUMENTS

Document Name
Hitachi Storage Provider for VMware vCenter Deployment Guide
Hitachi Command Suite User Guide
Hitachi Command Suite Installation and Configuration Guide
Hitachi Command Suite Administrator Guide
Provisioning Guide for Open Systems

 Hitachi Virtual Storage Platform G1000 and G1500

 Hitachi Virtual Storage Platform F1500

52
53

TABLE 6. REFERENCE DOCUMENTS (CONTINUED)

Document Name
Provisioning Guide

 Hitachi Virtual Storage Platform G200, G400, G600, G800

 Hitachi Virtual Storage Platform F400, F600, F800

Hitachi Thin Image User Guide

 Hitachi Virtual Storage Platform G1000 and G1500

 Hitachi Virtual Storage Platform F1500

 Hitachi Virtual Storage Platform G200, G400, G600, G800

 Hitachi Virtual Storage Platform F400, F600, F800

53
For More Information
Hitachi Data Systems Global Services offers experienced storage consultants, proven methodologies and a
comprehensive services portfolio to assist you in implementing Hitachi products and solutions in your environment. For
more information, see the Services website.

Live and recorded product demonstrations are available for many Hitachi products. To schedule a live demonstration,
contact a sales representative. To view a recorded demonstration, see the Resources website.

Hitachi Data Systems Academy provides best-in-class training on Hitachi products, technology, solutions and
certifications. Hitachi Data Systems Academy delivers on-demand web-based training (WBT), classroom-based
instructor-led training (ILT) and virtual instructor-led training (vILT) courses. For more information, see the Hitachi Data
Systems Services Training and Certification website.

For more information about Hitachi products and services, contact your sales representative or channel partner or visit the
Hitachi Data Systems website.
1

Corporate Headquarters Regional Contact Information

2845 Lafayette Street Americas: +1 866 374 5822 or info@hds.com
Santa Clara, CA 95050-2639 USA Europe, Middle East and Africa: +44 (0) 1753 618000 or info.emea@hds.com
www.HDS.com community.HDS.com Asia Pacific: +852 3189 7900 or hds.marketing.apac@hds.com

© Hitachi Data Systems Corporation 2017. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. HDS, VSP, and ShadowImage are trademarks of
Hitachi Data Systems. Microsoft and Internet Explorer are trademarks or registered trademarks of Microsoft Corporation. All other trademarks, service marks, and company names
are properties of their respective owners.
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by
Hitachi Data Systems Corporation.
AS-608-00, July 2017.