Service Manual
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. You must enable the VLT peer-routing command for the VLT proxy gateway to function.
3. The current design does not handle asymmetric virtual local area network (VLAN) conguration scenarios such as the same
VLAN congured with L2 mode on one VLT domain and L3 mode on another VLT domain. You must always congure 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 Conguration
Example
6. Trace route across DCs may show extra hops.
7. You must maintain route symmetry across the VLT domains to ensure no trac 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 trac. Because routing
protocols are enabled and both DCs come in the same subnet, there is no route asymmetry dynamically. But if you congure
the static route on one DC and not on the other, there is asymmetry.
8. If the port-channel specied in theproxy-gateway command is not a VLT LAG, the conguration is rejected by the CLI. VLT
LAG to a legacy LAG when it is part of 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.
784
VLT Proxy Gateway