VMware Networking Community
huchord
Enthusiast
Enthusiast
Jump to solution

No ESXi choice when adding Host Node

 

Built a NSX-T 4.1.0.2, 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 4.1.0.2 - on the right for comparison is nsx-t 3.x

huchord_0-1689346396904.png

 

Any suggestions on why no ESXi appears?

 

Reply
0 Kudos
2 Solutions

Accepted Solutions
tdyson
Enthusiast
Enthusiast
Jump to solution

KVM support is removed from NSX 4.x

View solution in original post

NicoRenard
Enthusiast
Enthusiast
Jump to solution

KVM is no longer supported by NSX because It was not so much used, so VMware decided to remove it. It's why you are not seeing it also...

View solution in original post

10 Replies
Sreec
VMware Employee
VMware Employee
Jump to solution

The standalone host won't support VDS integration, that's why you are not seeing 

https://docs.vmware.com/en/VMware-NSX/4.0/rn/vmware-nsx-4001-release-notes/index.html 

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
huchord
Enthusiast
Enthusiast
Jump to solution

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.

 

 

 

Reply
0 Kudos
huchord
Enthusiast
Enthusiast
Jump to solution

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.

 

 

Reply
0 Kudos
Sreec
VMware Employee
VMware Employee
Jump to solution

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

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 6x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
cms7
VMware Employee
VMware Employee
Jump to solution

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.

Reply
0 Kudos
huchord
Enthusiast
Enthusiast
Jump to solution

 

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:

 

huchord_0-1689596356116.png

 

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.

 

 

 

 

Reply
0 Kudos
tdyson
Enthusiast
Enthusiast
Jump to solution

KVM support is removed from NSX 4.x

NicoRenard
Enthusiast
Enthusiast
Jump to solution

KVM is no longer supported by NSX because It was not so much used, so VMware decided to remove it. It's why you are not seeing it also...

huchord
Enthusiast
Enthusiast
Jump to solution

Thanks again for all of the responses.

vCenter connected properly and all esxi hosts are usable.

Understood now that KVM is no longer supported.

Good to go.

cms7
VMware Employee
VMware Employee
Jump to solution

Great to hear that Huchord. Please mark this as solved and and please give a kudos to all the replies.

Thanks