Built a NSX-T 184.108.40.206, and go to add a Host Node, but all of the choices for OSes are physical servers, i.e. no ESXI nor KVM etc.
On the left is nsx-t 220.127.116.11 - on the right for comparison is nsx-t 3.x
Any suggestions on why no ESXi appears?
The standalone host won't support VDS integration, that's why you are not seeing
all of my hosts are 7.0 with Enterprise Plus licenses, so they support VDS switches.
It limits the choices well before I even enter a host IP address (probably should have mentioned that).
Re-built nsx4.0 with "Medium" size just to be sure that "Small" might have been causing problems. Same result.
This is probably the issue (seen from that link):
VDS is configured through vCenter, while N-VDS was vCenter independent. With the deprecation of N-VDS, NSX will be closely tied to vCenter and vCenter will be required to enable NSX in vSphere environments.
I don't yet have vCenter and NSX communicating properly. In the past, I could add Host Nodes without that connection being done first.
Thanks a lot for that link.
You are trying to add a host in the standalone mode. It will work only when the host has NVDS integration which is deprecated in the recent release. So the choice of design moving forward is to use vSphere Cluster preparation wherein all hosts are backed by VDS 7.X or later
From NSX 4.x onwards since the NVDS is deprecated, you will have to use the TransportNode profiles in NSX and use them to prepare the vSphere clusters that you want prepared for NSX. So from my understanding since its Converged VDS or only VDS used in NSX 4.x, you have the option to prepare the clusters using the VDS.
Thanks for all of the answers, but I'm still confused.
Suppose I wanted to add a Ubuntu KVM host - it's not in the list here:
I haven't put in any ip addresses, etc.
So the fact that I don't get a good connection to any vCenter shouldn't be a factor.
And: I would still think that esxi should appear in this list also.
Not sure what I'm missing - obviously doing something wrong.