Failed to run health checks for NSX-T on hosts and cluster

[alireza1023]

Hi

when I run Pre-check on VLCM on hosts or remediate cluster I see this error:

Failed to run health checks for NSX-T on ...

my VCenter and ESXis are 7.0.1Uc and NSX-T is 3.1.1

what should I do?

[sjesse]

Moderator: I think  you'll get better help under NSX so I moved your question here

[shank89]

We'll need more information, screen shots, logs, error messages... is vRSLCM able to get to the VIP/ manager cluster, any firewalls in between, any issues in NSX-T ?

[alireza1023]

my hosts are HPE Customization for HPE Servers 701.0.0.10.6.3-9

ESXi 7.0.1Uc with NSX-T 3.1.1

in nsx-t all ports to all segments are allowed

when I attach 7.0.1Ud and check compliance:

4 of 4 hosts are out of compliance with the cluster's image

after pre-check:

Pre-check completed

Completed 02/19/2021, 10:45:26 PM

1 issue on the cluster

The image has hardware compatibility issues.

2 issues on host 172.30.0.104

Failed to run health checks for NSX-T on '172.30.0.104'.

Failed to run health checks for NSX-T on '172.30.0.104'.

4 issues on host 172.30.0.102

Virtual machine 'Crater' that runs on cluster 'vSAN Cluster' reported an issue which prevents entering maintenance mode: Currently connected device 'USB 41001' uses backing 'path:0/1/12', which is not accessible.

DRS reported issues that prevent host '172.30.0.102' from entering maintenance mode

Failed to run health checks for NSX-T on '172.30.0.102'.

Failed to run health checks for NSX-T on '172.30.0.102'.

2 issues on host 172.30.0.103

Failed to run health checks for NSX-T on '172.30.0.103'.

Failed to run health checks for NSX-T on '172.30.0.103'.

4 issues on host 172.30.0.101

Virtual machine 'Libra' that runs on cluster 'vSAN Cluster' reported an issue which prevents entering maintenance mode: Currently connected device 'USB 41001' uses backing 'path:0/1/13', which is not accessible.

DRS reported issues that prevent host '172.30.0.101' from entering maintenance mode.

Failed to run health checks for NSX-T on '172.30.0.101'.

Failed to run health checks for NSX-T on '172.30.0.101'.

[shank89]

The errors are pointing you in the direction, have you tried resolving the issues with DRS and the VM? if the hosts can't be placed into maintenance mode it breaks the upgrade workflow and you'll get issues like this.

[alireza1023]

my problem is:

Failed to run health checks for NSX-T on ...

for maintenance mode I can shutdown those vm, but what should I do about this error?

[shank89]

The IP ending in .101 is your NSX-T manager right?

What is the health status of your NSX-T cluster?  Are you performing the compliance check with vCenter or are you using any form of lifecycle management?

[alireza1023]

101, 102, 103 and 104 are hosts

NSX-T managers are OK, I checked with lifecycle manager in vcenter

[shank89]

If NSX-T is healthy, i'm not so sure that you have posted this in the correct thread.  However, have you actually attempted to sort out the vSAN and DRS errors and retry to see what behaviour you get at that stage?

[mauricioamorim]

There are some pre-reqs when using vLCM with NSX-T. I would start checking these 2:

1) Did you prepare your hosts using Transport Node Profile?

2) Check the setting regarding vCenter in NSX-T (System > Fabric > Compute Managers). Verify that you have enabled the service account creation, enabled trust and also given full access (last three options).

Other helpful information can be found here: Prepare an NSX-T Cluster with vSphere Lifecycle Manager (vmware.com)

[alireza1023 · Accepted solution]

my problem is wrong time configuration!!!

when I corrected ntp on nsx-t, it seems OK

one of my problem was traceflow and now it's OK!!!!

[mhkhoshraftar]

Hi,

For solve this problem "Failed to run health checks for NSX-T on '172.30.0.102'."

you must login to your NSX-T UI, go to the system and Compute Managers edit Compute Managers and save it again.

Validate your vCenter certificate for NSX-T.