vSAN1

 View Only
  • 1.  vSAN Policy

    Posted May 15, 2018 03:34 PM

    Hello Support,

    I'm trying to create a new vSAN policy using RAID5 but I'm not able to find the Failure tolerance method in the vSAN policy as per the below screen shot.



  • 2.  RE: vSAN Policy

    Posted May 15, 2018 03:40 PM

    Hello elieqt

    Are you perchance using a vSAN cluster with Standard Licensed and/or a Hybrid cluster here?

    RAID5/6 requires All-Flash and a minimum of Advanced vSAN licensing:

    https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsan/vmware-vsan-66-licensing-guide.pdf

    Using RAID 5 or RAID 6 Erasure Coding

    Bob



  • 3.  RE: vSAN Policy

    Posted May 18, 2018 08:53 PM

    Hello Bob,

    Thanks for the information.

    I tried to add the vSAN Enterprise license from the vCenter server but the CPU number is still 0. How can I activate the vSAN license per CPU?

    Regards,



  • 4.  RE: vSAN Policy

    Posted May 18, 2018 09:09 PM

    I added the license as per the below screen shot, but I'm still not able to find the RAID Method in the policy.



  • 5.  RE: vSAN Policy

    Posted May 18, 2018 09:21 PM

    Hello elieqt​,

    Are there at least 4 nodes in the cluster and out of Maintenance Mode etc.?

    This is an All-Flash cluster?

    Is this a 4-node single-CPU cluster? (This is the only configuration that could be licensed as per the image)

    If yes to both then try resyncing the VASA providers and restarting vmware-sps service on the vCenter.

    VMware Knowledge Base

    Bob



  • 6.  RE: vSAN Policy

    Posted May 18, 2018 09:48 PM

    It is a Hybrid cluster.



  • 7.  RE: vSAN Policy

    Posted May 18, 2018 10:01 PM

    Hello elieqt​,

    Theres the reason so.

    "RAID 5 or RAID 6 erasure coding is available only on all-flash disk groups."

    https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-6D818555-8DE8-4F06-9498-66903FB9C775.html

    Bob



  • 8.  RE: vSAN Policy

    Posted May 18, 2018 10:06 PM

    Thanks a lot.