Dell EMC Unity™ Family

Configuring Hosts to Access VMware Datastores

Version 5.1

Part Number: 302-002-569

June 2021
Rev. 03
Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid
the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2017 - 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Other trademarks may be trademarks of their respective owners.
 Contents

Additional resources..................................................................................................................... 5

Chapter 1: Introduction................................................................................................................. 6
System requirements..........................................................................................................................................................6
Managed and generic host objects................................................................................................................................. 6
VMware vSphere versions.................................................................................................................................................7

Chapter 2: Setting up a host to use Unity VMware NFS datastores............................................... 8

Requirements for setting up a host................................................................................................................................ 8
Network requirements..................................................................................................................................................8
Using network high availability......................................................................................................................................... 8
Link aggregations...........................................................................................................................................................8
Configuring a link aggregation.................................................................................................................................... 9
Configuring Unity NFS datastores for the host......................................................................................................... 10
Manually setting up the connection to a Unity NFS datastore.............................................................................. 10

Chapter 3: Setting up a host to use Unity VMware VMFS iSCSI datastores.................................. 12

Requirements for setting up a host to use Unity VMware VMFS datastores.....................................................12
iSCSI network requirements for host connection to VMFS datastores......................................................... 12
Path management network requirements for VMFS datastores..................................................................... 12
Using multi-path management software with ESXi hosts....................................................................................... 13
Setting up your system for multi-path management software.........................................................................13
Installing PowerPath....................................................................................................................................................14
Configuring the ESXi iSCSI adapters............................................................................................................................ 14
Creating a VMkernel port for the software iSCSI adapter...................................................................................... 14
Setting up multipathing for iSCSI.................................................................................................................................. 15
Configuring the Unity VMware VMFS datastores for the host..............................................................................15
Configuring ESXi host native failover........................................................................................................................... 16
Configuring the native failover policy for iSCSI connections............................................................................ 16
Manually setting up the iSCSI connection for a Unity VMFS datastore...............................................................17
Manually configuring a Unity iSCSI VMFS datastore................................................................................................ 17
iSCSI session troubleshooting for ESXi hosts.............................................................................................................18

Chapter 4: Setting up a host to use Unity VMware VMFS FC datastores...................................... 19

Requirements for setting up a host to use Unity VMware VMFS datastores with FC.....................................19
SAN requirements........................................................................................................................................................ 19
Path management SAN requirements.....................................................................................................................19
Using multi-path management software with ESXi hosts....................................................................................... 19
Setting up a Unity system for multi-path management software ..................................................................20
Installing PowerPath...................................................................................................................................................20
Configuring ESXi host native failover.......................................................................................................................... 20
Configuring the native failover policy for FC connections................................................................................20
Configuring the Unity VMware VMFS datastores for the host.............................................................................. 21
Manually configuring a Unity VMware VMFS datastore.......................................................................................... 21

Contents 3
 Chapter 5: Setting up a host to use Unity vVol datastores........................................................... 23
Add the storage system as a VASA provider..............................................................................................................23
Configuring Unity File vVol datastores for the host................................................................................................. 23
Setting up the connection to a File vVol datastore.................................................................................................. 24
Add an iSCSI target for Block vVol datastores.......................................................................................................... 24
Configuring the Unity Block vVol datastores for the host...................................................................................... 24

Chapter 6: Migrating VMware Virtual Machines to the Unity system........................................... 26

VMware virtual machine migration environment and limitations........................................................................... 26
Migrating a virtual machine to a Unity datastore...................................................................................................... 27
Migrating a virtual machine with suspended migration...................................................................................... 27
Migrating a virtual machine with Storage vMotion............................................................................................. 27

4 Contents
 Preface

As part of an improvement effort, revisions of the software and hardware are periodically released. Therefore, some functions
described in this document might not be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features. Contact your technical support professional if a
product does not function properly or does not function as described in this document.

Where to get help

Support, product, and licensing information can be obtained as described below.

Product information
For product and feature documentation or release notes, go to Unity Technical Documentation at: dell.com/unitydocs.

Troubleshooting
For information about products, software updates, licensing, and service, go to Support (registration required) at: dell.com/
support. After logging in, locate the appropriate product page.

Additional resources 5
 1
Introduction
This chapter describes high-level host requirements.
Topics:
• System requirements
• Managed and generic host objects
• VMware vSphere versions

System requirements
Before configuring hosts to access the storage system, ensure that the following tasks are completed.
● Install and configure the system using the Initial Configuration wizard.
● Use Unisphere or the CLI to configure NAS servers or interfaces, or iSCSI or Fibre Channel (FC) LUNs, on the storage
system.

Managed and generic host objects

There are two ways of deploying traditional Unity VMFS and NFS datastores to vSphere:
● Automatically using managed host objects
● Manually using generic host objects

Managed host objects

Managed host objects use a set of APIs on the array to prepare vSphere for Unity VMFS or NFS datastores and mounts them
automatically.
For example, when deploying an iSCSI VMFS datastore:
1. The user completes the following actions on the storage system:
a. Creates the iSCSI interface.
b. Creates the VMFS datastore.
c. Grants host access to the datastore.
2. The following processes then occur automatically:
a. The storage system sends a request to the associated hosts to add the iSCSI interface for the VMFS datastore to the
iSCSI table in vSphere.
b. vSphere confirms to the storage system that the LUN device (for the VMFS datastore) has been added to the target
table in vSphere.
c. The storage system sends a request to vSphere to format that LUN device as a VMFS datastore.

Generic host objects

Unity File vVol and Block vVol datastores use generic host objects by default. Refer to Setting up a host to use Unity vVol
datastores for more information.
You may also want to use generic host objects in the following cases:
● You want to boot the host from the storage system
● You are using non-ESXi hosts for backup purposes

6 Introduction
● You are deploying an NFS datastore on a NAS server using NFSv4.0 or later (managed host objects deploy NFS datastores
as the default NFSv3.0).
To use generic host objects, manually set up the connection to the datastores as described in Manually setting up the iSCSI
connection for a Unity VMFS datastore or Manually setting up the connection to a Unity NFS datastore

VMware vSphere versions

The VMware vSphere instructions in this guide may not be consistent with your version of vSphere. Always use the VMware
documentation for your vSphere version for the most up-to-date detailed instructions.
NOTE: All vVols-related vSphere instructions in this guide are based on the vSphere 7.0.2 web client. The vVols feature is
not available in VMware releases of vSphere that are earlier than 6.x.

Introduction 7
 2
Setting up a host to use Unity VMware NFS
datastores
This chapter describes how to set up a VMware ESXi host or virtual machine to use Unity VMware NFS datastores.
Topics:
• Requirements for setting up a host
• Using network high availability
• Configuring Unity NFS datastores for the host
• Manually setting up the connection to a Unity NFS datastore

Requirements for setting up a host

These system and network requirements must be met before setting up a host to use Unity storage.
Before you can set up a host to use Unity storage, the following storage system and network requirements must be met.

Network requirements
This topic lists the network requirements for a host attaching to a Unity system.
Ensure that you meet these network requirements:
● The host (client) is in the same LAN environment as the Unity NAS server.
● If the NAS server is enabled for multiprotocol (CIFS and NFS), you have connected it to an NIS server or an LDAP server.
The Unisphere online help describes how to configure Unix Directory Service (either NIS or LDAP) on the system.
NOTE: Users can store files on a Unity NAS server in a Network Information Service (NIS) environment, but you cannot
configure a Unity NAS server as an NIS client.

Using network high availability

This topic describes how to use link aggregation for high availability configurations.
The Unity system supports link aggregations that allow up to four Ethernet ports connected to the same physical or logical
switch to be combined into a single logical link. To configure link aggregation on the system, each storage processor (SP) must
have the same type and number of Ethernet ports as link aggregation actually creates two link aggregations — one on each SP.
This provides high availability. If one of the ports in the link aggregation fails, the system directs the network traffic to one of
the other ports in the aggregation. If you add an Ethernet I/O module to each SP in the system, you can create one additional
link aggregation group (LAG) on the set of ports in the I/O module.

Link aggregations
This topic describes the advantages and function of link aggregations.
Link aggregations use the Link Aggregation Control Protocol (LACP) IEEE 802.3ad standard.

NOTE: Link Aggregation does not apply to iSCSI interfaces.

A link aggregation appears as a single Ethernet link with these advantages:

● High availability of network paths to and from the Unity system — If one physical port in a link aggregation fails, the system
does not lose connectivity.

8 Setting up a host to use Unity VMware NFS datastores

● Possible increased overall throughput — Because multiple physical ports are bonded into one logical port with network
traffic distributed between the multiple physical ports.
Although link aggregations can provide more overall bandwidth than a single port, the connection to any single client runs
through one physical port and is therefore limited by the port’s bandwidth. If the connection to one port fails, the switch
automatically switches traffic to the remaining ports in the group. When the connection is restored, the switch automatically
resumes using the port as part of the group.
On the Unity system, you can configure up to four ports in a link aggregation. When you configure a link aggregation, you are
configuring two link aggregations — one on each SP. If one of the ports in an aggregation fails, the system directs network
traffic to one of the other ports in the group.

Switch requirements
This topic describes switch requirements when using link aggregation.
If the Unity ports are connected to different network switches, you should configure all switch ports connected to these ports
to immediately switch from blocking mode to forwarding mode and not pass through spanning tree states of listening and
learning when an interface comes up. On Cisco switches, this means that you must enable the portfast capability for each
switch port connected to a Unity port to guarantee that the switch forwards the Ethernet frame that the storage system
generates when a physical link is enabled. You enable the portfast capability on a port-to-port basis. When enabled, the portfast
variable causes the port to immediately switch from blocking to forwarding mode. Do not use portfast on switch-to-switch
connections.
For link aggregation, network switches must have IEEE 802.3ad protocol support and guarantee that packets from a single TCP
connection always go through the same link in a single direction.

Configuring a link aggregation

This topic describes link aggregation configuration and lists the required configuration tasks.
For link aggregation, you have at least one 802.3ad-compliant switch, each with an available port for each switch port you want
to connect to a Unity port in the aggregation.
The term NIC teaming refers to all NIC redundancy schemes, including link aggregation with 802.3ad.
For link aggregation, you need to perform two sets of configuration tasks:
● Configure a link aggregation from the switch to the Unity system
● Configure a link aggregation from the host to the switch

Configuring link aggregation from the switch to the Unity system

Learn how to configure the switch ports and join them into a link aggregation.

Steps
1. Configure the switch ports, which are connected to the Unity system, for LACP in active mode. Refer to the documentation
provided with your switch for details.
2. Join the ports into a link aggregation using Unisphere. To do this:
a. Select the Settings icon, then select Access > Ethernet.
b. Select an Ethernet port, then select Link Aggregation > Create Link Aggregation.
c. Select the ports for the link aggregation, then select Create.

Results
Two link aggregations are created with the same ports — one aggregation on each SP.

Configuring link aggregation from the ESXi host to the switch

Steps
1. Configure the switch ports for link aggregation.

Setting up a host to use Unity VMware NFS datastores 9

 NOTE: Depending on the type of NIC teaming used, you may not need to configure these switch ports for link
aggregation. For more information, refer to your VMware documentation.

2. On an ESXi host, you create a NIC team by creating a virtual switch with two or more physical NICs. For information on
creating a virtual switch, refer to the VMware documentation for the version of ESXi running on the host.

Configuring Unity NFS datastores for the host

About this task
Use the Unisphere UI or CLI to:

Steps
1. Discover VMware ESXi hosts.
2. Create NFS datastores.
When you create NFS datastores for discovered VMware ESXi hosts, the Unity system automatically configures the hosts to
use the datastores. If you select multiple hosts to have access to the NFS datastore, all the selected hosts are configured
automatically.
NOTE: The Unity system automatically mounts NFS datastores as NFSv3.0. NAS servers using Kerberos security use
NFSv4.1. In order to use NAS servers enabled for Kerberos or NFSv4 for Unity NFS datastores, you must manually
mount the datastores. Refer to Manually setting up the connection to a Unity NFS datastore

Next steps
For more information on performing these tasks, refer to the Unisphere online help or Unisphere CLI User Guide.

Manually setting up the connection to a Unity NFS

datastore
Prerequisites
Manually set up the connection to an NFS datastore if you are using generic host objects, or if you want to mount NFS
datastores as NFSv4 and later.

Steps
1. In Unisphere, as an administrator ensure hosts have access to the NFS datastore.
a. Under Storage, select VMware > Datastores.
b. Select the NFS datastore and click the Edit icon to view its properties.
NOTE: On the Host Access tab, you can choose to configure a default access for all hosts or customized access to
individual hosts. Setting up customized access for hosts overrides default access for those hosts. For an ESXi host
to be able to access an NFS datastore, it must be granted access. Also, in order to use a NAS server enabled for
Kerberos or NFSv4 for Unity NFS datastores, you must manually mount the datastores. Select NFSv4 for Mount
datastore from VMware hosts protocol for these datastores

2. Find the IP address of the NAS server for the NFS datastore. On the General tab, note the Export Paths.
For example, for Export Path 10.0.0.1/nfsdatastore123, 10.0.0.1 is the IP address of the NAS server for NFS datastore
nfsdatastore123.
3. Log in to vSphere as an administrator.
4. For each NFS datastore:
a. From Hosts and Clusters, select the server.
b. From the Actions drop down list, select Storage > New Datastore....
The New Datastore wizard appears.
c. In the New Datastore wizard, do the following:
i. Select NFS as the datastore type.

10 Setting up a host to use Unity VMware NFS datastores

ii. Select the NFS version.
iii. Enter the following NFS share details:
● For name, enter the name of the new VMware datastore.
● For folder, enter the path to the Unity share.
● For server, enter the IP address of the Unity NAS server.
iv. For NFS version 4.1 Kerberos, configure the Kerberos authentication.

Setting up a host to use Unity VMware NFS datastores 11

 3
Setting up a host to use Unity VMware VMFS
iSCSI datastores
This chapter describes the requirements for setting up an ESXi host to use EMC Unity VMFS datastores, how to set up the
ESXi host for path management software, and how to troubleshoot the connection between the ESXi host and a Unity VMFS
datastore.
Topics:
• Requirements for setting up a host to use Unity VMware VMFS datastores
• Using multi-path management software with ESXi hosts
• Configuring the ESXi iSCSI adapters
• Creating a VMkernel port for the software iSCSI adapter
• Setting up multipathing for iSCSI
• Configuring the Unity VMware VMFS datastores for the host
• Configuring ESXi host native failover
• Manually setting up the iSCSI connection for a Unity VMFS datastore
• Manually configuring a Unity iSCSI VMFS datastore
• iSCSI session troubleshooting for ESXi hosts

Requirements for setting up a host to use Unity

VMware VMFS datastores
Before you set up a host to use Unity VMware VMFS datastores, these storage system and host and network requirements
must be met.

iSCSI network requirements for host connection to VMFS

datastores
For a host to connect to VMware VMFS datastores on a Unity iSCSI interface, the host must be in a network environment
as the iSCSI interface. To achieve best performance, the host should be on a local subnet with each Unity iSCSI interface
that provides storage. For a Windows multi-pathing environment, each Unity iSCSI interface providing iSCSI LUNs for the host
must have two IP addresses associated with it. These two addresses should be on different subnets to ensure high availability.
If possible, you should segment network traffic from the Unity system through a private LAN using either a virtual LAN or a
dedicated network switch.
To achieve maximum throughput, connect the Unity iSCSI interface and the hosts for which it provides storage to their own
dedicated private network. Consider network performance when choosing the network.

Path management network requirements for VMFS datastores

When implementing a highly-available network between a host and the Unity system, keep in mind that:
● You can configure up to 32 IPs/VLANs per physical interface. You can create up to 64 iSCSI IPs per system.
● Network switches may be on separate subnets.
NOTE: Directly attaching an ESX host to a Unity system is supported.

The following figure shows a highly-available iSCSI network configuration for hosts accessing a Unity storage resource (VMware
VMFS datastore). Switch A and Switch B are on separate subnets. Host A and Host B can each access the storage resource
through separate NICs. If the storage resource is owned by SP A, the hosts can access the storage resource through the paths

12 Setting up a host to use Unity VMware VMFS iSCSI datastores

to the eth2 interface on SP A. Should SP A fail, the Unity system transfers ownership of the resource to SP B and the hosts can
access the storage resource through the paths to the eth2 interface on SP B.

Figure 1. Highly-available iSCSI network example

Using multi-path management software with ESXi

hosts
Multi-path management software manages the connections (paths) between the host and the Unity system to provide access
to the Unity storage should one of the paths fail. The following types of multi-path management software are available for an
ESXi host connected to a Unity system:
● ESXi native failover on any ESXi host
● EMC PowerPath/VE software on an ESXi 5.x or later host
For the supported versions of the PowerPath/VE software, refer to the Unity Support Matrix on the support website.

Setting up your system for multi-path management software

For your system to operate with hosts running multi-path management software, two iSCSI IPs are required. These IPs should
be on separate physical interfaces on separate SPs.
Verify the configuration in Unisphere. For details on how to configure iSCSI interfaces, refer to topics about iSCSI interfaces in
the Unisphere online help.
NOTE: For highest availability, use two network interfaces on the iSCSI interface. The network interfaces should be on
separate subnets. You can view the network interfaces for an iSCSI interface within Unisphere.

Setting up a host to use Unity VMware VMFS iSCSI datastores 13

Installing PowerPath
Steps
1. On the host or virtual machine, download the latest PowerPath version from the PowerPath software downloads section on
the Online Support website.
2. Install PowerPath as described in the appropriate PowerPath installation and administration guide for the host’s or virtual
machine’s operating system.
This guide is available on Online Support. If the host or virtual machine is running the most recent version and a patch exists
for this version, install it, as described in the readme file that accompanies the patch.
3. When the installation is complete, reboot the host or virtual machine.
4. When the host or virtual machine is back up, verify that the PowerPath service has started.

Configuring the ESXi iSCSI adapters

About this task
Follow these steps to configure software iSCSI adapters. If CHAP authentication is required, follow VMware vSphere
documentation to configure CHAP parameters for iSCSI adapters.

Steps
1. Log in to VMware vSphere Client as administrator.
2. From Hosts and Clusters, select the server with the initiator that you want to configure.
3. Select Configure.
4. Under Storage select Storage Adapters.
5. Select Add Storage Adapter, and then select Add software iSCSI adapter and click OK.
Use the adaptor details section to complete the configuration.
6. Select the iSCSI adapter that you want to configure, and click Properties.
To configure the General and Authentication properties for the iSCSI adapter, click Edit... to the right of the related
settings heading.
7. (Optional) For General properties, click Edit... and enter a user-friendly iSCSI name and an iSCSI alias for the software
iSCSI adaptor, and then click OK.
8. [Generic host objects only] Add target addresses for the software iSCSI adapter:
a. Select Dynamic Discovery and click Add.
b. Add the target’s information and click OK.
c. Click Rescan Adapter.
9. If you want to configure CHAP credentials for the target, access the Storage Adapters page and do the following:
a. Select the adapter and click the Static Discovery tab.
b. Select the iSCSI server from the list and click Authentication.
c. Add the target's CHAP information.
d. Rescan the adapter.

Creating a VMkernel port for the software iSCSI

adapter
About this task
Connect the VMkernel, which runs services for iSCSI storage, to the physical network adapter.

Steps
1. Log in to the vSphere Client as an administrator.
2. From Hosts and Clusters, select the host.

14 Setting up a host to use Unity VMware VMFS iSCSI datastores

3. Select Configure.
4. Under Networking, select Virtual Switches.
5. In the Virtual switches view, click Add Networking....
6. Select VMkernel Network Adapter and click Next.
7. Select either an existing network or switch or to create a new switch and click Next.
If you select either an existing network or switch, go to step 9.
8. To create a new switch, select an adapter that you want to use for iSCSI traffic and click Next.
NOTE: Do not use iSCSI on 100 Mbps or slower adapters.

If no adapters appear under Create a virtual switch, the existing vSwitches are using all the network adapter in the host. In
this situation, you can use an existing vSwitch for iSCSI traffic.
9. Under Port properties, enter the applicable VMkernel port settings and click Next.
The network label is the name that you want to identify the VMkernel port that you are creating.
10. Specify the IP settings and click Next.
11. After you review the summary information, click Finish.
12. Bind the VMkernel adapter that was created in the previous step to the iSCSI software adapter:
a. From Hosts and Clusters, select the host.
b. Select Configure.
c. Under Storage select Storage Adapters.
d. Select Network Port Binding and click Add.
e. Select the VMkernel adapter from the list of adapters and click OK.

Next steps
If your host uses only one physical network adapter for iSCSI, your network configuration is complete.
If your host uses more than one physical network adapter for iSCSI, you must connect additional adapters to the vSwitch and
associate each port with a VMkernel port using the port binding technique. You can do this in one of following ways:
● Create separate vSwitches for each additional network adapter by repeating the above steps for each additional adapter.
● Use a single vSwitch for iSCSI multipathing by connecting the additional network adapters and VMkernel ports to the
vSwitch that you just created and override the default setup so that each port maps to only one active adapter.

Setting up multipathing for iSCSI

Follow the VMware vSphere documentation to set up multipathing for iSCSI.

Configuring the Unity VMware VMFS datastores for

the host
Steps
1. Add the software iSCSI adapter, if not already added, as described in VMware vSphere documentation.
2. Set up the iSCSI session between the ESXi host and the Unity system:
a. Select the ESXi host->Storage->Storage Adapters->iscsi adapter.
b. From Hosts and Clusters, select the ESXi host.
c. Select Configure.
d. Under Storage select Storage Adapters.
e. Select the iSCSI adapter from the list of adapters.
f. Select Static Discovery and click Add.
g. Enter one of the iSCSI target IP addresses that you configured on the Unity system and click OK.
3. Use Unisphere UI or CLI to:
a. Discover VMware ESXi hosts.
b. Create Unity VMFS datastores.

Setting up a host to use Unity VMware VMFS iSCSI datastores 15

 c. Assign host access during Unity VMFS datastore creation.
For more information about completing these tasks, refer to the Unisphere online help or the Unisphere CLI User Guide.
NOTE: When you create Unity VMFS datastores for discovered VMware ESXi hosts, the system automatically
configures the hosts to use the datastores. If you select multiple discovered hosts for the datastores, all the selected
hosts are configured automatically. The VMware VMFS datastores are presented directly to the ESXi hosts and not to
the hosts’ virtual machines. If an ESXi host cannot see the VMFS datastore after you create the datastore, manually
configure the connection to the VMFS datastore.

4. If you are providing access to hosts that are not registered as ESXi, rescan for the VMFS datastores:
a. From Hosts and Clusters, select the server.
b. Select Configure.
c. Under Storage, select Storage Adapters.
d. Select the iSCSI storage adapter in the list of adapters.
e. Select Rescan Storage....
If the host can see the VMFS datastore, you must set up the host to use the datastore, as described in the next section.
If the host cannot see the VMFS datastore, you may have a problem with the connection between the host and iSCSI target
(iSCSI connection). Refer to iSCSI session troubleshooting for ESXi hosts for additional steps to resolve the problem.

Configuring ESXi host native failover

ESXi hosts include native failover for managing the I/O paths between the server and storage system. Native failover provides
multiple paths from the server to the storage system. To use ESXi host native failover with your storage system, you
must implement one of the failover policies listed below. For more information about these policies, refer to VMware ESXi
configuration documentation.
● Round Robin (default)
● Fixed with failover mode
● Most Recently Used (MRU)

Configuring the native failover policy for iSCSI connections

Steps
1. Log into the vSphere client as administrator.
2. From Hosts and Clusters, select the server.
3. Select Configure.
4. Under Storage, select Storage Devices and select the storage device from the list.
5. Under Properties and to the right of Multipathing Policies, select Edit Multipathing... which is listed under Actions.
The Edit Multipathing Policies dialog box appears.
6. For Path selection policy, verify that the selected policy is the one that you want:
● Fixed (VMware) for fixed native failover policy
● Round Robin (VMware) for Round Robin native failover policy
● Most Recently Used (VMware) for MRU native failover policy
If the policy is not set to the desired policy, select the correct policy.
7. If you selected the Fixed (VMware) policy, select the preferred path.
You can statically balance the load using the fixed policy by selecting different paths for each datastore. To designate a
different path as preferred, select the path from the list.
8. Click OK.

Next steps
You are now ready to either migrate a virtual machine to the VMFS datastore or create a virtual machine on the VMFS
datastore. To migrate a virtual disk to the VMFS datastore, see the section on Migrating VMware Virtual Machines to the Unity
System. For information about creating a virtual machine on the VMFS datastore, refer to the VMware documentation.
A rescan of the storage is required after any change is made to the SAN.

16 Setting up a host to use Unity VMware VMFS iSCSI datastores

Manually setting up the iSCSI connection for a Unity
VMFS datastore
About this task
If you want to use generic host objects, you must manually add the software iSCSI adapter:

Steps
1. Log in to the vSphere Client as an administrator.
2. From Host and Clusters, select the host with the initiator you want to configure.
3. Select Configure.
4. Under Storage click Storage Adapters.
5. If the Software iSCSI adapter is not listed, click Add Software Adapter, and then select Add software iSCSI adapter.
6. Select the iSCSI adapter that you want to configure, and click Properties.
To configure the General and Authentication settings for the iSCSI adapter, click Edit... to the right of the related
settings heading.
7. (Optional) For General settings, click Edit... and enter a user-friendly iSCSI name and an iSCSI alias for the software iSCSI
adaptor, and then click OK.

Manually configuring a Unity iSCSI VMFS datastore

Steps
1. Log in to the vSphere client as an administrator.
2. Set up the iSCSI session between the ESXi host and the Unity system:
a. Select the ESXi host->Storage->Storage Adapters->iscsi adapter.
b. From Hosts and Clusters, select the ESXi host.
c. Select Configure.
d. Under Storage select Storage Adapters.
e. Select the iSCSI adapter from the list of adapters.
f. Select Static Discovery and click Add.
g. Enter one of the iSCSI target IP addresses that you configured on the Unity system and click OK.
3. Rescan for new storage devices:
a. From Hosts and Clusters, select the server.
b. Select Configure.
c. Under Storage, select Storage Adapters.
d. Select the iSCSI adapter from the list of adapters.
e. Select Rescan Storage...
4. Add each VMFS datastore to the ESXi host:
a. From Hosts and Clusters, select the host.
b. From the Actions drop down list, select Storage > New Datastore....
The New Datastore wizard appears.
c. In the New Datastore wizard, do the following:
i. Select VMFS as the datastore type.
ii. Specify a datastore name and a disk/LUN for provisioning the datastore.
iii. Specify the VMFS version for the datastore.
iv. Review the disk layout and specify the partition configuration details.
v. Review the datastore information, and click Finish.

Results
The Unity VMFS datastores are configured for the ESXi host.

Setting up a host to use Unity VMware VMFS iSCSI datastores 17

iSCSI session troubleshooting for ESXi hosts
About this task
Verify the connectivity between the host and the target either from the storage system iSCSI interface IP interface or from the
ESXi host:

Steps
1. Verify the connectivity between the host and the target either from the Unity iSCSI interface IP interface or from the ESXi
host:
From the iSCSI IP interface:
a. Select the Settings icon, then select Access > Routing.
b. Select the iSCSI interface and select Ping/Trace.
c. Enter the network name of the host iSCSI adapter, select the IP address from which to send the request, and click Ping.
From the ESXi host:
a. Use vmkping to verify connectivity to the Unity iSCSI interface IP interfaces.
b. If jumbo frames are configured, you should use vmkping with the -s option at a size larger than 1500 to verify that all
network elements are properly configured for jumbo frames.
vmkping -s 9000 <IP_address_of_iSCSI _Server>
Using the IP address avoids name resolution issues.
NOTE: You can find the IP address for the target by selecting Settings > iSCSI Settings in Unisphere.
Some switches intentionally drop ping packets or lower their priority during times of high workload. If the ping testing fails
when network traffic is heavy, verify the switch settings to ensure the ping testing is valid.
2. On the host, verify that the iSCSI adapter has been added.
NOTE: The iSCSI service on the iSCSI interface starts in vSphere when the storage system is powered up.

3. If you are using CHAP authentication, ensure that the CHAP security settings are correct for your system. See VMware
vSphere steps for configuring CHAP parameters for iSCSI adapters.

18 Setting up a host to use Unity VMware VMFS iSCSI datastores

 4
Setting up a host to use Unity VMware VMFS
FC datastores
Topics:
• Requirements for setting up a host to use Unity VMware VMFS datastores with FC
• Using multi-path management software with ESXi hosts
• Configuring ESXi host native failover
• Configuring the Unity VMware VMFS datastores for the host
• Manually configuring a Unity VMware VMFS datastore

Requirements for setting up a host to use Unity

VMware VMFS datastores with FC
Before you set up a host to use Unity VMware VMFS datastores, the Unity system and host and network requirements in
described this section must be met.
Unity automatically detects VMware ESXi hosts on the SAN. It is possible to add ESXi hosts manually, but letting the storage
system detect ESXi hosts automatically provides the highest level of functionality.

SAN requirements
For a host to connect to FC LUNs or VMware VMFS and Block VVol datastores on the Unity system, the host must be in a
SAN environment with the storage system, and zoned so that the host and the storage system are visible to each other over
the SAN. For a multi-pathing environment, each Unity FC LUN for the host must have two paths associated with it. These two
paths should be on different switches to ensure high availability.

Path management SAN requirements

When implementing a highly-available SAN between a host and the Unity system, keep in mind that:
● A LUN or VMware VMFS datastore is visible to both SPs.
● You can configure multiple paths for a LUN. These paths should be associated with separate physical ports on the same SP.
● Each LUN must present the same LUN ID to all hosts.
NOTE: Directly attaching a host to a storage system is supported if the host connects to both SPs and has the required
multipath software.

Using multi-path management software with ESXi

hosts
Multi-path management software manages the connections (paths) between the host and the Unity system to provide access
to the Unity storage should one of the paths fail. The following types of multi-path management software are available for an
ESXi host connected to a Unity system:
● ESXi native failover on any ESXi host
● EMC PowerPath/VE software on an ESXi 5.x or later host
For the supported versions of the PowerPath/VE software, refer to the Unity Support Matrix on the support website.

Setting up a host to use Unity VMware VMFS FC datastores 19

Setting up a Unity system for multi-path management software
For a Unity system to operate with hosts running multi-path management software, each FC LUN on the Unity system should be
associated with multiple paths.

Installing PowerPath
Steps
1. On the host or virtual machine, download the latest PowerPath version from the PowerPath software downloads section on
the Online Support website.
2. Install PowerPath as described in the appropriate PowerPath installation and administration guide for the host’s or virtual
machine’s operating system.
This guide is available on Online Support. If the host or virtual machine is running the most recent version and a patch exists
for this version, install it, as described in the readme file that accompanies the patch.
3. When the installation is complete, reboot the host or virtual machine.
4. When the host or virtual machine is back up, verify that the PowerPath service has started.

Configuring ESXi host native failover

ESXi hosts include native failover for managing the I/O paths between the server and storage system. Native failover provides
multiple paths from the server to the storage system. To use ESXi host native failover with your storage system, you
must implement one of the failover policies listed below. For more information about these policies, refer to VMware ESXi
configuration documentation.
● Round Robin (default)
● Fixed with failover mode
● Most Recently Used (MRU)

Configuring the native failover policy for FC connections

Steps
1. Log into VMware vSphere client as administrator.
2. From Hosts and Clusters, select the server.
3. Select Configure.
4. Under Storage, select Storage Devices and select the storage device from the list.
5. Under Properties and to the right of Multipathing Policies, select Edit Multipathing... which is listed under Actions.
The Edit Multipathing Policies dialog box appears.
6. For Path selection policy, verify that the selected policy is the one that you want:
● Fixed (VMware) for fixed native failover policy
● Round Robin (VMware) for Round Robin native failover policy
● Most Recently Used (VMware) for MRU native failover policy
If the policy is not set to the desired policy, in the policy selection dialog, select the correct policy.
7. If you selected the Fixed (VMware) policy, select the preferred path.
You can statically balance the load using the fixed policy by selecting different paths for each datastore. To designate a
different path as preferred, select the path from the list.
8. Click OK.

Next steps
You are now ready to either migrate a virtual machine to the VMFS datastore or create a virtual machine on the VMFS
datastore. To migrate a virtual disk to the VMFS datastore, see the section on Migrating VMware Virtual Machines to the Unity
System. For information about creating a virtual machine on the VMFS datastore, refer to the VMware documentation.

20 Setting up a host to use Unity VMware VMFS FC datastores

For FC connections, if you receive a connection error when the host is trying to log into an FC LUN, or you cannot see the
datastores on the target, you may be having problems with the SAN connection between the host and the storage system. This
problem may occur because:
● The Fibre Channel SAN is zoned incorrectly.
● A physical hardware issue is disrupting the SAN connectivity.
A rescan of the storage is required after any change is made to the SAN.

Configuring the Unity VMware VMFS datastores for

the host
Steps
1. Use Unisphere UI or CLI to:
a. Discover VMware ESXi hosts.
b. Create Unity VMFS datastores.
c. Assign host access during Unity VMFS datastore creation.
NOTE: If the datastore is created from Unisphere and granted host access during the creation (from either Unisphere
or the CLI), the datastore will automatically appear on the VMware side. In this case, a rescan for storage is not needed.
For more information about completing these tasks, refer to the Unisphere online help or the Unisphere CLI User Guide.
NOTE: When you create Unity VMFS datastores for discovered VMware ESXi hosts, the system automatically
configures the hosts to use the datastores. If you select multiple discovered hosts for the datastores, all the selected
hosts are configured automatically. The VMware VMFS datastores are presented directly to the ESXi hosts and not to
the hosts’ virtual machines. If an ESXi host cannot see the VMFS datastore after you create the datastore, manually
configure the connection to the VMFS datastore.

2. [Generic host objects only] Rescan for the VMFS datastores:

a. From Hosts and Clusters, select the server.
b. Select Configure.
c. Under Storage, select Storage Adapters.
i. Select the Fiber Channel storage adapter in the list of adapters.
ii. Click Rescan Storage ....

If the host can see the VMFS datastore, you must set up the host to use the datastore, as described in the next section.
If the host cannot see the VMFS datastore, there may be a problem with SAN connection between the host and the FC LUN
(FC connection), in which case you need to manually configure this connection.

Manually configuring a Unity VMware VMFS datastore

About this task
NOTE: If the VMware datastore is created in Unisphere, no additional action is required on the VMware side, the datastore
will appear automatically. If a LUN is provisioned to the ESXi host, a datastore must be manually created on the VMware
side.

Steps
1. Log in to the vSphere client as an administrator
2. Rescan for new storage devices:
a. From Hosts and Clusters, select the server.
b. Select the Configure tab.
c. Under Storage, click Storage Adapters.
i. Select the Fiber Channel adapter from the list of adapters.
ii. Select Rescan Storage....

Setting up a host to use Unity VMware VMFS FC datastores 21

3. Add each VMFS datastore to the ESXi host:
a. FromHosts and Clusters, select the host.
b. From the Actions drop down list, select Storage > New Datastore....
The New Datastore wizard appears.
c. In the New Datastore wizard, do the following:
i. Select VMFS as the datastore type.
ii. Specify a datastore name and a disk/LUN for provisioning the datastore.
iii. Specify the VMFS version for the datastore.
iv. Review the disk layout and specify the partition configuration details.
v. Review the datastore information, and click Finish.

Results
The Unity VMFS datastores are configured for the ESXi host.

22 Setting up a host to use Unity VMware VMFS FC datastores

 5
Setting up a host to use Unity vVol
datastores
Topics:
• Add the storage system as a VASA provider
• Configuring Unity File vVol datastores for the host
• Setting up the connection to a File vVol datastore
• Add an iSCSI target for Block vVol datastores
• Configuring the Unity Block vVol datastores for the host

Add the storage system as a VASA provider

About this task
Add the system as a VASA provider in vSphere.

Steps
1. In vSphere, go to Networking.
2. Select Configure.
3. Select Storage providers, then select the Add icon.
4. Enter the Name of the storage system. It is recommended that you use the same system name as Unisphere.
5. Enter the VASA provider URL for the Unity system. Use the following format: https://<management IP
address>:8443/vasa/version.xml .
6. Enter the Unisphere credentials and select OK.
NOTE: The credentials must be of a user that has either the Administrator or VMware Administrator role.

Next steps
It may take a few minutes for the registration to complete.

Configuring Unity File vVol datastores for the host

About this task
Use the Unisphere UI or CLI to:

Steps
1. Discover VMware ESXi hosts.
2. Create capability profiles, NAS protocol endpoint servers (vVols-enabled NAS servers), and File vVol datastores. You must
create a vVol-enabled NAS server.

Next steps
For more information on performing these tasks, refer to the Unisphere online help or Unisphere CLI User Guide.

Setting up a host to use Unity vVol datastores 23

Setting up the connection to a File vVol datastore
Prerequisites
The vVol datastore must already be created on the Unity system.
If the ESXi host cannot detect the storage system File vVol datastore, or if you are using generic host objects, you will need to
manually set up the connection.

Steps
1. Log into vSphere as an administrator.
2. For each File vVol datastore:
a. From Hosts and Clusters, select the host.
b. From the Actions drop down list, select Storage > New Datastore...
The New Datastore wizard appears.
c. In the New Datastore wizard, do the following:
● Select vVol as the datastore type.
● Specify the datastore name and select a backing storage container from the list of storage containers.
NOTE: Make sure to use the name that does not duplicate another datastore name in your data center
environment. If you mount the same vVols datastore to several hosts, the name of the datastore must be
consistent across all hosts.
● Select the hosts that require access to the datastore.
● Review the configuration options and click Finish.

Add an iSCSI target for Block vVol datastores

About this task
Add an iSCSI target in vSphere for SCSI Block vVol datastores.

Steps
1. From Hosts and Clusters, select the server.
2. Select Configure.
3. Under Storage, select Storage Adapters.
4. From the Storage Adapters panel, select the iSCSI software adapter.
5. In the details section of the panel, select Dynamic Discovery and click Add.
The Add Send Target Server dialog box appears.
6. Add the target’s information and click OK.

Configuring the Unity Block vVol datastores for the

host
Steps
1. [For iSCSI only:] Add the software iSCSI adapter, if not already added, as described in VMware vSphere documentation.
2. Use Unisphere UI or CLI to:
a. Discover VMware ESXi hosts.
b. Create Unity Block vVol datastores.
For more information about completing these tasks, refer to the Unisphere online help or the Unisphere CLI User Guide.
3. In vSphere, rescan for the VMFS datastores:
a. From Hosts and Clusters, select the server.
b. Select Configure, and under Storage, select Storage Adapters.

24 Setting up a host to use Unity vVol datastores

 For iSCSI:
i. Select the iSCSI storage adapter in the list of adapters.
ii. Select Rescan Storage....
For FC:
i. Select the Fiber Channel storage adapter in the list of adapters.
ii. Select Rescan Storage....

If the host can see the Block vVol datastore, you must set up the host to use the datastore, as described in the next section.
If the host cannot see the Block vVol datastore, you may have one of the following issues.
● iSCSI: A problem with the connection between the host and iSCSI target (iSCSI connection). Refer to iSCSI session
troubleshooting for ESXi hosts for additional steps to resolve the problem.
● FC: A problem with SAN connection between the host and the FC LUN (FC connection), in which case you need to
manually configure this connection.

Setting up a host to use Unity vVol datastores 25

 6
Migrating VMware Virtual Machines to the
Unity system
Topics:
• VMware virtual machine migration environment and limitations
• Migrating a virtual machine to a Unity datastore

VMware virtual machine migration environment and

limitations
The table below provides a high-level outline of the environments for suspended migration and vMotion migration. Refer to the
VMware documentation for more detailed information about migration limitations.

Table 1. Virtual machine migration environment and limitations

Component Requirement
Suspended Migration vMotion migration
Unity Datastore sized to accommodate the existing data that you are migrating and to
allow for data growth.
Hosts One or two ESXi hosts One or two ESXi hosts, each with:
● A vMotion license and configured for
vMotion.
● Access to both the source and target
datastores.
● Sufficient resources to support two
instances of the virtual machine
running concurrently for a brief time.
Virtual machines None. Virtual machines with snapshots cannot
be migrated.
Datastores ● Datastore is on either a local or ● Datastore is on either a local or
attached storage device and does attached storage device and must be
not need to be shared storage. shared storage.
● Entire datastore is migrated to the ● Entire datastore is migrated to the
Unity datastore. Unity datastore.
● Datastore is in persistent mode.

Table 2. Comparison of suspended migration versus vMotion migration of a virtual machine

Parameter Suspended Migration vMotion Migration
Graphic user interface (GUI) Provided by ESXi host Migrate Virtual Provided by ESXi host Migrate Virtual
Machine wizard. Machine wizard.
Access to virtual machine Disrupted relative to time required for No disruption.
the copying of the virtual machine to the
Unity datastore.

26 Migrating VMware Virtual Machines to the Unity system

Migrating a virtual machine to a Unity datastore
To migrate a virtual machine to a Unity datastore, perform these tasks:
1. Set up the host of the virtual machine migration.
2. Migrating a virtual machine with suspended migration or Migrating a virtual machine with Storage vMotion
NOTE: In Unisphere, the polling period for a VMware ESXi host or vCenter is once every 24 hours.

Migrating a virtual machine with suspended migration

Use the Migrate Virtual Machine wizard to migrate the datastore, as described in the VMware documentation for your ESX
Server.
After you click Finish in the wizard, the migration operation begins. During the migration operation, you have no access to the
virtual machine’s functions.

Migrating a virtual machine with Storage vMotion

Steps
1. In the vSphere client, set up VMkernel for vMotion:
a. From Hosts and Clusters, select the server.
b. Select Configure.
c. Under Networking, select Virtual Switches.
d. In the Virtual switches panel, click Add Networking....
e. Select VMkernel Network Adapter, and then click Next.
f. Do one of the following:
● Select an existing switch and go to the next step.
● Select to create a new switch, then select the network adapters for the virtual switch to use, and click Next.
g. Specify the network label, VLAN ID, IP settings, MTU, and which TCP/IP stack to use for the port group you are
creating.
h. From the list of Available services, select those Enabled services that apply, and then click Next.
i. Do one of the following for IPv4 settings:
● Select Obtain IP settings automatically and click Next.
● Use static IPv4 settings
NOTE: If you select Use static IPv4 settings, enter the IP settings and click Next.

j. On the summary page, verify the settings and then click Finish.
2. Under VMs, right-click the virtual machine that you want to migrate, select Migrate and click Next.
3. Proceed through the Migrate wizard until you reach the summary page..
4. On the summary page, verify the settings and then click Finish.

Migrating VMware Virtual Machines to the Unity system 27