Edge Tunnels Down when hosting NSX-T on the same DVS

[lyanthony]

Hello All,

When testing NSX-T, I came across the issue described in the following post:

https://www.ntpro.nl/blog/archives/3570-Edge-Tunnels-Down-when-hosting-NSX-T-on-the-same-DVS.html

The solution in the post was to create a 2nd vDS and move the Edges onto that vDS, which in my lab does work fine.

However my existing production ESXi hosts are configured with only 2 x 10GB uplinks for production traffic which would be configured on a single vDS, I do not have the option of adding additional 10GB physical nics just to accommodate the NSX-T Edges, and taking one 10GB uplink from the production vDS isn't a viable option as I lose network redundancy.

What are the options to allow both the host vmk10 geneve TEPs and the Edge uplinks to run within the same vDS? I'm using NSX-T 3.1.3 and vSphere 7.0.

Thanks in advance for any suggestions.

[parkersm · Accepted solution]

Are the hosts and edges on the same vlan/subnet? If so you can utilize a single vDS and use inter TEP communication. You would need to make sure that the fp-eth interfaces with tep traffic are connected to vlan-backed NSX segments, and not to vDS native port groups. This article provides a good example: https://www.lab2prod.com.au/2020/11/nsx-t-inter-TEP.html#more 

[lyanthony]

Hello @parkersm . Yes the hosts and edges were on the same vlan/subnet. I ran through the provided link and following the instructions to use segments to connect the NSX Edges instead of the vDS portgroups I was able to resolve the problem.

Thanks for the help.