AlphaJin
Contributor
Contributor

vSan unable to get pass fault domain creation

Jump to solution

Greetings salutation,

VSan newbie here.

After conducting the hands on lab and attempting to implement it on my own, I ran into a problem where I am stuck at "Create fault domains". Clicking next does nothing, not even an error message.

The 3 hosts are Dell R440 VSAN ready node.

-Have attempted to reinstall EXSi on all hosts but to no avail.

-Tried to create 3 separate fault domains for each host. Next is still unresponsive.

pastedImage_0.png

Looking through existing threads, there was a user who managed to overcome this problem by tweaking with NVMe drives on bios but did not provide any further information. Honestly not even sure if its using NVMe driver either but figure it's worth highlighting just in case.

vSAN configuration issue

Here's hoping veterans have an idea what's going on. Thanks in advance !

1 Solution

Accepted Solutions
TheBobkin
VMware Employee
VMware Employee

Hello AlphaJin

Welcome to Communities and vSAN.

Issues with configure wizard are very often caused by vCenter being on a lower version than the ESXi (e.g. 6.7 GA vCenter 6.7 U1 ESXi) - please confirm you vC is on same or higher build.

Also, there is no benefit to specifying Fault Domains in a 3-node cluster - the nodes themselves act as Fault Domains by default in non-stretched clusters.

Bob

View solution in original post

3 Replies
TheBobkin
VMware Employee
VMware Employee

Hello AlphaJin

Welcome to Communities and vSAN.

Issues with configure wizard are very often caused by vCenter being on a lower version than the ESXi (e.g. 6.7 GA vCenter 6.7 U1 ESXi) - please confirm you vC is on same or higher build.

Also, there is no benefit to specifying Fault Domains in a 3-node cluster - the nodes themselves act as Fault Domains by default in non-stretched clusters.

Bob

AlphaJin
Contributor
Contributor

Could have sworn I was using the most updated version...I will need to get this looked up next working day.

0 Kudos
AlphaJin
Contributor
Contributor

Holy Molly, you're absolutely right.

Resolved the problem by updating to 6.7 U3B. Can't believe the solution was that simple, you live and learn I guess.

Many thanks, Bobkin !

0 Kudos