Administrator Guide

Figure 148. VLT Proxy Gateway — Topology 1
Guidelines for Enabling the VLT Proxy Gateway
Keep the following points in mind when you enable this functionality:
1. The proxy gateway is supported only for VLT; for example, across VLT domain.
2. To get full benefits out of proxy gateway, peer-routing is recommended
3. The current design does not handle asymmetric virtual local area network (VLAN) configuration scenarios such as the same
VLAN configured with L2 mode on one VLT domain and L3 mode on another VLT domain. Configure the same mode for the
VLANs across the VLT domain.
4. You must maintain VLAN symmetry within a VLT domain.
5. The connection between DCs can only be a L3 VLT in eVLT format. For more information, refer to the eVLT Configuration
Example
6. Trace route across DCs may show extra hops.
7. You must maintain route symmetry across the VLT domains to ensure no traffic drops. When the routing table across DCs is
not symmetrical, there is a possibility of a routing miss by a DC that does not have the route for the L3 traffic. Because
routing protocols are enabled and both DCs come in the same subnet, there is no route asymmetry dynamically. But if you
configure the static route on one DC and not on the other, there is asymmetry.
8. If the port-channel specified in theproxy-gateway command is not a VLT LAG, the configuration is rejected by the CLI.
The VLT LAG cannot be configured as a legacy LAG when it is part of a proxy-gateway
9. You cannot change the LLDP port channel interface to a legacy LAG when you enable the proxy gateway.
10. Dell recommends using thevlt-peer-mac transmit command only for square VLTs without diagonal links.
11. VRRP and IPv6 routing is not supported.
12. Private VLANs (PVLANs) are not supported.
VLT Proxy Gateway
1003