You can add locations to the Global Manager after you have installed the Global Manager. You can add up to three locations to a Global Manager. After you add a location to the Global Manager, the NSX Manager is called a Local Manager.
On the NSX Manager appliance, run the get certificate api thumbprint command to get the Thumbprint.
Copy and paste the Thumbprint into the required field and check compatibility.
When you're using a DVS for your NSX-T overlay transport zone, you have to think about where your edges will be connected to the overlay network. If the edge is attached to a distributed port group created on the same DVS in the same VLAN, it doesn't work.
In the picture, we can see that both tunnel endpoints are down. I'm hosting two virtual machines attached to an NSX segment based on an overlay transport zone. The segment is attached to a T0-Gateway for north-south connectivity.
The Alarms section also warns us that the edge overlay network is down.
The first interface of the edge is connected to the "Edge-Uplink-Management" distributed port group. The second interface is connected to the "Edge-Uplink-VLAN" distributed port group. Interface 3 and 4 are connected to the "Edge-Uplink-Overlay" port group.
The VMK10 Geneve tunnel endpoint on the ESXi host is using the same DVS and is configured with the same VLAN-ID 0.
After creating a second DSwitch Edge alongside the one that's used by NSX-T, I'm reconfiguring the second adaptor of the Edge virtual machine.
After a while, the tunnels on the Edge are reestablished.
So when you're using and N-VDS or VDS for NSX-T and you're placing an Edge on the same switch you have to put the Edge overlay in a different subnet. The Geneve traffic that originates from the Edge is not allowed to pass a switch that's hosting a tunnel endpoint for ESXi (VMK10).
One of the coolest features of NSX-T 3.0 is the possibility to host NSX-T of a distributed switch instead of an N-VDS. Especially when the amount of network adapters is limited, it allows you to create segments managed by NSX-T alongside distributed port groups and other kernel ports groups.
Your ESXi cluster can be prepared for NSX-T by assigning a transport node profile to the hosts. This transport node profile contains an Uplink profile. The uplink profile specifies which physical NICs are used on the ESXi host.
This is a default failover uplink profile with one uplink on standby and one active uplink.
In the switch visualization tab, you can clearly see that the VDS DSwitch is mapped to vmnic1 and vmnic2. This configuration is owned by vCenter. The kernel port group that's used as a Geneve tunnel endpoint will be created on this VDS. However, the failover policy for this VMK10 is managed by NSX-T.
We can see that the kernel port group is listed on the ESXi host and configured with an IP address that comes from an IP pool managed my NSX-T. The switch that's used by VMK10 is a VDS managed by vCenter.
This is the Networking view in the vSphere Client. You notice there's no port group listed for managing the policies of VMK10. The policies are managed by NSX-T.
In esxtop we're able to validate the NIC mapping of the Geneve tunnel endpoint (VMK10). It's connected to VMNIC1. When vmnic1 fails it will jump to vmnic2.
I was trying to apply a profile to my nested production cluster when I noticed the installation of the NSX kernel modules stalled at 18%. The ESXi hosts were configured with 8 GB of RAM but I also enabled vSAN of the cluster. After reconfiguring the hosts with 16 GB of memory and hitting the resolve button the process completed successfully.
Failed to install software on host. Failed to install software on host. esx01.ntpro.local : java.rmi.RemoteException: [LiveInstallationError] Error in running ['/etc/init.d/nsx-mpa', 'start', 'install']: Return code: 1 Output: Unable to setmemconfig for mpa host/vim/vmvisor/mpa Resource pool 'host/vim/vmvisor/mpa' released. Waiting for /usr/lib64/vmware/nsx-mpa/mpa to start... Waiting for /usr/lib64/vmware/nsx-mpa/mpa to start... Waiting for /usr/lib64/vmware/nsx-mpa/mpa to start... Waiting for /usr/lib64/vmware/nsx-mpa/mpa to start... Waiting for /usr/lib64/vmware/nsx-mpa/mpa to start... Unable to start /usr/lib64/vmware/nsx-mpa/mpa It is not safe to continue. Please reboot the host immediately to discard the unfinished update. Please refer to the log file for more details.
