I ran into the same issue as described by Eric Sloof:
https://www.ntpro.nl/blog/archives/3570-Edge-Tunnels-Down-when-hosting-NSX-T-on-the-same-DVS.html
The problem I had was i did not have enough uplinks to create a new dvSwitch to get the tunnel to work. For the tunnel to work, the geneve traffic has to leave the host and get routed back in. I had a layer 3 physical switch and decided to make use of inter-vlan routing.
Once logged into the switch:...
Some notes from a recent lab I configured:
My current lab looks like this - I have few production VMs in one VLAN segment External network access and Internet access is through another VLAN segment There is a jumpbox VM that is uplinked to both the VLAN segments. VMware vDS is currently being used and there are no free uplinks to make use of nvds. What do I want to accomplish?...
I accidentally used the wrong VLAN on a portgroup in vDS while playing with NSX-T.(long story) This caused vCenter to lose access to all the hosts in a cluster.
There is a KB article that goes through a few hoops before we can get the hosts back into vCenter Server, Recovering from a management portgroup VLAN misconfiguration on a vNetwork Distributed Switch (vDS)
To resolve the issue,
As i still had access to vCenter, after configuring the right vlan in vCenter I used net-dvs to manually change the vlan on each vmkernel interface....
I recently lost access to few of my ESXi hosts after using the incorrect VLAN on the dvSwitch portgroup. Was unable to find any command to change the VLAN of a dvSwitch portgroup from the command line.
Luckily I came across the Network Restore Option in DCUI
To restore VDS from DCUI:
Connect to the DCUI. From the Network Restore Options menu, select Restore vDS. Type the correct values for VLAN uplink and blocked properties, where appropriate....