Summary: The intent of this KB is for awareness in the event that one might encounter the same issue.
Article Content
| Issue | When new deployment is initiated and encounters the following message: "An unknown validation error occurred in WitnessHostValidator" NOTE: In this particular case, it was not a stretch cluster.  [Failure] - Checking host is a witness node. [Failure] - Checking NTP server availability. [Failure] - Validating time configurations of VxRail Manager, ESXi nodes, and vCenter Server. [Failure] - Validating external DNS server host name records. [Failure] - Validating DNS server configuration. [Failure] - Verifying external vCenter Server licenses. [Failure] - Verifying external vCenter Server capacity. [Failure] - Validating vCenter Server user permissions. [Failure] - Verifying external vCenter Server entities. [Failure] - Validating ESXi host version compatibility. [Failure] - Validating vCenter Server version compatibility. |
| Cause | There is an IP conflict with VxRail Manager. |
| Resolution | Attempt to manually set static IP for VxRail Manager using KB: Customizing the VxRail Initial IP Address: 490026 If you cannot manually assign the VxRail IP manually, you would see the following: "Unable to set the network parameters"  NOTE: If you cannot manually assign the IP, VxRail validation will fail with the errors noted above. Use a different IP for VxRail Manager that is not taken. |