After configuring a Virtual SAN cluster, an administrator using the vSphere Web Client notices that the Virtual SAN datastore is smaller than expected. The cluster
contains:
Three ESXi hosts
Each host has one 10GB SDD
Each host has one 100GB HDD
Why would the Virtual SAN datastore show as 100GB instead of 300GB?
A.
There is a network problem with the Virtual SAN vmkernel ports.
B.
The Virtual SAN VASA provider is disabled.
C.
vSphere High Availability is enabled on the Virtual SAN cluster.
D.
The Virtual SAN cluster must be managed using the vSphere Web Client.
Explanation:
Explanation/Reference:
Correct Answer: A
0
0
Don’t know, which answer is right
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.virtualsan.doc/GUID-AD408FA8-5898-4541-9F82-FE72E6CD6227.html shows that administrator uses RAID1 with Number of Failures to Tolerate=2
B, D and A is definitly wrong
C is right?
0
0
A – Network partition
0
0
@RC, anything to back that up? I think this is worded incorrectly. C can be right, but it really isn’t talked about as HA. Rather, you have two replicas and one witness, so only 100GB available. Though, you don’t setup VSAN options under HA.
http://www.yellow-bricks.com/2013/08/26/introduction-vmware-vsphere-virtual-san/
1
0
I have spent way too much time on this question. I am still going with C. Here is why http://www.yellow-bricks.com/2013/09/19/isolation-partition-scenario-with-vsan-cluster-handled/
0
0
Not ‘C’ for sure. In fact, use of HA on VSAN clusters is a recommended practice.
In this case, VSAN vmkernel network is used for HA heartbeat (instead of mgmt vmk network).
‘D’ is obviously not the one since it just re-states what’s already in the question.
While ‘B’ seems theoretically feasible, i’m not aware of any way to do it using admin tools.
‘A’ explains why one or two hosts in this scenario might be not connected to the VSAN network.
By the way, in my lab i have three VSAN hosts with exactly this config and there’s no loss of capacity due to one host being a witness, i.e. total available capacity is close to 3 x 100 = 300 GB (minus FS overhead of course).
1
0
A.
There is a network problem with the Virtual SAN vmkernel ports.
0
0