NSX-T 3.1 North-South routing

[emistery]

Hi all,

I'm pretty new to NSX-T, and trying to set up a lab to gain some knowledge about it. I already set up some segments with VMs connected to it, a T1 router and a T0 router. The VMs can reach the uplink interface of the T0 router, but no further (the physical router). What are some troubleshooting steps I could try to do? All suggestions or tips are welcome.

[emistery]

I did that, but I cannot choose them as uplink profiles on the edge node.

[shank89]

You'll have to edit the nodes is fabric settings,  then select it under uplink profiles in the node configuration section

[emistery]

It literally does not allow me to choose custom uplink profiles. Only the default ones without VLANs

[shank89]

Can you post screenshots of the profiles and the process you're following?

[shank89]

Also I assume you haven't got any licensing issues?

[emistery]

The uplink profiles.

[emistery]

Here you can see I can only select the 2 default uplink profiles.

[shank89]

You can actually use load balance source with two active uplinks for the edge.  Not sure if that's causing you the issue, but worth a.shot. 

[emistery]

Yes, now I'm able to select the uplink profile. Meanwhile I changed so much while troubleshooting the TEPs between the hosts and edge doesn't work anymore 😅. Also while applying the uplink profile and selecting adapters, I got the following error:

[VTEP-vlan of TransportNode/500c47f9-6162-4c11-b296-2500bbb5e210] and [Logical-Switch-vlan of d0ecf169-8b7a-42e5-adc8-d662dec6789f] having same vlan-ids:160 in same underlying Edge host-switch is not allowed. Change vlan configuration. (Error code: 8331)

I cannot quite follow what's going wrong here.

[shank89]

Sounds like double tagging,  copy the uuid into the search and see if you can unwind. 

[shank89]

Ensure the hosts are tagged correctly and edges,  then make sure they can ping their own Gateways and then each others. 

It's either going to be a vlan issue, routing issue or mtu issue,  needs 1600 at least without fragmentation. 

[shank89]

May be worthwhile to start again and follow something like this.  https://shuttletitan.com/nsx-t/nsx-t-installation-series/nsx-t-installation-series-step-9-configure-...

[emistery]

The first uuid is of the t0 uplink segment, and the second one is the edge node. Where should I untag?

[emistery]

Thanks, I'm probably gonna remove everything in NSX-T and start again.

My setup is based on:

http://keithlee.ie/2018/11/24/pks-nsx-t-home-lab-part-8-configure-nsx-t/ & https://sivasankar.org/2020/3032/vmware-nsx-t-preparing-transport-nodes-and-segments/

[shank89]

The edge node should only have trunks not the tagged vlan segment 

[shank89]

Sounds like a plan, at least now you know it was likely wiring. 

If you found any of these responses to be adequate, please mark the thread as solved and kudo posts you deemed helpful. 

Thanks for assisting with troubleshooting!

[emistery]

Thanks. Can I continue this thread if I need assistance with the same problem again?

[shank89]

Sure, no worries, if it is related to the same issue you should!

However, I imagine since you know where the fault was and have a guide, you should be Ok 🙂

[emistery]

Hi Shank,

I solved a part of the issue by creating a seperate VLAN for edge TEP, since the edge TEP and host TEP can't be on the same subnet apparently. Now the T0 can ping to WAN.

However, now the vms on a segment connected to the T1 router, which is connected to the T0 router, cannot reach WAN. And all the pings I get are DUP. Do you have an idea?

[shank89]

The DUP pings is likely to do with nesting and the security options enabled on the portgroup.
When you do a traceroute from the VM towards the WAN, where is it getting stuck?