Contents

Dell VxBlock 350 Converged Infrastructure Reference Guide PDF

1 of 28
1 of 28

Summary of Content for Dell VxBlock 350 Converged Infrastructure Reference Guide PDF

Dell Workflow Automation Reference Guide

May 2022 Rev. 2.2

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.

2019- 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Revision history..........................................................................................................................................................................5

Chapter 1: Introduction................................................................................................................. 7

Chapter 2: Workflow automation library........................................................................................ 8

Chapter 3: Compute/host management ...................................................................................... 10 Compute capacity expansion.......................................................................................................................................... 10

Provision ESXi cluster - PowerMax/VMAX...........................................................................................................10 Provision ESXi cluster - PowerStore....................................................................................................................... 11 Provision ESXi cluster - Unity.................................................................................................................................... 11 Provision ESXi cluster - XtremIO.............................................................................................................................. 11 Provision ESXi hosts - SD boot................................................................................................................................ 12 Provision ESXi hosts - PowerMax/VMAX, PowerStore, Unity, and XtremIO boot.....................................12 Provision ESXi hosts - M.2 boot.............................................................................................................................. 13 Move an ESXi host from cluster to cluster............................................................................................................13 Remove ESXi host from production cluster.......................................................................................................... 13 Decommission the ESXi host from vCenter.......................................................................................................... 13 Create new service profile template....................................................................................................................... 14 Provision bare metal server....................................................................................................................................... 14 Provision bare metal server - Cisco UCS............................................................................................................... 14 Add host to vSphere cluster......................................................................................................................................14

Host management..............................................................................................................................................................14 Create VMFS datastore cluster with configuration.............................................................................................14 Add VMFS datastore to datastore cluster.............................................................................................................15 Remove VMFS datastore from datastore cluster................................................................................................ 15 Create Virtual Distributed Switch............................................................................................................................ 15

Chapter 4: Storage management..................................................................................................16 PowerMax/VMAX..............................................................................................................................................................16

Create storage volume and VMFS datastore for ESXi host/cluster............................................................... 16 Expand the storage volume and increase VMFS capacity of existing datastore ........................................ 16 Remove VMFS datastore and associated storage volume.................................................................................17 Delete VMFS datastore and associated storage volume....................................................................................17 Add datastore to existing ESXi cluster................................................................................................................... 17 Create new volume and datastore; move VMs to new datastore ...................................................................17 Create new volume and attach RDM disks to VM............................................................................................... 18 Delete block volume.....................................................................................................................................................18 Expand block volume...................................................................................................................................................18

PowerStore..........................................................................................................................................................................18 Create volume and VMFS datastore for ESXi host/cluster.............................................................................. 18 Expand the volume and increase VMFS capacity of existing datastore ........................................................18 Remove VMFS datastore and associated volume................................................................................................19 Delete VMFS datastore and associated volume................................................................................................... 19

Dell Unity and Dell Unity XT............................................................................................................................................ 19

Contents

Contents 3

Create LUN volume and VMFS datastore for ESXi host/cluster.....................................................................19 Expand the LUN and increase VMFS capacity of existing datastore ............................................................ 19 Remove VMFS datastore and associated LUN....................................................................................................20 Delete VMFS datastore and associated LUN....................................................................................................... 20 Add datastore to existing ESXi cluster.................................................................................................................. 20 Create new LUN and datastore; move VMs to new datastore .......................................................................20 Create new LUN and attach RDM disks to VM................................................................................................... 20

XtremIO................................................................................................................................................................................ 21 Create new LUN and VMFS datastore for ESXi host/cluster.......................................................................... 21 Expand the LUN and increase VMFS capacity to existing datastore ............................................................ 21 Remove VMFS datastore and associated LUN.....................................................................................................21 Delete VMFS datastore and associated LUN........................................................................................................21 Add datastore to existing ESXi cluster.................................................................................................................. 22 Create new LUN and datastore; move VMs to new datastore .......................................................................22 Create new LUN and attach RDM disks to VM................................................................................................... 22

Chapter 5: Snapshot management...............................................................................................23 PowerMax/VMAX.............................................................................................................................................................23

Create snapshot of storage group.......................................................................................................................... 23 Rename snapshot of storage group........................................................................................................................23 Delete snapshot of storage group...........................................................................................................................23

Dell Unity and Dell Unity XT............................................................................................................................................23 Create snapshot of block LUN.................................................................................................................................23 Export snapshot of block LUN to host...................................................................................................................24 Delete snapshot of block LUN..................................................................................................................................24

Chapter 6: Provision ESXi hosts - PowerStore boot.................................................................... 25

Chapter 7: Provision ESXi hosts - PowerStore.............................................................................28

4 Contents

Revision history

Date Document revision Description of changes

May 2022 2.2 New workflows in 22-04.1: Provision ESXi hosts - M.2 boot

December 2021 2.1 Content generalized for both VxBlock Central and CMS.

June 2021 2.0 New workflows in 21-06.1: Provision ESXi cluster - PowerStore Create volume and VMFS datastore for ESXi cluster/host Expand volume and increase VMFS capacity of existing datastore Remove VMFS datastore and associated volume Delete VMFS datastore and associated volume

Enhanced workflows in 21-06.1: Rollback capability for Provision ESXi hosts - PowerStore boot Added PowerStore to Provision ESXi hosts - SD boot Added PowerStore to Provision bare metal server

March 2021 1.9 New workflows in 21-03.1: Provision ESXi hosts - PowerStore boot

Enhanced workflows in 21-03.1: The following workflows were updated to support VMware vSphere

7.0: Provision ESXi cluster - PowerMax/VMAX Provision ESXi cluster - Unity Provision ESXi cluster - XtremIO Provision ESXi hosts - SD boot Provision ESXi hosts - PowerMax/VMAX, PowerStore, Unity, and

XtremIO

May 2020 1.8 New workflows in 20-05.1: Decommission ESXi host from vCenter

Enhanced workflows in 20-05.1: Rollback capability for Provision ESXi hosts - Unity boot

April 2020 1.7 New workflows in 20-04.1: Provision ESXi cluster - XtremIO Move an ESXi host from cluster to cluster

Enhanced workflows in 20-04.1: Rollback capability for Provision ESXi hosts - PowerMax/VMAX

Updated titles to match tiles in VMware vRealize Orchestrator.

March 2020 1.6 New workflows in 20-03.1: Provision ESXi cluster - Unity Create snapshot of block LUN for Dell Unity and Dell Unity XT Export snapshot of block LUN to host for Dell Unity and Dell Unity XT Delete snapshot of block LUN for Dell Unity and Dell Unity XT

February 2020 1.5 New workflows in 20-02.1: Expand LUN and increase VMFS capacity of existing datastore for Dell

Unity, Dell Unity XT, and XtremIO

Revision history 5

Date Document revision Description of changes

Remove VMFS datastore and associated LUN for Dell Unity, Dell Unity XT, and XtremIO

Delete VMFS datastore and associated LUN for Dell Unity, Dell Unity XT, and XtremIO

Add LUN datastore to existing ESXi cluster for Dell Unity, Dell Unity XT, and XtremIO

January 2020 1.4 New workflows in 20-01.1: Provision ESXi cluster - PowerMax/VMAX Remove ESXI host from production cluster Create a new LUN and datastore and move VMs to new datastore Create new volume and attach RDM disks to VM for PowerMax/

VMAX Create new LUN and attach RDM disks to VM for Dell Unity, Dell Unity

XT, and XtremIO

Enhanced workflows in 20-01.1: Provision host (bare metal) - PowerMax/VMAX/Unity/XtremIO

December 2019 1.3 New workflows in 19-12.1: Create VDS and default port groups Create a new volume and datastore and move VMs to new datastore Delete block volume(s) Expand block volume(s)

November 2019 1.2 New workflows in 19-11.1: Add PowerMAX/VMAX datastore to existing ESXi cluster Create snapshot of storage group - PowerMax/VMAX Rename snapshot of storage group - PowerMax/VMAX Delete snapshot of storage group - PowerMax/VMAX

Updated workflows in 19-11.1: Create storage volume and VMFS datastore for ESXi cluster/host Added Dell Unity XT to all workflows that support Dell Unity.

October 2019 1.1 New workflows in 19-10.1: Create VMFS datastore cluster with configuration Add VMFS datastore to datastore cluster Remove VMFS datastore from datastore cluster Create storage volume and VMFS datastore for ESXi cluster/host Expand storage volume and increase VMFS capacity of existing

datastore Remove VMFS datastore and associated storage volume Delete VMFS datastore and associated storage volume

September 2019 1.0 Initial release

6 Revision history

Introduction This guide provides an overview of the Workflow Automation library with a detailed description of the automated steps for each workflow.

Workflow Automation enables you to use automated workflows to deploy and configure your Converged System across compute, storage, and network layers in both physical and virtual environments. Workflow Automation reduces administration overhead by providing a library of engineered workflows that enables an administrator to deliver services quickly at a lower cost, while improving operational efficiency. Workflows are developed to integrate with VMware vRealize Orchestrator to keep the operating environment simple, extensible, and consistent. The workflows are regularly updated with the most up-to-date software and firmware versions, which eliminates challenges in lifecycle management and maintenance.

Workflow Automation is available as an optional orchestration module. After Workflow Automation is entitled, you can access the software package from the Download Center.

The Workflow Automation library is expanded with new workflows on a regular cadence. On the Download Center, the filenames indicate the year, month, and day a new workflow package is published.

For custom requirements of Workflow Automation, contact your Dell Account Manager.

The target audience for this document includes customers using the Workflow Automation feature with VxBlock Central or Converged Management Software.

The Glossary provides terms, definitions, and acronyms that are related to Dell Technologies.

1

Introduction 7

Workflow automation library

Compute/Host management workflows Supported systems

Provision ESXi hosts - SD boot VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Provision ESXi hosts - PowerMax/VMAX boot

NOTE: The fulfillment workflow has the rollback feature.

VxBlock and Vblock 740 and VxBlock 1000

Provision ESXi hosts - PowerStore boot

NOTE: The fulfillment workflow has the rollback feature.

VxBlock 1000

Provision ESXi hosts - XtremIO boot VxBlock and Vblock 540 and VxBlock 1000

Provision ESXi hosts - Unity boot

NOTE: The fulfillment workflow has the rollback feature.

VxBlock and Vblock 350 and VxBlock 1000

Provision ESXi hosts - M.2 boot VxBlock 1000

Create service profile template VxBlock and Vblock 350, 540, 740 and VxBlock 1000

Provision bare metal server VxBlock and Vblock 350, 540, 740 and VxBlock 1000

Provision bare metal server - Cisco UCS VxBlock and Vblock 740 and VxBlock 1000

Add host to vSphere cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Create VMFS datastore cluster with configuration VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Add VMFS datastore to datastore cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Remove VMFS datastore from datastore cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Create Virtual Distributed Switch VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Provision ESXi cluster - PowerMax/VMAX VxBlock and Vblock 740 and VxBlock 1000

Provision ESXi cluster - PowerStore VxBlock 1000

Provision ESXi cluster - Unity VxBlock and Vblock 350 and VxBlock 1000

Provision ESXi cluster - XtremIO VxBlock and Vblock 540 and VxBlock 1000

Move an ESXI host from cluster to cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Remove ESXI host from production cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Decommission ESXi host from vCenter VxBlock and Vblock 350, 540, and VxBlock 1000

Storage management workflows Supported systems

Create storage volume and VMFS datastore for ESXi host/cluster VxBlock and Vblock 740 and VxBlock 1000

Create volume and VMFS datastore for ESXi host/cluster VxBlock 1000

Create LUN and VMFS datastore for ESXi cluster/host VxBlock and Vblock 350, 540, and VxBlock 1000

2

8 Workflow automation library

Storage management workflows Supported systems

Expand storage volume and increase VMFS capacity of existing datastore

VxBlock and Vblock 740 and VxBlock 1000

Expand volume and increase VMFS capacity of existing datastore VxBlock 1000

Expand LUN and increase VMFS capacity of existing datastore VxBlock and Vblock 350, 540, and VxBlock 1000

Remove VMFS datastore and associated storage volume VxBlock and Vblock 740 and VxBlock 1000

Remove VMFS datastore and associated volume VxBlock 1000

Remove VMFS datastore and associated LUN VxBlock and Vblock 350, 540, and VxBlock 1000

Delete VMFS datastore and associated storage volume VxBlock and Vblock 740 and VxBlock 1000

Delete VMFS datastore and associated volume VxBlock 1000

Delete VMFS datastore and associated LUN VxBlock and Vblock 350, 540, and VxBlock 1000

Add datastore to existing ESXi cluster VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Create a new LUN and datastore; move VMs to new datastore VxBlock and Vblock 350, 540, and VxBlock 1000

Create a new volume and datastore; move VMs to new datastore VxBlock and Vblock 740 and VxBlock 1000

Delete block volume VxBlock and Vblock 740 and VxBlock 1000

Expand block volume VxBlock and Vblock 740 and VxBlock 1000

Create new volume and attach RDM disks to VM VxBlock and Vblock 740 and VxBlock 1000

Create new LUN and attach RDM disks to VM VxBlock and Vblock 350, 540, 740, and VxBlock 1000

Snapshot management workflows Supported systems

Create snapshot of storage group VxBlock and Vblock 740 and VxBlock 1000

Rename snapshot of storage group VxBlock and Vblock 740 and VxBlock 1000

Delete snapshot of storage group VxBlock and Vblock 740 and VxBlock 1000

Create snapshot of block LUN VxBlock and Vblock 350 and VxBlock 1000

Export snapshot of block LUN to host VxBlock and Vblock 350 and VxBlock 1000

Delete snapshot of block LUN VxBlock and Vblock 350 and VxBlock 1000

Workflow automation library 9

Compute/host management

Compute capacity expansion Workflow Automation reduces the time spent completing compute capacity expansions on Converged Systems by eliminating the manual steps and the number of tools required.

The following figure is an example of the steps automated by the Provision ESXi hosts workflows:

Provision ESXi cluster - PowerMax/VMAX

This workflow provisions a new cluster of hosts, installs VMware ESXi, and adds the newly created cluster to the VMware vCenter database. The workflow also provisions storage capacity to the newly provisioned cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Create and apply a service profile from a service profile template. 3. Configure the zoning on the SAN switches. 4. Provision the boot LUN from the storage array. 5. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 6. Install VMware ESXi.

3

10 Compute/host management

7. Set up the VMware vCenter cluster. 8. Add the hosts to the new VMware ESXi cluster. 9. Configure the Virtual Distributed Switch (VDS). 10. Add the hosts to the new VDS. 11. Create port groups for the new VDS. 12. Create a storage volume. 13. Provision a datastore to the new host cluster.

Provision ESXi cluster - PowerStore

This workflow provisions a new cluster of hosts, installs VMware ESXi, and adds the newly created cluster to the VMware vCenter database. The workflow also provisions storage capacity to the newly provisioned cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Create and apply a service profile from a service profile template. 3. Configure the zoning on the SAN switches. 4. Provision the boot LUN from the storage array. 5. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 6. Install VMware ESXi. 7. Set up the VMware vCenter cluster. 8. Add the hosts to the new VMware ESXi cluster. 9. Configure the Virtual Distributed Switch (VDS). 10. Add the hosts to the new VDS. 11. Create port groups for the new VDS. 12. Create a volume. 13. Provision a datastore to the new host cluster.

Provision ESXi cluster - Unity

This workflow provisions a new cluster of hosts, installs VMware ESXi, and adds the newly created cluster to the VMware vCenter database. The workflow also provisions storage capacity to the newly provisioned cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Create and apply a service profile from a service profile template. 3. Configure the zoning on the SAN switches. 4. Provision the boot LUN from the storage array. 5. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 6. Install VMware ESXi. 7. Set up the VMware vCenter cluster. 8. Add the hosts to the new VMware ESXi cluster. 9. Configure the Virtual Distributed Switch (VDS). 10. Add the hosts to the new VDS. 11. Create port groups for the new VDS. 12. Create a LUN. 13. Provision a datastore to the new host cluster.

Provision ESXi cluster - XtremIO

This workflow provisions a new cluster of hosts, installs VMware ESXi, and adds the newly created cluster to the VMware vCenter database. The workflow also provisions storage capacity to the newly provisioned cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Create and apply a service profile from a service profile template. 3. Configure the zoning on the SAN switches.

Compute/host management 11

4. Provision the boot LUN from the storage array. 5. Install VMware ESXi. 6. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 7. Set up the VMware vCenter cluster. 8. Add the hosts to the new VMware ESXi cluster. 9. Configure the Virtual Distributed Switch (VDS). 10. Add the hosts to the new VDS. 11. Create port groups for the new VDS. 12. Create a LUN. 13. Provision a datastore to the new host cluster.

Provision ESXi hosts - SD boot

This workflow helps you expand the compute capacity of your Converged System by provisioning Cisco UCS servers using the SD card, installing VMware ESXi, and adding the servers to an existing host cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Identify a service profile template in use by the existing service. 3. Create and apply a service profile from a service profile template. 4. Configure the zoning on the SAN switches. 5. Power on the physical servers. 6. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 7. Install VMware ESXi on the SD card. 8. Add the servers to the existing VMware ESXi cluster. 9. Assign the cluster datastores to the newly provisioned servers. 10. Add the host to the VDS and complete the network configuration. 11. Schedule an RCM scan.

Provision ESXi hosts - PowerMax/VMAX, PowerStore, Unity, and XtremIO boot

These workflows help you expand the compute capacity of your Converged System by provisioning Cisco UCS servers using the Boot LUN of the storage array, installing VMware ESXi, and adding the servers to an existing host cluster.

The following workflows are available in VMware vRO: Provision ESXi hosts - PowerMax/VMAX Boot with rollback feature Provision ESXi hosts - Unity Boot with rollback feature Provision ESXi hosts - PowerStore Boot with rollback feature

NOTE: These workflows have the rollback feature that allows you to undo changes to the MDS, storage array, host

configuration, and service profile information. You can access the rollback feature through the fulfillment workflow.

Provision ESXi hosts - XtremIO Boot

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Identify a service profile template in use by the existing service. 3. Create and apply a service profile from a service profile template. 4. Configure the zoning on the SAN switches. 5. Provision the Boot LUN from the storage array. 6. Power on the physical servers. 7. Select legacy boot for VMware vSphere 6.7 or UEFI boot for VMware 7.0. 8. Install the VMware ESXi. 9. Add the servers to the existing VMware ESXi cluster. 10. Assign the cluster datastores to the newly provisioned servers. 11. Add the host to the VDS and complete the network configuration. 12. Schedule an RCM scan.

12 Compute/host management

Provision ESXi hosts - M.2 boot

This workflow helps you expand the compute capacity of your Converged System by provisioning Cisco UCS servers using M.2 boot, installing VMware ESXi, and adding the servers to an existing host cluster.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and validate the data. 2. Identify a service profile template in use by the existing service. 3. Create and apply a service profile from a service profile template. 4. Configure the zoning on the SAN switches. 5. Provision the Boot LUN from the storage array. 6. Power on the physical servers. 7. Install the VMware ESXi. 8. Add the servers to the existing VMware ESXi cluster. 9. Assign the cluster datastores to the newly provisioned servers. 10. Add the host to the VDS and complete the network configuration. 11. Schedule an RCM scan.

Move an ESXi host from cluster to cluster

This workflow helps you move an existing VMware ESXi host from one cluster to another, attaches the host to the VDS, and maps the host to a datastore in the other cluster.

The following manual steps are automated by this workflow: 1. Place the VMware ESXi host in maintenance mode. 2. Remove the host from VMware vSphere cluster. 3. Power down the host. 4. Remove the host from zoning group. 5. Remove the service profile from the host. 6. Assign a service profile to the host. 7. Add host to zoning group. 8. Power on the host. 9. Add the host to VMware vSphere cluster. 10. Remove host from maintenance mode.

Remove ESXi host from production cluster

This workflow helps you remove an existing VMware ESXi host from the production cluster and places the host in maintenance mode.

The following manual steps are automated by this workflow: 1. Remove VMware ESXi host from production vCenter. 2. Validate if DRS is enabled. 3. Place host in maintenance mode. 4. Verify the virtual machines successfully migrated to the available hosts. 5. Verify the hosts were placed in maintenance mode.

Decommission the ESXi host from vCenter

This workflow helps you decommission an existing VMware ESXi host from VMware vCenter, which includes detaching the host from the VDS, unmapping the datastores, removing the ESXi host from the vCenter, cleaning up the storage and MDS, and deleting the storage profile from UCSM.

The following manual steps are automated by this workflow: 1. Place the VMware ESXi host in maintenance mode. 2. Remove the host from VMware vSphere cluster. 3. Power down the host.

Compute/host management 13

4. Remove the host from zoning group. 5. Remove the service profile from the host.

Create new service profile template

This workflow creates a service profile template you can use in the provisioning of a new VMware ESXi cluster.

The following manual steps are automated by this workflow: 1. Set the profile name and type. 2. Set the vNICs template and adapter policy. 3. Set the vHBAs template and adapter policy. 4. Assign the vNICs and vHBAs to servers. 5. Establish boot, maintenance, and operational policies.

Provision bare metal server

This workflow helps you provision the compute capacity for bare metal Cisco UCS servers in your Converged System using the Boot LUN from the storage array.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and carry out data validation. 2. Identify a service profile template in use by the existing service. 3. Create and apply service profile from service profile template. 4. Configure the zoning on the SAN switches. 5. Provision the Boot LUN from the storage array. 6. Power on the physical servers.

Provision bare metal server - Cisco UCS

This workflow helps you expand the compute capacity of a bare metal Converged System by provisioning Cisco UCS servers.

The following manual steps are automated by this workflow: 1. Determine the available resources (servers) and carry out data validation. 2. Identify a service profile template in use by the existing service. 3. Create and apply service profile from service profile template. 4. Power on the physical servers.

Add host to vSphere cluster

This workflow helps you add a provisioned Cisco UCS server to a VMware vSphere cluster.

The following manual steps are automated by this workflow: 1. Add the host to a cluster. 2. Place the host in maintenance mode.

Host management Workflow Automation provides automated workflows for administrators to easily create, delete, and manage VMware vCenter datastore clusters.

Create VMFS datastore cluster with configuration

This workflow creates and configures a VMFS datastore cluster in VMware vCenter.

The following manual steps are automated by this workflow: 1. Configure the Storage DRS.

14 Compute/host management

2. Configure the Storage DRS rules. 3. Configure Manual or Automation mode. 4. Configure I/O metrics for the VMFS datastore cluster. 5. Configure the space and latency threshold.

Add VMFS datastore to datastore cluster

This workflow helps add existing VMFS datastores to a VMware vCenter datastore cluster.

The following manual process is automated by this workflow: Add multiple existing VMFS datastores to a VMware vCenter datastore cluster.

Remove VMFS datastore from datastore cluster

This workflow helps you remove multiple VMFS datastores from an existing VMware vCenter datastore cluster.

The following manual process is automated by this workflow: Remove multiple VMFS datastores from the VMware vCenter datastore cluster.

Create Virtual Distributed Switch

This workflow creates a Virtual Distributed Switch (VDS) with a default port group using the user provided VLAN ID in the specified network folder.

The following manual steps are automated by this workflow: 1. Create VDS. 2. Create VDS port group.

Compute/host management 15

Storage management The storage management and administration workflows eliminate manual and repetitive tasks, which helps the operations teams rapidly provision storage resources to respond to the needs of the business.

The following figure is an example of the steps automated by the Create storage volume and VMFS datastore for ESXi cluster/host workflow:

PowerMax/VMAX

Create storage volume and VMFS datastore for ESXi host/cluster

This workflow helps you create multiple storage volumes in PowerMax or VMAX, and presents the volumes as VMFS datastores to an existing VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple storage volumes (TDEVs). 4. Allocate the newly created storage volumes to an existing storage group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to VMware vSphere ESXi host/cluster.

Expand the storage volume and increase VMFS capacity of existing datastore

This workflow helps expand the storage volume in PowerMax or VMAX and increases the corresponding VMFS datastore capacity for the VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Retrieve the PowerMax or VMAX volume ID.

4

16 Storage management

3. Expand the storage volume. 4. Expand the VMFS datastore. 5. Rescan the host vHBAs for the VMware vCenter datastore host/cluster.

Remove VMFS datastore and associated storage volume

This workflow removes the selected datastore from the VMware vSphere ESXi cluster and removes the associated storage volumes from the PowerMax or VMAX storage group.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Remove the datastore from VMware vSphere ESXi cluster. 3. Unmap the storage volume from PowerMax or VMAX.

Delete VMFS datastore and associated storage volume

This workflow removes the selected datastore from a VMware vSphere ESXi cluster, and unmaps the volume from the PowerMax or VMAX storage group before deleting the volume.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Delete the VMFS datastore from the VMware vSphere ESXi cluster. 3. Unmap the storage volume from the PowerMax or VMAX storage group. 4. Delete the storage volume.

Add datastore to existing ESXi cluster

This workflow adds one or more storage volumes to a storage group, which is created as a datastore in VMware ESXi cluster.

The following manual steps are automated by this workflow: 1. Select the storage volume. 2. Add the storage volume to the storage group. 3. Validate and rescan the VMware ESXi cluster. 4. Create and add VMFS datastores to the selected VMware ESXi clusters.

Create new volume and datastore; move VMs to new datastore

This workflow creates a new storage volume and VMFS datastore and allows you to migrate one or more virtual machines (VM) to the newly created datastore using vMotion. You can select Compute vMotion, Storage vMotion, or Compute and Storage vMotion.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple storage volumes (TDEVs). 4. Allocate the newly created storage volumes to an existing storage group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to the VMware vSphere ESXi host/cluster. 7. Select the applicable VMs. 8. Create a snapshot of the VMs. 9. Migrate the VMs. 10. Verify the VMs migrated successfully.

Storage management 17

Create new volume and attach RDM disks to VM

This workflow creates new storage volumes and adds the volume to the selected storage group. After adding the storage volume, the workflows adds raw device mapping (RDM) to the selected virtual machine (VM).

The following manual steps are automated by this workflow: 1. Create new storage volumes. 2. Present new storage volumes as an RDM to hosts. 3. Rescan the hosts. 4. Attach the RDM to the production VMs.

Delete block volume

This workflow selects one or more storage volumes that are not part of a storage group to delete from a PowerMax or VMAX storage array.

The following manual steps are automated by this workflow: 1. Select the applicable storage volumes. 2. Verify the selected storage volumes are not part of a storage group. 3. Delete the storage volumes.

Expand block volume

This workflow selects one or more storage volumes from a storage group in the PowerMax or VMAX storage array to expand based on the specified value.

The following manual steps are automated by this workflow: 1. Select the storage volume to expand. 2. Enter the new size of the storage volume. 3. Expand the storage volume in the selected storage group by the amount specified.

PowerStore

Create volume and VMFS datastore for ESXi host/cluster

This workflow helps you create multiple volumes in PowerStore, and presents the volumes as VMFS datastores to an existing VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple volumes. 4. Allocate the newly created volumes to an existing storage group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to VMware vSphere ESXi host/cluster.

Expand the volume and increase VMFS capacity of existing datastore

This workflow helps expand the volume in PowerStore and increases the corresponding VMFS datastore capacity for the VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Retrieve the PowerStore volume ID.

18 Storage management

3. Expand the volume. 4. Expand the VMFS datastore. 5. Rescan the host vHBAs for the VMware vCenter datastore host/cluster.

Remove VMFS datastore and associated volume

This workflow removes the selected datastore from the VMware vSphere ESXi cluster and removes the associated volumes from the PowerStore storage array.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Remove the datastore from VMware vSphere ESXi cluster. 3. Unmap the volume from the PowerStore storage array.

Delete VMFS datastore and associated volume

This workflow removes the selected datastore from a VMware vSphere ESXi cluster, and unmaps the volume from the PowerStore storage array before deleting the volume.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Delete the VMFS datastore from the VMware vSphere ESXi cluster. 3. Unmap the volume from the PowerStore storage array. 4. Delete the volume.

Dell Unity and Dell Unity XT

Create LUN volume and VMFS datastore for ESXi host/cluster

This workflow helps you create multiple LUNs in Dell Unity and Dell Unity XT, and presents the volumes as VMFS datastores to an existing VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple storage LUNs. 4. Allocate the newly created storage volumes to an existing storage group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to VMware vSphere ESXi host/cluster.

Expand the LUN and increase VMFS capacity of existing datastore

This workflow helps expand the LUN in a Dell Unity or Dell Unity XT storage array and increases the corresponding VMFS datastore capacity for the VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Retrieve the Dell Unity or Dell Unity XT LUN ID. 3. Expand the LUN. 4. Expand the VMFS datastore. 5. Rescan the host vHBAs for the VMware vCenter datastore host/cluster.

Storage management 19

Remove VMFS datastore and associated LUN

This workflow removes the selected datastore from the VMware vSphere ESXi cluster and removes the associated LUN from a host in the Dell Unity or Dell Unity XT storage array.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Remove the datastore from VMware vSphere ESXi cluster. 3. Unmap the LUN from a host in the Dell Unity or Dell Unity XT storage array.

Delete VMFS datastore and associated LUN

This workflow removes the selected datastore from a VMware vSphere ESXi cluster, and unmaps the LUN from a host in the Dell Unity or Dell Unity XT storage array before deleting the LUN.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Delete the VMFS datastore from the VMware vSphere ESXi cluster. 3. Unmap the LUN from the host in the Dell Unity or Dell Unity XT storage array. 4. Delete the LUN.

Add datastore to existing ESXi cluster

This workflow adds one or more LUNs to a host in the Dell Unity or Dell Unity XT storage array, which is created as a datastore in VMware ESXi cluster.

The following manual steps are automated by this workflow: 1. Select the LUN. 2. Add the LUN to the host in the Dell Unity or Dell Unity XT storage array. 3. Validate and rescan the ESXi cluster. 4. Create and add VMFS datastores to the selected ESXi clusters.

Create new LUN and datastore; move VMs to new datastore

This workflow creates a new LUN and VMFS datastore and allows you to migrate one or more virtual machines (VM) to the newly created datastore using vMotion. You can select Compute vMotion, Storage vMotion, or Compute and Storage vMotion.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple LUNs. 4. Allocate the newly created LUNs to a host in the Dell Unity or Dell Unity XT storage array. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to the VMware vSphere ESXi host/cluster. 7. Select the applicable VMs. 8. Create a snapshot of the VMs. 9. Migrate the VMs. 10. Verify the VMs migrated successfully.

Create new LUN and attach RDM disks to VM

This workflow creates a new LUN and adds the LUN to the selected host in the Dell Unity or Dell Unity XT storage array. After adding the LUN, the workflows adds raw device mapping (RDM) to the selected virtual machine (VM).

The following manual steps are automated by this workflow: 1. Create new LUNs.

20 Storage management

2. Present the new LUNs as an RDM to hosts. 3. Rescan the hosts. 4. Attach the RDM to production VMs.

XtremIO

Create new LUN and VMFS datastore for ESXi host/cluster

This workflow helps you create multiple LUNs in XtremIO, and presents the volumes as VMFS datastores to an existing VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple storage LUNs. 4. Allocate the newly created storage volumes to an existing storage group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to VMware vSphere ESXi host/cluster.

Expand the LUN and increase VMFS capacity to existing datastore

This workflow helps expand the LUN in the XtremIO storage array and increases the corresponding VMFS datastore capacity for the VMware vSphere ESXi host/cluster.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Retrieve the XtremIO LUN ID. 3. Expand the LUN. 4. Expand the VMFS datastore. 5. Rescan the host vHBAs for the VMware vCenter datastore host/cluster.

Remove VMFS datastore and associated LUN

This workflow removes the selected datastore from the VMware vSphere ESXi cluster and removes the associated LUN from the XtremIO initiator group.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Remove the datastore from VMware vSphere ESXi cluster. 3. Unmap the LUN from the XtremIO initiator group.

Delete VMFS datastore and associated LUN

This workflow removes the selected datastore from a VMware vSphere ESXi cluster, and unmaps the LUN from the XtremIO initiator group before deleting the LUN.

The following manual steps are automated by this workflow: 1. Identify the datastore in VMware vCenter. 2. Delete the VMFS datastore from the VMware vSphere ESXi cluster. 3. Unmap the LUN from the XtremIO initiator group. 4. Delete the LUN.

Storage management 21

Add datastore to existing ESXi cluster

This workflow adds one or more LUN to an initiator group, which is created as a datastore in VMware ESXi cluster.

The following manual steps are automated by this workflow: 1. Select the LUN. 2. Add the LUN to the XtremIO initiator group. 3. Validate and rescan the ESXi cluster. 4. Create and add VMFS datastores to the selected ESXi clusters.

Create new LUN and datastore; move VMs to new datastore

This workflow creates a new LUN and VMFS datastore and allows you to migrate one or more virtual machines (VM) to the newly created datastore using vMotion. You can select Compute vMotion, Storage vMotion, or Compute and Storage vMotion.

The following manual steps are automated by this workflow: 1. Select the storage array. 2. Verify the capacity of the storage array. 3. Create multiple LUNs. 4. Allocate the newly created LUNs to an existing initiator group. 5. Rescan the host vHBAs in VMware vCenter. 6. Create VMFS datastores and add them to the VMware vSphere ESXi host/cluster. 7. Select the applicable VMs. 8. Create a snapshot of the VMs. 9. Migrate the VMs. 10. Verify the VMs migrated successfully.

Create new LUN and attach RDM disks to VM

This workflow creates a new LUN and adds the LUN to the selected initiator group. After adding the LUN, the workflows adds raw device mapping (RDM) to the selected virtual machine (VM).

The following manual steps are automated by this workflow: 1. Create new LUNs. 2. Present the new LUNs as an RDM to hosts. 3. Rescan the hosts. 4. Attach the RDM to production VMs.

22 Storage management

Snapshot management Snapshot management workflows help automate manual and repetitive administrative tasks such as creating and deleting snapshots of existing storage groups.

PowerMax/VMAX

Create snapshot of storage group

This workflow creates a new or existing snapshot of a PowerMax or VMAX storage group. As part of this workflow, you have the option to set the time to live value, which defines how long the snapshot is kept.

The following manual steps are automated by this workflow: 1. Select the storage group in PowerMax or VMAX. 2. Create a snapshot of the storage group.

Rename snapshot of storage group

This workflow selects a snapshot to rename from a selected storage group.

The following manual steps are automated by this workflow: 1. Select an existing snapshot to rename. 2. Rename snapshot.

Delete snapshot of storage group

This workflow deletes a snapshot from a selected storage group.

The following manual steps are automated by this workflow: 1. Select an existing snapshot to delete. 2. Delete snapshot.

Dell Unity and Dell Unity XT

Create snapshot of block LUN

This workflow creates a new or existing snapshot of a Dell Unity or Dell Unity XT block LUN. As part of this workflow, you have the option to set the time to live value, which defines how long the snapshot is kept.

The following manual steps are automated by this workflow: 1. Select the Dell Unity or Dell Unity XT block LUN. 2. Create a snapshot of the block LUN.

5

Snapshot management 23

Export snapshot of block LUN to host

This workflow exports a snapshot of a Dell Unity or Dell Unity XT block LUN to an ESXi host.

The following manual steps are automated by this workflow: 1. Select a snapshot of a Dell Unity or Dell Unity XT block LUN. 2. Select an ESXi host. 3. Export the selected snapshot to the selected host.

Delete snapshot of block LUN

This workflow deletes a snapshot of a Dell Unity or Dell Unity XT block LUN.

The following manual steps are automated by this workflow: 1. Select an existing snapshot of a block LUN to delete. 2. Delete snapshot.

24 Snapshot management

Provision ESXi hosts - PowerStore boot Deploys a service profile from a service profile template and associates it with a selected server. The Ansible Playbook provisions servers using the boot volume of the PowerStore storage array, while selecting the corresponding zoning and masking, installing VMware ESXi, and adding the server to the VMware ESXi cluster.

Prerequisites The following are required before you can run the playbook successfully:

IP addresses needed to provision the VMware ESXi hosts are free. The VLANS are configured in the ToR switches. The VMware ESXI license keys are available for the required version. The following components are configured:

PowerStore - available to provision volumes. Cisco MDS switches - vSAN, zone, and fc alias are configured and available to provide the vSAN for the host. Cisco UCS servers - Service profile is created and available to use for the allocated servers. VMware vCenter - ESXi cluster is available to add the host, along with vMotion, FT and NFS port groups are added to

DVS for use by the newly provisioned hosts.

The input file contains the following sections:

Name Description

system Serial number for your VxBlock System

managedBy Details for Converged Management Software (CMS)

compute Information for Cisco UCS and server configuration sections

network Details for Cisco MDS switches

storage Details for PowerStore storage array

virtualization Configuration for VMware vCenter and ESXi

system:

serialNumber: - The serial number of the VxBlock System that contains the Cisco UCS servers you want to provision.

managedBy:

name: - Details for the instance of CMS managing the VxBlock System selected. ipAddress: - IP address for CMS. hostName: - Hostname for CMS. credentials: - The credentials for the instance of CMS selected. username: - ciadmin

compute: - UCSM details and server configuration.

family: - Default is set to ucs.

type: - Default is set to ucsm.

ipAddress: - IP address for UCSM. hostName: - Hostname for UCSM. role: - Default is set to compute.

configuration: - Service profile details for the host you want to provision. serviceProfileTemplate: - Name of the service profile. destinationOrg: - Default is set to org-root.

restrictMigration: - Default is set to false.

6

Provision ESXi hosts - PowerStore boot 25

esxiProvisioning: - Select the IP address of the Dell EMC PowerStore storage array. imageName: - Enter the name for the VMware ESXi image. version: - Enter the version of VMware ESXi that corresponds to the ESXi image.

network- Network details for host provisioning subnet: - Subnet mask for the VMware ESXi management IP. gateway: - Gateway for the VMware ESXi management IP. domain: - Domain for the VMware ESXi management IP. nameServer: - DNS IP address. vlan: - Default is set to 105.

servers: - Details for the VMware ESXi servers (Provision up to 5 servers at one time) type: - Blade or rack server. ipAddress: - IP address for the UCS server. hostName: - Hostname for the UCS server. chassisId: - ID for the chassis that contains the server. serverId - ID for the server being provisioned. credentials: - Credentials for the server. userName: - Username previously created for the server. pwdValue: - Password that corresponds to the username.

Repeat the same inputs for each server with up to five servers in total.

network: - Details for Cisco MDS switches.

family: - Default is set to mds.

type: - Default is set to a.

ipAddress: - IP address for Cisco MDS A in the VxBlock System selected. hostName: - Hostname for Cisco MDS A in the VxBlock System selected. role: - Default is set to SAN.

configuration: - Configuration details for Cisco MDS A. vsan: - vsan for Cisco MDS A. zone: - Zone where pwwn is registered for MDS A. domain: - fc alias for Cisco MDS A.

family: - Default is set to mds.

type: - Default is set to b.

ipAddress: - IP address for Cisco MDS B in the VxBlock System selected. hostName: - Hostname for Cisco MDS B in the VxBlock System selected. role: - Default is set to SAN.

configuration: - Configuration details for Cisco MDS B. vsan: - vsan for Cisco MDS B. zone: - Zone where pwwn is registered for MDS B. domain: - fc alias for Cisco MDS B.

storage: - Details for PowerStore storage array.

family: - Default is powerstore.

type: - ipAddress: - IP address for PowerStore storage array in the VxBlock System selected. hostName: - Hostname for PowerStore storage array in the VxBlock System selected. role: - Default is BlockStorage.

configuration: - Configuration details for the boot volume of the PowerStore storage array. type: - Default is boot.

size: - The size of the boot volume. unit: - The unit type used for the size of the boot volume in GB or TB.

virtualization: - Details for VMware vCenter.

family: - Default is virtualization.

type: - Default is vcenter.

ipAddress: - IP address for the VMware vCenter to which the host is added. hostName: - Hostname for the VMware vCenter to which the host is added.

26 Provision ESXi hosts - PowerStore boot

role: - Default is primary.

configuration: - Configuration details for VMware vCenter cluster. licenseKey: - Key for the VMware ESXi license. cluster:

addhostToCluster: - Default is set to true.

parentCluster: - The cluster where the host is provisioned. resource: credentials: - Credentials for VMware vCenter. userName: - Username previously created for VMware vCenter. pwdValue: - Password that corresponds to the username.

network: - type: - Default is set to vds.

- switch: - Name of Virtual Distributed Switch (VDS). - portGroup: - Name of management port group in the VDS. - vmotion: - Set to true or false, if needed. If set to true, additional details for VMotion are needed.

- ft: - Set to true or false, if needed. If set to true, additional details for FT are needed.

- nfs: - Set to true or false, if needed. If set to true, additional details for NFS are needed.

vmotionDetails: - Details for VMotion when set to true.

- portGroup:- Name of the port group to host the VMotion VMK. - ipAddress: - IP address used to create VMotion VMK. - subnetMask: - Subnet mask used to create VMotion VMK.

ftDetails: - Details for FT when set to true.

- portGroup:- Name of the port group to host the FT VMK. - ipAddress: - IP address used to create FT VMK. - subnetMask: - Subnet mask used to create FT VMK.

nfsDetails: - Details for NFS when set to true.

- portGroup:- Name of the port group to host the NFS VMK. - ipAddress: - IP address used to create NFS VMK. - subnetMask: - Subnet mask used to create NFS VMK.

Provision ESXi hosts - PowerStore boot 27

Provision ESXi hosts - PowerStore This playbook helps provisions servers using the boot volume of the PowerStore storage array, while associating a service profile with a server, selecting the corresponding zoning and masking, installing VMware ESXi, and adding the server to the VMware ESXi cluster.

The following manual steps are automated by this playbook: 1. Determine the available resources (servers) and validate the data. 2. Identify a service profile template in use by the existing service. 3. Create and apply a service profile from a service profile template. 4. Configure the zoning on the SAN switches

Manualsnet FAQs

If you want to find out how the VxBlock 350 Dell works, you can view and download the Dell VxBlock 350 Converged Infrastructure Reference Guide on the Manualsnet website.

Yes, we have the Reference Guide for Dell VxBlock 350 as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Reference Guide should include all the details that are needed to use a Dell VxBlock 350. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell VxBlock 350 Converged Infrastructure Reference Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell VxBlock 350 Converged Infrastructure Reference Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell VxBlock 350 Converged Infrastructure Reference Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell VxBlock 350 Converged Infrastructure Reference Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell VxBlock 350 Converged Infrastructure Reference Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.