vsan 6.2 "fault tolerance method" not available

[vmb01]

Hi,

I've installed 4 6,0u2 ESXi hosts, each one equipped with 3 flash devices and a VCVA 6.0U2

I've built the VSAN cluster without enabling dedup and compression.

But when I try to build a raid5 storage policy, I do not find the Failure Tolerance Method setting to enable the erasure coding with RAID5,

I found the Failure Tolerance Method setting only after have enabled dedup and compression.

Is this right ?

[Techie01 · Accepted solution]

That is surprising . I have 60U2 based vsan cluster where I am able to see 'Fault tolerance method' both option raid-0 and raid 5/6 without enabling dedupe/compression.

Can you confirm you had all flash disk group when you tried this option

Can you logout/login back to the webclient and check if you are able to see ( there is a know issue documented where some of the policies wont be seen unless you logout/login back to the UI)

Was it fresh installed or upgraded. If upgraded, have you done the disk version upgrade. I believe the features wont be seen if disk upgrades are not done ( and enabling dedup/compression automatically does a disk upgrade)

[CHogan]

Nope - it should be available immediately. I suspect it was just a refresh issue with the UI.

[vmb01]

I've done a new test and with logout/login back to the webclient and the policy appears.

[mlbaltz]

I found that this could also be due to not having a 6.2 license applied to the VSAN.

[ChrisKuhns]

It's actually a refresh of the VASA providers. Once those are seen the option become available.

[Vividly_Group]

I have VCSA 6.5.0 build 4602587, the fault tolerance method not showing up too. I used VSAN standard lic. Anyone can help?

[multihawk]

I was having the same issue on VCSA 6.5.0 & VSAN 6.6 but fix from ChrisKuhns​above worked for me.

In 6.5 Flex Client:

1. Hosts and Clusters view
2. Click vCenter
3. Click "Config" tab and then Storage Providers
4. Select VSAN Provider is HOSTNAME and then click "Synchronize all Storage Providers...." button.
5. Waited 15 seconds and then was able to create policy.