Concept Guide

In this topology, P2 and P3 in VTEP 1 are VLT port-channels with corresponding VLT peer LAGs being P2 and P3 in VTEP 2. Similarly, P6
and P7 in VTEP 3 are VLT port-channels with corresponding VLT peer LAGs being P6 and P7 in VTEP 4.
NOTE: P2, P3, P6, and P7 can be a single port or multi-port port-channels that are VLT port-channels.
NOTE: The VLT VXLAN conguration for RIOT deviates from the standard VLT behavior when these physical loopbacks are
provisioned as VLT port-channels.
VXLAN RIOT with Internal Loopback
To facilitate it’s working in a VLT environment, the loopback port channel should be provisioned as VLT port channels with a peering
relationship. For instance, in the topology below , P2 in VTEP 1 should be a VLT port-channel with it’s corresponding vlt-peer-lag being P2
on VTEP 2, and similarly P6, etc., :
For VLT, in addition to the masks specied earlier, the VLT specic mask, to disallow frames that ingress on an ICL from going out of a VLT
port channel would be permanently in place. These masks won’t be removed for the loopback ports even if the VLT peer LAG goes down
(this is a deviation from standard VLT behavior, when these loopbacks are provisioned as VLT port-channels.).
NSX Controller-based VXLAN for VLT
Apart from static VXLAN for VLT, you can also use an NSX controller for VXLAN in a VLT setup. The following illustration depicts a VXLAN
setup in a VLT topology. With this setup, VXLAN switch happens across data centers.
Virtual Extensible LAN (VXLAN)
1165