Users Guide

information about the eVLT, see the Virtual Link Trunking (VLT) chapter. The core or Layer 3 routers C and D in local VLT
Domain and C1 and D1 in the remote VLT Domain are then part of a Layer 3 cloud.
Figure 140. 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
VLT Proxy Gateway 956