L3 DCI link between DCs

[LingQin]

THere is a L3 DCI link between two DCs. Can NSX-T leverage on this link to form a stratched network without addtional L2 link in between? like VDS 1 in DC 1 geneve stretch to VDS 2 in DC 2? so that server 1 connecting VDS 1 can be in same subnet as server 2 connecting to VDS 2.

[Sreec]

Yes, that will work as long MTU requirements are also met.

[LingQin]

Does that mean NSX-T is different with NSX-V. For NSX-V, it requires a trunk link between hosts for DLS to communicate, even it applies to host in different DCs.

[Sreec · Accepted solution]

Well , all we need is a IP connectivity with MTU . L2/L3 is not a concern and we could even run an overlay.

[tanurkov]

Yes it can !

as long there is connectivity between them and transport zone spans across two switches so segments can span both sides. Remember boundary is span of transport zone not vds it seltf

[p0wertje]

Please do take in account that if DC1 is in London and DC2 in paris, it will prob be not be the best way of doing it.

I think it is still possible though.

In that case it is better to look a federation.

There is a good vmworld session available for that VCNC1178D

Federation is not quiet ready for real production though. But that soon will be the case.

If the DC is close-by, i.e Amsterdam region, it will work fine. All trafic will exit over the edge-nodes, so keep in mind you will have cross-dc traffic.

[tanurkov]

there is no need for Federation (which correctly notices under technical review) You can use also Multisite

[LingQin]

In my case, both DCs got only one exit which is the Internet link (no dedicated link for DCI links). Under such circumstance, what the design will be looked like in term of T0 outside interface (the real exit) and DCI link between both DCs carrying stretched traffic between VDS 1 in DC 1 and VDS 2 in DC2. sharing same physical interface or better to be dedicated interface? or i can do a vpn between both T0? thanks in advance.