VCP6-DCV blueprint section 3:Configure and Administer Advanced vSphere 6.x Storage -Objective 3.2 – Part 1

Home / blueprint / VCP6-DCV blueprint section 3:Configure and Administer Advanced vSphere 6.x Storage -Objective 3.2 – Part 1

In this post we will continue covering the storage objective from the blueprint. Again I will NOT follow the order of blueprint objective but i will cover all of them.

The following are the blueprint objective:

  • Explain VSAN and VVOL architectural components
  • Determine the role of storage providers in VSAN
  • Determine the role of storage providers in VVOLs
  • Explain VSAN failure domains functionality
  • Configure/Manage VMware Virtual SAN
  • Create/Modify VMware Virtual Volumes (VVOLs)
  • Configure Storage Policies
  • Enable/Disable Virtual SAN Fault Domains
  • Create Virtual Volumes given the workload and availability requirements
  • Collect VSAN Observer output
  • Create storage policies appropriate for given workloads and availability requirements
  • Configure VVOLs Protocol Endpoints

The following objective I will not be able to demonstrate since i am using VMware Workstation and not real HW but i will try to point to the configuration location

  • Create/Modify VMware Virtual Volumes (VVOLs)
  • Configure VVOLs Protocol Endpoints

Also since there is a lot to cover i will use multiple post and i will split vSAN and VVOL subjects

For vSAN we will need to use the following documents from VMware:

So let start with VSAN

Explain VSAN components



Source: VMwareVirtual SAN Whats New document

vSan architecture include the followings:

  • Minimum of three hosts in a cluster
  • SSD and HDD minimum one of each
  • Separate networking minimum 1G connection
  • VMkernel Port.

Configure/Manage VMware Virtual SAN

In this section I will configure vSAN in my current lab

The plan:

  • Networking – i will create new dVS with new VMkernels for vSAN traffic (this is not a must , you can use the existing vDS and allow vSAN traffic on it  but i will like to separate the vSAN traffic for more practice
  • Adding two more disks for each ESXi hosts (we will do it via VMware workstation)
  • Re-scanning the ESXi hosts for the new storage
  • Assign SSD to each ESXi host
  • Enable vSAN
  • Claim and assign diskgroups in each ESXi host
  • Verify vSAN datastore
  • Moving VM’s to vSAN


So lets get started:

New vDS switch configuration, i will not create all the screenshots for new vDS you can look at my previous networking posts. here is the screenshots of the vDS setup.


Make surer to enable “Virtual SAN traffic” in the new VMkernel


Adding 2 virtual disks to each ESXi host via VMware Workstation


Re-scan each ESXi host for the newly add drives


Assign one drive as a Flash drive on each ESXi hosts


Turning ON vSAN on the clsuter: Click on Cluster >> Manage>> Setting>>under vSAN General click on the Edit button >> Turn ON Virtual SAN >> change the setting to manual and click Ok.


After this is done you verify that you can see all 3 hosts ad network status is normal.


Under Disk Management we can now claims disks from each ESXi host to create diskgroups.


On each ESXi host choose One SSD and one HDD from the previous configuration




Verify that you have a new vSAN datastore


Now lets migrate VM;s (i have only one) to the new vSAN datastore. choose storage only


Choose vSAN datastore.


Thanks for reading



Leave a Reply

Your email address will not be published. Required fields are marked *