PowerStore 3.0 Administration VMware Provisioning Participant Guide PDF PDF
PowerStore 3.0 Administration VMware Provisioning Participant Guide PDF PDF
0
ADMINISTRATION -
VMWARE PROVISIONING
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerStore 3.0 Administration - VMware Provisioning
Appendix 99
Introduction
VASA Support
Overview
VASA Sessions
Plugins
Plugin Description
vVols communication
Benefits:
Use storage profiles in vCenter, with configurable rules, to provision
virtual machines. Storage profile rules include usage tags, QoS priority,
and storage properties.
Reporting on existing vVols and related virtual machines in
PowerStore Manager without requiring continuous polling.
VM-level granularity, which offloads data services operations to the
PowerStore system. Data service operations include individual VM
snapshots, fast clones, and full clones.
iSCSI Connectivity
Verify that the ESXi host VMkernel adapter is associated with the iSCSI
Software Adapter, so that initiator and target have connectivity.
Open a vSphere Client session to the vCenter server that manages the
ESXi host. Go to the Hosts and Clusters section and select the ESXi
host. Then perform the following operations:
1. Expand the Storage section and select Storage Adapters.
2. Select the adapter under the iSCSI Software Adapter section.
3. Open the Network Port Binding tab.
4. Verify that the iSCSI VMkernel network adapter from the VMkernel
adapters page is listed. The Port Group Policy must be Compliant and
the Path Status Active, indicating that the initiator and target
connectivity is set. If not listed, the adapter must be added by selecting
Add.
iSCSI VMkernel network adapter vmk1 is associated with the iSCSI Software Adapter
vmhba65
Discover Targets
To discover the ESXi host initiator in the PowerStore cluster, enable the
ESXi host to discover the PowerStore iSCSI targets.
From the vSphere Web Client session to the vCenter Server > ESXi Host
Configure tab:
1. Open the Dynamic Discovery tab.
2. Click Add to open the Add Send Target Server dialog.
3. Type the Global Storage Discovery IP address, or the storage IP
address of one of the nodes of the Cluster appliance.
4. Click OK to close the Add Send Target Server dialog and save the
configuration.
5. The IP address is displayed in the list of iSCSI servers. Repeat to add
another target.
The Global Storage Discovery IP for Cluster1 is added for dynamic discovery
Paths
If iSCSI connectivity is set correctly, the paths between the initiator and
the iSCSI servers (targets) can be verified:
Select the Paths tab on the details information page of the adapter. If
no adapter is selected from the Storage adapters page, there is
nothing displayed on the bottom of the page.
The status of all paths should be active. The LUNs column is empty
because there is no provisioned volume presented to the ESXi host.
This example uses iSCSI. You can also add an NVMe host and attach a
volume in PowerStore and VMware.
Add Host
To add a host configuration, associate the host with one or more initiators
(iSCSI initiator, FC WWN, or NVMe initiator) and the Operating System.
Host Details
Follow the Add Host wizard to create the Host configuration, selecting
ESXi as the operating system.
Initiator Type
On the Initiator Type step, select the block storage protocol the host uses
to access provisioned storage.
iSCSI initiators are automatically discovered if the host has logged in
and connected to the PowerStore iSCSI targets.
If any appliance in the cluster has an FC embedded module, FC and
NVMe/FC initiators are automatically discovered. The cluster FC port
must be connected to a FC-based switch and zoned to the host FC
HBA. Click to see examples of the initiator step with FC and NVMe
selected.
An NVMe-vVol host type enables vVol support for ESXi hosts
connected to PowerStore using NVMe over Fibre Channel. ESXi must
be selected as the operating system for this option to be available.
Initiator Type steps of the Add Host wizard with iSCSI selected
Host Initiators
If the host identifier was not discovered, add it manually by clicking ADD
INITIATOR.
Host Connectivity
Summary
Click ADD HOST to start the job. The job starts in the background, and
PowerStore Manager displays a confirmation message when the host is
added.
ESXi Multipathing
Simulation:
Create an ESXi Host Configuration in
PowerStore.
Create a volume and then map it to an ESXi host so that VMFS datastores
can be created in the vSphere environment.
Select an ESXi host during the Create Volumes wizard, or add the host
later.
When the volume is created and mapped to an ESXi host, discover the
volume in the vSphere environment.
Open a session to the vCenter server that manages the ESXi host. Select
the ESXi host from the Hosts and Clusters section:
1. Select Storage Devices.
2. Open the Configure tab.
3. From the Actions menu, select Storage > Rescan Storage.
4. Keep the checkboxes marked and click OK to initiate the task.
Rescanning the iSCSI software adapter for new storage devices in vSphere Client
From the vSphere Web Client session, select the ESXi host under the
Hosts and Clusters section:
1. Open the Datastores tab.
2. From the Actions menu, select Storage > New Datastore to launch
the wizard.
3. Select VMFS Datastore as the type
4. Enter a name to identify the new datastore.
5. From the list of available storage devices, select the discovered
volume.
6. Next steps enable you to specify the VMFS version for the datastore
(VMFS 6 or VMFS 5) and the partition configuration. After reviewing
the configuration, start the creation process by clicking Finish.
Simulation:
Present a PowerStore Volume to an ESXi
Host.
Volume Properties
From Storage > Volumes, select the name of the volume that is
provisioned to the ESXi host.
Volume Performance
From the properties page of the volume that is mapped to the ESXi host:
1. Select the pencil icon on the right of the Volume name.
2. Increase the size of the volume. Shrinking of volume size is not
supported in PowerStore.
3. Click APPLY to save the changes. The slide-out panel closes and the
information at the capacity tab is updated.
Launch a vSphere Web Client session to the vCenter Server, and open
the Storage view from the menu.
VMware File Systems are designed to perform better than general file
systems for VMware workloads. PowerStore VMware File Systems are
intended to be used as NFS datastores in vSphere environments.
Supported Features:
Relevant plug-ins for VMware NFS use cases:
VAAI
VSI
AppSync
PowerStore VM awareness
The first step in the Create File System wizard is to select the type:
General or VMware File System.
VMware File System are only supported on NAS servers configured
with the NFS protocol.
VMware File Systems can only be created on NAS servers configured with
the NFS sharing protocol.
There are two ways to provision file systems using the PowerStore
Manager interface:
1. From the Storage menu, click the File System Add icon to launch the
Create File System wizard.
2. Select File Systems and click + CREATE on the File Systems page.
Associate the file system with a NAS server. The table identifies which
sharing protocols are enabled in each NAS server. Verify that the NAS
server has the NFS protocol enabled.
FS Details
Enter the file system details, including name, description, and size. The
size represents the quantity of storage that is subscribed for the file
system. The minimum is 3 GB, and the maximum is 256 TB. 1.5 GB per
file system is always allocated for metadata.
NFS Export
Optionally create an NFS export for the file system during file system
creation. The NFS export name must be unique at the NAS server level
per protocol. The NFS export name is combined with the NAS server IP
address to provide an NFS export path for the file system.
You can also assign NAS client access to an NFS export by selecting
MORE ACTIONS and Import Hosts. The option provides instructions on
how to create a CSV file with a list of hosts network addresses and access
types. The CSV file can be imported to the storage system.
1
Access is denied to user or client.
Protection Policy
Summary
Review the file system configuration on the Summary page. You may click
BACK to edit, or CREATE FILE SYSTEM to continue.
Host Access
Give the ESXi host access to the NFS export. Find the host IP address by
looking at the VMkernel adapters in vCenter.
From the File Systems page NFS Exports tab, select the NFS export and
MORE ACTIONS > Host Access to add a host. The host must have
read/write, allow root access.
With the ESXi host selected in vCenter Server, select ACTIONS >
Storage > New Datastore.
Select the NFS datastore type and version of NFS that was selected when
the file system was created.
Name the datastore and provide the paths to the NFS export:
1. Name: A name that identifies the new datastore
2. Folder: The NFS export
3. Server: The IP address of the NAS server interface
Ready to Complete
New Datastore
Select the Datastores tab from the top menu. The new NFS datastore is
listed.
Virtual Machines
PowerStore Manager displays details about the Virtual Machines and their
associated datastores. Go to Compute > Virtual Machines.
Click the name of the virtual machine to open its properties page.
Properties for NFS Virtual Machines are limited to the compute
performance. Snapshots, protection policies, and alerts that are available
for other objects are not available for NFS-based VMs.
From Storage > File Systems, select the name of the file system that is
provisioned to the ESXi host using an NFS export.
Launch a vSphere Web Client session to the vCenter Server, and open
the Storage view from the menu.
VMware File Systems are designed to perform better than general file
systems for VMware workloads. PowerStore VMware File Systems are
intended to be used as NFS datastores in vSphere environments.
Exported file systems are mounted as NFS datastores (only on
PowerStore T).
NFS datastore size can be increased or decreased on their
underlying exported and mounted file systems.
Workflow Steps
FC and NVMe/FC connectivity between the ESXi host and the PowerStore
system require that:
ESXi host has at least one HBA adapter that is installed and connected
to an FC-based switch.
Overview
Workflow Steps
Highlighted steps are related to provisioning storage for Virtual Volumes support
There are two ways to provision a storage container using the PowerStore
Manager interface:
Expand the Storage submenu, and click the Storage Containers Add
sign.
Or select Storage Containers and click CREATE on the Storage
Containers page.
Define Quota
Availability
Workflow Steps
From the vSphere Web Client session, select the ESXi host under the
Hosts and Clusters section:
1. Expand the Storage section and select Storage > New Datastore.
2. Select vVol as the type of datastore.
3. Enter a name for the new datastore, and select a storage container
from the list of discovered storage devices. The example shows the
default container and storage container recently added to the
PowerStore cluster.
4. After reviewing the configuration, start the creation process by clicking
FINISH.
The vVol datastore is mounted to the ESXi host and is ready to store
virtual machines and their vVols.
Protocol Endpoints
SCSI PEs are like LUN mount points that allow I/O access to vVols from
the ESXi host to the storage system.
The block vVol is bound to the associated SCSI PE every time that the
VM is powered on.
When the VM is powered off, the PE is unbound.
From the vSphere Web Client session, open the Hosts and Clusters view
and select the ESXi host from the left panel:
1. Open the Configure tab.
2. Select the Protocol Endpoints option under Storage.
3. Verify that the established data paths with the PowerStore storage
container are displayed.
SCSI PEs are created for every ESXi host-to-vVol datastore (storage container)
established connection.
Workflow Steps
With the vVol datastore created, create a Virtual Machine storage policy.
Provision VMs by selecting the storage policy and using a compatible vVol
datastore. Storage policies ensure that the datastore has the appropriate
configuration for the VM.
VM Storage Profiles
Policy Structure
On the Policy Structure page, select Enable rules for Dell EMC
PowerStore storage in the Datastore specific rules section.
PowerStore Rules
Storage Compatibility
The next step shows all the available mounted compatible datastores.
Workflow Steps
To create a virtual machine on the vVol datastore, select the ESXi host
under Hosts and Clusters. Select Actions > New Virtual Machine.
Enter a name for the new virtual machine, and select the datacenter and
folder where to place the new VM.
Compute Resource
Select the ESXi host where the virtual machine must be placed, and
advance to the next step.
Select a host
Select Storage
Select Compatibility
Select a Guest OS
Customize Hardware
Customize Hardware
Finish
Ready to complete
Power On VM
1. From the left panel, select the virtual machine that was created.
2. Power on the virtual machine using the menu tools.
Power on new VM
Virtual Machines
PowerStore discovers the details about VMs that are stored in the
datastores and displays them in PowerStore Manager. This feature is
available for all VMs created on provisioned PowerStore storage, including
VMFS, NFS, and vVol datastore types.
Virtual Volumes
PowerStore discovers the details about the vVols and displays them in
PowerStore Manager.
Storage Containers
List of vVols
Select the name of the storage container that is provisioned to the ESXi
host using VASA support.
Select the VIRTUAL VOLUMES card and select one or more vVols:
GATHER SUPPORT MATERIALS for troubleshooting.
From Storage > Storage Containers, select the name of the storage
container that is provisioned to the ESXi. Select any of the cards to see
details.
From the properties page of the storage container that is attached to the
ESXi host:
1. Select the pencil icon next to the storage container name.
2. Change the value of the Container Quota. In the example, the storage
container quota was increased.
a. A high water mark defines the percentage used that triggers an
alert.
3. Click APPLY to save the changes.
Launch a vSphere Web Client session to the vCenter Server, and open
the Storage view from the menu.
On the General page, click REFRESH on the Capacity section. The vVol
datastore capacity reflects the change to the PowerStore storage
container size.
VM Migration Overview
Storage Containers
Migrating VM Storage
From the vSphere Web Client session, select the ESXi host under the
Hosts and Clusters section.
The storage that is associated with the virtual machine shows as modified.
In the example, virtual machine is migrated from VVol_Datastore06 to
VVol_Datastore02.
Placement
The migrated VM and its associated vVols exist in the destination storage
container. From the virtual machine properties, select the VIRTUAL
VOLUMES card. All virtual machine volumes including snapshots are
moved during Storage vMotion operations.
In the example, the VMs and their vVols that were once stored in storage
container VVOL_SC06 in Cluster1 are now in storage container
VVOL_SC02 in Cluster2.
For policies that include a replication rule, only the snapshot schedule is
used. Replication is not supported for virtual machines.
About VM Migration
Migration uses the system bond over the cluster network to migrate the
vVols. The migration session replicates the source vVol and its snapshots
to the destination appliance. After the initial synchronization, the
replication process performs the last delta copy of the vVol.
PowerStore and the ESXi hosts nondisruptively cut over to the migrated
vVol.
Select VM
Verification
PowerStore verifies that there are no issues with the proposed migration.
Select Appliance
Summary
The summary screen displays details about the process that is about to be
started.
Recommended knowledge base article with detailed use cases and
limitations to be reviewed before starting the process.
Notification that the virtual machine and any associated thin clones and
snapshots are also migrated.
Notification that the migration process takes some time.
Review the Summary information. Click BACK if edits are required. Select
whether the migration should start immediately or defer it until later.
VM migration summary
Internal Migrations
Before removing a storage container, the VMs and vVols that are stored in
it must be migrated to another storage. Then unmount the vVol datastore
from the ESXi host in the vSphere environment, and remove the storage
container in PowerStore Manager.
vSphere
From the vSphere Web Client session, select the ESXi host under the
Hosts and Clusters section to unmount the vVol datastore:
1. Click Datastores.
2. Click the name of the datastore to unmount.
3. Click VMs. Verify that the datastore does not contain any virtual
machines.
4. From the Actions menu, select Unmount Datastore.
5. In the Unmount Datastore window, check the box next to each host
that has the datastore mounted. Click OK.
PowerStore Manager
PowerStore T
The page shows that there is a vCenter Server that is connected to the
storage system that is Configured and Online.
If PowerStore will not be used for vVol support at any time soon, consider
also unregistering it as a VASA storage provider in vCenter server. To
manually remove a PowerStore T system from the list of VASA storage
providers, launch a web client session to the vCenter Server. Then open
the Hosts and Clusters view.
Select the vCenter server on the left pane and open the Configure tab.
From the Configure page:
1. Select the Storage Providers option from the submenu.
2. Select the VASA provider record to exclude.
3. Click Remove on the top menu.
4. Click YES to confirm the exclusion of the PowerStore cluster. The
dialog box is closed and the VASA record is eliminated from the list.
PowerStore X
To monitor the VMs and its vVols in PSM, go to Compute > Virtual
Machines.
Click the virtual machine to open its properties.
To view the vVols associated with the virtual machine, open the
Virtual Volumes card. A list of vVols created with the VM is
displayed.
From the vSphere Web Client session on the vCenter Server, ESXi Host
Configure tab:
1. Expand the Networking section and select VMkernel adapters.
a. The default vmk0 adapter is used for the Management Network.
b. The list of adapters must include another adapter with an IP
address on the iSCSI network and be associated with a different
virtual switch.
2. Select the adapter.
3. Verify that the IPv4 settings of the iSCSI VMkernel network adapter are
properly configured.
The VMkernel network adapter vmk1 is associated with the virtual switch vSwitch1
Before the ESXi host can connect to PowerStore using NVMe over TCP,
add the Software Adapter to the list of Storage Adapters in vSphere Client.
The process is similar to adding the iSCSI Software Adapter to a new
ESXi host.
Add Controller
Add Controller
In the PowerStore Manager Add Host wizard, select the NVMe initiator for
the ESXi host.
Host Added
The new ESXi host is shown in the list of hosts on PowerStore Manager.
In vSphere, refresh the NVMe over TCP Storage Adapter. The new disk
appears under Devices.
Recommended configuration:
Use two separate fabrics.
For resiliency, each fabric should be on a different physical FC
switch.
Zone each host to both nodes of each appliance.
Zoning must be done using the appropriate WWN. PowerStore
exposes two WWNs, one for FC (SCSI WWN) and one for NVMe
(NVMe WWN).
Use PowerStore SCSI WWN for Fibre Channel SAN.
Use PowerStore NVMe WWN for NVMe/FC.
To locate the correct WWN, use the PSTCLI fc_port show
command or the Fibre Channel Ports page in PowerStore Manager
Locate correct FC WWN in Hardware > Appliance > Ports > Fibre Channel
Initiator Type steps of the add host wizard with Fibre Channel (FC) selected
Initiator Type steps of the add host wizard with NVMe selected
NAS Servers
Click the NAS server to show its properties. Settings that must be
configured are available on the NAMING SERVICES and SHARING
PROTOCOLS tabs, including:
Enabling DNS services
Configuring naming services with UNIX Directory Services (LDAP/NIS)
or local files
Defining the supported NFS protocol versions
DNS
NIS
LDAP
Note: Enable either NIS or LDAP services. The LDAP configuration must
adhere to either the Active Directory, RFC 2307, RFC 2307bis, or iPlanet
schemas. If not, LDAP does not function properly.
Local Files
Local files can be used instead of, or in addition to, DNS, LDAP, and NIS
directory services. To configure naming services with local files, select
NAMING SERVICES and the LOCAL FILES option. Complete the form
and click APPLY to save the configuration.
1. Download the template using the icon next to the file type.
a. Passwd resolves usernames to User IDs.
PowerStore also supports the combination of local files and NIS, or LDAP
for naming services. If combined with other naming services, the storage
system queries the uploaded local files first.
Sharing Protocols
Considerations:
DNS and NTP must be configured.
UNIX Directory Service must be configured.
VM awareness No Yes
FS_BLOCKIO_NOT_MATCH_ALLOCATON_SIZE:
File system %(fsname) in NAS server %(vdmname)
I/O patterns do not match the allocation size
(%(actualSize) bytes) of the file system. The
suggested allocation unit size is %(suggested Size)
bytes
FS_BLOCKIO_NOT_ALIGNED:
File system %(fsname) in NAS server %(vdmname) I/O
patterns are not aligned with the allocation size
(%(actualSize) bytes) of the file system.
vCenter Server with highlighted VMkernel adapter configured for ESXi host access
Add Host wizard showing NVMe-vVol initiator type for ESXi host
NVMe/FC initiators
On the Select Host's Initiators screen, check the boxes for the initiators
to associate with the host.
A new Initiator Type column is displayed on the Host & Host Groups
page.
Identify which hosts have NVMe-vVol initiators by looking at the
column.
Create Storage Container panel with Select the storage protocol option
Storage Container
A storage container is a pool of raw storage capacity or an aggregation of
storage capabilities that a cluster can provide to virtual volumes (vVols).