Cluster is not compatible for Workload Management

[Ohad Mashiach]

trying to enable workload management in vsphere 7 but cluster is not compatible.

i validate the following are set: 3 ESXi hosts, DRS on , HA on, NSX-T 3.0 is running with trust enabled , hosts license with VMware vSphere 7 Enterprise Plus with Add-on for Kubernetes

also i'm getting this error when running cluster compatibility from within the vcenter.

|------------|----------|-----------------------------------------------------|

|cluster     |compatible|incompatibility_reasons                              |

|------------|----------|-----------------------------------------------------|

|domain-c2026|False     |Cluster domain-c2026 is missing compatible NSX-T VDS.

any advice what else can be the cause?

thanks

[daphnissov]

What configuration have you done yet inside NSX?

[Ohad Mashiach]

add compute manager, configure transport node, create 2 edge and add it to cluster, create tier-1.

TEP is up both for TN and edge.

[daphnissov]

You need to create a T0 router and not a T1 and configure the uplinks on the edges appropriately. You also need to tag those edges inside NSX.

[Ohad Mashiach]

saw this msg in wcp log:

2020-06-22T15:46:43.997Z debug wcp [opID=5ef0a333] nsx setNSXCompatibleClusterSet vdsList: []compatibility.DistributedSwitch{compatibility.DistributedSwitch{ID:"50 13 ce 84 6f f9 f1 6e-27 5f 98 1b c1 be 2b 3b", ClusterID:"domain-c2026:8b0db815-26a7-4e13-9617-dff34e4c426d", WCPCompatible:false, IncompatibilityReasons:[]std.LocalizableMessage{std.LocalizableMessage{Id:"vcenter.wcp.nsx.vds.incompatible.no_tier0_gateway", DefaultMessage:"VDS 50 13 ce 84 6f f9 f1 6e-27 5f 98 1b c1 be 2b 3b has no tier0 gateway.", Args:[]string{"50 13 ce 84 6f f9 f1 6e-27 5f 98 1b c1 be 2b 3b"}, Params:map[string]std.LocalizationParam(nil), Localized:(*string)(nil)}}}}

will try to create tier-0

thanks!

[daphnissov]

Yes, like I said, you must have a T0 created and configured.

[karlosvalencia]

could you explain how to get to that log?

[daphnissov]

/var/log/vmware/wcp/wcpsvc.log

[aravinda-mit]

Hi,

This is an error I received during the cluster validation

 

[aravinda-mit]

What I found was the VCenter server is unable to communicate with the NSX-Manager. This was due to an issue with the Domain Controller. The trust between NSX-Manager and the vCenter wasn't established due to the domain name resolving issue. Finally managed to fix.

[GregPatria]

Hi daphnissov​​

I've the same error, but maybe its different problem. can you help me?

2020-06-24T12:58:33.496Z debug wcp [opID=5ef2ec34] Transport node ID for host host-16: b793b69a-5c79-41e9-8da7-8312531453bb

2020-06-24T12:58:33.514Z debug wcp [opID=5ef2ec34] Transport node ID for host host-13: 0135609b-5abb-4930-9fbe-38960b3c1f76

2020-06-24T12:58:33.514Z debug wcp [opID=5ef2ec34] Finding VDS for hosts: b793b69a-5c79-41e9-8da7-8312531453bb, 0135609b-5abb-4930-9fbe-38960b3c1f76

2020-06-24T12:58:33.515Z error wcp [opID=5ef2ec34] Failed to get list of VDS for cluster: domain-c8. Err: Invalid hosts: b793b69a-5c79-41e9-8da7-8312531453bb

2020-06-24T12:58:33.515Z debug wcp [opID=5ef2ec34] nsx setNSXCompatibleClusterSet vdsList: []compatibility.DistributedSwitch(nil)

2020-06-24T12:58:33.515Z debug wcp [opID=5ef2ec34] nsx.nsxCompatibleClusterSet: map[]

thanks

[daphnissov]

Do you have ESXi hosts joined to this vDS that are below version 7.0 GA?

[GregPatria]

daphnissov​,

yes already joined..

[daphnissov]

Not what I asked. I asked what version were the hosts you have joined to the vDS.

[GregPatria]

upss, Im sorry, not all the words I read.

the esxi version is 7 GA..

[daphnissov]

It doesn't like host-16 for some reason. Are they both licensed for the vSphere 7 with Kubernetes add-on? If not, that's likely the issue.

[GregPatria]

yess daphnissov​ . actually vsphere 7 w/ k8s. I'm still confused, how come it's all of version 7, but that said VDS not compatible.

2020-06-24T12:58:33.414Z debug wcp [opID=5ef2ec34] Found tier0 router 2957e639-0e70-4f2e-ac34-87de9eb54401 associated with transport zone a9ae14d7-249b-4de1-8ab2-d6ba4cd15f86 via edge cluster 4e5075fb-d2fc-48dc-aa37-85ce5cc30603

2020-06-24T12:58:33.496Z debug wcp [opID=5ef2ec34] Transport node ID for host host-16: b793b69a-5c79-41e9-8da7-8312531453bb

2020-06-24T12:58:33.514Z debug wcp [opID=5ef2ec34] Transport node ID for host host-13: 0135609b-5abb-4930-9fbe-38960b3c1f76

2020-06-24T12:58:33.514Z debug wcp [opID=5ef2ec34] Finding VDS for hosts: b793b69a-5c79-41e9-8da7-8312531453bb, 0135609b-5abb-4930-9fbe-38960b3c1f76

2020-06-24T12:58:33.515Z error wcp [opID=5ef2ec34] Failed to get list of VDS for cluster: domain-c8. Err: Invalid hosts: b793b69a-5c79-41e9-8da7-8312531453bb

2020-06-24T12:58:33.515Z debug wcp [opID=5ef2ec34] nsx setNSXCompatibleClusterSet vdsList: []compatibility.DistributedSwitch(nil)

2020-06-24T12:58:33.515Z debug wcp [opID=5ef2ec34] nsx.nsxCompatibleClusterSet: map[]

2020-06-24T12:58:33.516Z debug wcp [opID=5ef2ec34] TimeProfile[NSX]: Time taken to perform NSX compatibility check: 2.426941134s

2020-06-24T12:58:33.516Z debug wcp [opID=5ef2ec34] nsx checkNSXCompatibilityHelper incompatibleReasons: []

2020-06-24T12:58:33.516Z debug wcp [opID=5ef2ec34] TimeProfile[NSXD]: Time taken to perform NSXD compatibility check for vc: 10.224µs

2020-06-24T12:58:33.516Z debug wcp [opID=5ef2ec34] TimeProfile[Cluster]: Time taken to perform compatibility check for cluster domain-c8:

[daphnissov]

Are you able to spot at differences between how that one host attaches to the vDS versus the other?

[GregPatria]

Still got incompatible after I add one host and not attached to VDS

[Sukanya D]

check if all the Edge  uplink status are up in  NSX-T.

[daphnissov]

Doesn't have anything to do with it, Sukanyad​. The user hasn't deployed a T0, which is why the cluster is showing as incompatible.