NVDS switch migration to vCenter vDS- how to add a host to NSX-T now?

[JDMils_Interact]

With the NSXT NVDS swith residing in the NSXT environment, we would add a new host to the NSXT-enabled cluster, and the Transport Node Profile would automatically connect the specified vmnics on the host to the NVDS switch.

Now we have migrated the NVDS switch to vCenter as a vDS switch and found that we have to manually add the respective vmnics to the NVDS vDS switch and NSXT would then configure the host for NVDS connectivity.

Is this the correct way in which the NVDS switch now works when configured as a vDS switch in vCenter?

What's the purpose of the TNP now when we have to manually add the vmnics to the vDS NVDS switch?

vCenter 7.0u3s
ESXi hosts build 23794027 7.0u3q
NSXT 3.2.4

[JohannesWalter]

Hello, 
please note the exact wording, NVDS actually only refers to the old implementation. The new variant is called “VDS” or occasionally “CVDS”. It was used imprecisely in the question...

Francois Tallet has written a very good document on the subject of NVDS/VDS: https://community.broadcom.com/applications-networking-security/blogs/francois-tallet/2024/11/21/moving-from-nvds-to-vds

Although the NVDS provided the same functions as a vCenter VDS, it was fully managed by NSX. It could therefore also be deployed from NSX (outside of vCenter). 

If you take a close look at the new construct with VDS and the NSX extensions, almost all functions are provided by the (C)VDS. NSX only adds a few additional features.
This also explains why the VDS must be provided by the vCenter (outside NSX). The NSX transport node profile (vCenter doesn' know anything about it) then only refers to the NSX additional features, and is provided by NSX manager.

The new order is:
1. you create a transport node profile (possibly specific to an ESX cluster)
2. connect the Compute Manager (vCenter) to the NSX Manager
3. the ESX clusters from the Compute Manager become visible in the NSX Manager (Transport Node Collections)
4. you assign a Transport Node Profile to a Transport Node Collection in the NSX Manager
5. all existing hosts in the ESX cluster automatically receive the NSX configuration according to the TNP

If you want to add another host, you just have to move it into the ESX cluster in vCenter...

Kind regards
Hannes

[JDMils_Interact]

So the process now is:

1. Add a new host to the vCenter.
2. Attach the appropriate vmnics to the NVDS vDS switch.
3. NSXT will then install the NSXT VIBs on the host.
4. Done.

The old process when the NVDS switch was managed by NSXT Manager was:

1. Add the new host to the vCenter.
2. Reserve the correct vmnics as specified in the TNP.
3. NSXT would automatically add the vmnics to the NVDS switch.
4. Done.

Is this correct? So the TNP really just assigns the Uplink profile and NIOC profile to the vmnics.