White Papers

Table Of Contents
In this RIOT scheme, whenever R1 tries to reach R2, the packet gets to P1 on VTEP 1 with VLAN 10 and gets routed out of P2 on VLAN
20. VTEP 1 sends an ARP request for R2 (10.1.2.1) through P2. This request gets VXLAN encapsulated at P3 and is sent out of P4.
Eventually, the native ARP request reaches R2.
R2 sends an ARP response that is VXLAN encapsulated at VTEP 2. This response reaches VTEP 1 on P4 with a VXLAN encapsulation. At
this point, the ARP response is de-capsulated at P4. The native ARP response egresses through P3 and re-enters through P2. The ARP is
then resolved pointing to P2.
After this ARP discovery is complete, the existing routing and VXLAN encapsulation mechanisms facilitate routing over VXLAN tunnels
between R1 and R2.
NOTE
: VXLAN RIOT with loopback is not supported in a stacking environment.
Restrictions
The topology to achieve RIOT with a physical loopback is inherently susceptible to Layer 2 loops. To prevent these loops from disrupting the
network, the following egress masks need to be applied:
Any frame ingressing on a VXLAN access port is not allowed to egress out of a VXLAN loopback port.
Any frame ingressing on a VXLAN loopback port is not allowed to egress out of a VXLAN access port.
Any frame ingressing on a Non-VXLAN loopback port is not allowed to egress out of a VXLAN access port.
Any frame ingressing on a Non-VXLAN loopback port is not allowed to egress out of a VXLAN loopback port.
Routing protocols and other control protocols like VRRP are not supported over a VXLAN tunnel.
While 4000 VLANS or VNIDs are supported in a Layer 2 context; for VXLAN RIOT, the number of VLANS or VNIDs supported is limited to
1000.
Virtual Extensible LAN (VXLAN)
1093