Symptoms

The health-check called hoststatus is run by VxVerify from VxRail Manager prior to an upgrade. This check attempts to validate the host management accounts used in the VxRail environment to ensure that they are complete and consistent in the VxRail Manager DO-Host and Lockbox services. TestResultResult CodeResult InterpretationPass (green)0Host management accounts matchWarning (yellow)1Host connects not OK, such as when a retry was necessary to establish an SSH session to the node.Failure (red)2Failures can occur due to SSH connection issues between VxRM and ESXi nodes.Critical (purple)3Potentially caused by errors in the VxRM database tables The full results of this test may not fit into a single line of the summary table. The full results can be checked in the VxVerify log.The following​​​​ responses are examples of hoststatus warning or failure alerts: #========================#======#=========#====================================================================#==============# | Hostname / Category |Status Dell_KB | Warnings or Failures, unless tests Passed ; Product S.N. | #========================#======#=========#====================================================================#==============# | esxi-01 | Failure 203703 | hoststatus: Host connection: Ok; iDRAC IP missing xxxxxxxxxxx| | esxi-02 | Warning 203703 | hoststatus: Host connection had to be retried xxxxxxxxxxx| | _cluster | Warning 203703 | hoststatus: Invalid configuredHosts: ['xxxxxx', 'xxxxxx'] |

Cause

Node Disconnected This article is only for the hoststatus issues that are detected from VxRail Manager 7.0.010 and later. Typical root cause of node hoststatus warnings or failures include: SSH connectivity issue between VxRail Manager and Host in issue with management accountDNS-related issues for the node when obtaining an IP address from the hostnameiDRAC IP address missing from DO_Host record If hoststatus warnings are for _cluster, this may be caused by incomplete entries in the VxRM do_host records for some node serial numbers. In that case, it is likely that those serial numbers are for unconfigured nodes. If these serial numbers must be double checked against the other nodes, this is done by checking the VxTii report (vxtii.txt). See article VxRail: Generating VxTii reports for troubleshooting VxRail Node Licenses A common cause for nodes being listed as disconnected when there were no previous connectivity issues, are the licenses expiring. Typically this could occur 60 days after installation if the nodes were still using evaluation licenses. Check licensing in the vCenter. 

Resolution

Check licensing in vSphere > Administration > Licensing > LicensesFor example, https://<vSphere-FQDN>/ui/app/admin/licensing/licensesIf the licensing has not expired, check these resolutions for the above connectivity root cause: Ensure that SSH connectivity issue between the VxRail Manager and Host in issue with management account Ensure DNS issues identified by health check test dnslookup are resolved. See article Dell VxRail: VxRM health-check fails for dnslookup (Login as a Registered Dell user is required to view the article).Restart iDRAC on the host.

Support Cases