What is the correct way to map a NSX-T 3.x Uplink Profile + Transport Node Profile to a VDS 7.0 using LACP?
Lets say I have in my vCenter a VDS 7.0 (eg. named VDS1) with 1 LACP uplink (named lag1, 2 ports per ESXi - lag1-0, lag1-1).
Should I create a Uplink Profile (eg. named ULProfile) with a single teaming uplink (Failover Order, active uplinks = uplink1, standby uplinks = empty) and map this under a Transport Node profile as uplink1 -> lag1 (after choosing VDS -> VDS1 and Uplink profile ULProfile)?
Or should the Uplink Profile have two active uplinks (uplink1, uplink2) and these be mapped in the Transport Node profile as uplink1 -> uplink1 (lag1-0) and uplink2 -> uplink2 (lag1-1)?
Can't seem to find any documentation related to this.
Is there a reason you're using lags to the host? They're not needed or recommended.
Can make troubleshooting and deterministic paths more difficult
Lets just say that we prefer it that way in our current setup and we have all the necessary bells and whistles setup on the L2/L3 network side.
Our lab env. is currently not configured to test this (undergoing some other testing) and that's why I thought about asking in here. VMwares own documentation seems a bit lacking on this subject or my google-fu skills are not up to par...
Any specific reason why you are not interested in multi TEP design for overlay traffic? This will result in Active-Active overlay traffic without any operational complexity and most importantly no changes required in the physical network. I would suggest testing this in your lab and take a final call.