This is resolved in the nsx-t 3.1

https://fojta.wordpress.com/2020/11/12/nsx-t-3-1-sharing-transport-vlan-between-hosts-and-edge-nodes...

Ah, nice, I've just downloaded the upgrade bundle and will see if it works.

If you would like a bit more of an understanding as to the what and why this was an issue in the past, you may find this article useful as well.

NSX-T 3.1 Tunnel Endpoints | Inter TEP

I've deployed a fresh 3.1 environment, configured my transport nodes, Tier-0, Tier-1 and attached a few segments, but as soon as I add a VM to a segment, the tunnel becomes degraded.

I want to run a "collapsed" *environment now, where the TEP vmkernels run on the vds too and getting this ocnfiguration to work was my goal with the 3.1 update.

I guess the error is somewhere in the transport node (TEP) configuration, which I have to figure out now...

It sounds like you want to configure inter TEP, the above article walks through that and tells you how to configure it and how to test to make sure your tunnels are working.

Have you been through it?

I have followed another guide, yes, your link reutrns a 404

interesting,  if you're still wanting some details around this, try this one it should work.

https://www.lab2prod.com.au/2020/11/nsx-t-inter-tep.html

What do your BFD statuses report under the edge cluster?

"0 - No Diagnostic"

If you would like some more assistance.

Happy look at it over zoom, just let me know.

We can look at the steps you've tried and work forwards.

Thank you  for the offer, however this is not something that would be allowed in my environment:) I'll have to wait for GSS to finally respond to my SR.

Have you done all the vmkpings to check it all works?

So, normally this would indicate that the tunnel source and destination could not complete at the N-VDS specified MTU. This is pretty common in new builds because the actual MTU check doesn't occur until the tunnel is needed.

It'd be really cool if we could have some kind of "post-implementation network test"!

Anyhow, for the tunnel that is failing you want to run a vmkping against it with the DNF bit set and MTU set to 1600+:

vmkping -d -I vmk10 -s 1600 <the other end>

https://kb.vmware.com/s/article/1003728

That will work, so I generally use vmkping ++netstack=vxlan <dstIP> -s 8972 -d

Yep - the use of `vxlan` in this case feels...distasteful...so I don't use it

You're hitting the same bug that the rest of us always do when getting started with this platform.  Host and Edge TEPs cannot coexist on the same switch with the same physical network adapters.

VMware won't admit this is a bug, but they "fixed" it in 3.1.  

One workaround we were using was to put the Edge TEP on a Standard vSwitch with separate physical NICs, and leave the Host TEPs on the VDS.  This works fine, and you can then have a single Geneve VLAN, but traffic between Host and Edge TEP still needs to go through the top of rack switch, even if it's on the same physical host.

If you can't afford the extra physical NICs, then you had to use an external router to route between your Host TEP and Edge TEP networks, which was, of course, ridiculous.  After all, we're building software defined networks here!

Again, however, VMware has "fixed" this in 3.1 and you should be able to put everything on a single network now.

Technically not a bug, however as you mentioned the feature didn't exist in earlier versions. 

The explanation can be seen in the link that i posted earlier.

I've just downloaded the upgrade bundle and will see if it works

Speed Test