Home » VMware » VCP550D » What is the reason for this failure?
A vSphere administrator needs to add more space to an existing 3-node Virtual SAN cluster. The attempts to add the new host to the cluster as a contributing member has failed. However, it can be added as a non-contributing member.
The host was previously used in a single host configuration. The administrator recently upgraded the host from ESXi 5.1 to 5.5 prior to adding it to the cluster.
What is the reason for this failure?
A. The only SSD disk in the new host was formatted with a VMFS datastore.
B. The new host has a 10Gbps NIC while the rest of the cluster members have 1Gbps NICs.
C. The RAID controller in the new host does not have enough cache for the Virtual SAN datastore.
D. The new host’s VMFS datastores do not have sufficient capacity to be added as a contributing member.
Correct Answer: A
Explanation/Reference:
Explanation:
Every contributing member in a Virtual SAN cluster must have an SSD available for use. The SSD must be unformatted to enable you to configure the host as a contributing member. In this question, the new host was previously used in a single host configuration. It is therefore likely that the SSD is still formatted with VMFS used for a datastore in the previous configuration. You need to remove the VMFS datastore from the SSD before the host can be added as a contributing member in the Virtual SAN cluster.
Incorrect Answers:
B: The network interface cards (NICs) do not need to be the same speed on the hosts in a Virtual SAN. The 10Gbps NIC on the new host will run at the same speed (1Gbps) as the NICs on the other hosts. Therefore, this answer is incorrect.
C: The RAID controller cache is not used or required in a Virtual SAN datastore. Therefore, this answer is incorrect.
D: If the new host has a VMFS datastore, it will be from its previous configuration. It will not have a datastore from the Virtual SAN in this question because it was unable to join the cluster as a contributing member. Therefore, the datastore size is irrelevant. A VMFS datastore from its previous configuration would prevent the host joining the cluster as a contributing member. Therefore, this answer is incorrect.
References:
https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-A17F5D39-C1F3-47B1-9645-5C247412F370.html
