unable to add host in NSX-t workload cluster in VCF 3.9 error is "unable to fetch NSX-T version"

[mkeshsundrani]

unable to add host in NSX-t workload cluster in VCF 3.9 error is "unable to fetch NSX-T version" 

[shank89]

Is this when trying to commission the host or trying to add the host to the cluster?

Are these repurposed hosts or fresh hosts, has the host or one with the same name been in the SDDC manager inventory before?

Is SSH enabled ?

[mkeshsundrani]

these are new host and SSH was already enabled when we commission the hosts.

after this we adding them in workload (nsxt) cluster , were its failing with mentioned error

-------------------

Description Validate that installed NSX-T version is supported
Progress Messages Unable to check NSX-T version

Error

Message: Unable to check NSX-T version

Remediation Message:

Reference Token: O88AC9

Cause:

Type: java.lang.RuntimeException

Message: Unable to fetch NSX-T version

Type: java.lang.RuntimeException

Message: Cannot execute request

[shank89]

Can you pull the operations manager and domain manager log files please?

[shank89]

It would also be worthwhile to check if there are any NSX-T vibs on the host.

Esxcli software vib list | grep nsx

[CyberNils]

This is probably due to a communications problem between SDDC Manager and NSX-T Manager, so check that. Like Shank said, get the logs and look for Reference Token: O88AC9. I have had this error in my lab a few times and it has been due to lack of resources available for the NSX-T Manager, so increasing cpu/memory for that as well as rebooting it has solved it for me. Cheers.

[mkeshsundrani]

This is coming as Certificates issue when VCF wants to communicate with NSX-T, it uses FQDN.

But looks like pks uses IP address of nsxt VIP and create certificates , so VCF-SDDC is not able to communicate with NSX-T as it used FQDN.

VMware engr team- suggested to use FQDN and update that on pks side as well. 

surprisingly in PKS docs its not mentioned/recommended to use fqnd for certificates of nsxt VIP and it used IP.

in normal vsphere envrmt is ok but if its VCF then things arent same