Reference Guide

2. Trace route across VLT domains may show extra hops.
3. IP route symmetry must be maintained across the VLT domains. Assume if the route to a destination is not available at C2,
though the packet hits the MY_STATION_TCAM and routing is enabled for that VLAN, if there is no entry for that prefix in
the routing table it will dropped to CPU. By default, all route miss packets are given to CPU. To avoid this static entry must
be configured.
4. There could be L3 frames received out-of-order at the L3 cloud, when a MAC is removed and added back. This could happen
when proxy-routing and sub-optimal routing intersperse each other.
5. This feature is not supported for IPv6.
6. ICL shut – Assume ICL between C1 and D1 is shut and if D1 is secondary VLT then one half of the inter DC link goes down.
After vm motion, If a packet reaches D2 with the destination MAC address of D1, it may be dropped. This behaviour is
applicable only in the LLDP configuration; In static configuration, the packet will be forwarded.
7. Any L3 packet that was originally should have been switched across domains, when gets a hit at my_station_tcam (because
of this feature) and routed, will have a TTL decrement as expected.
8. Packet duplication – Assume exclude-vlan (say VLAN 10) is configured on C2/D2 for C1’s MAC. If packets for VLAN 10 with
C1’s MAC get a hit at C2, they will be switched to both D2 (via ICL) and C1 via inter DC link. This could lead to packet
duplication. So, if C1’s MAC is learnt at C2 then the packet would not have flooded (to D2) and only switched to C1 and thus
avoided packet duplication.
Configuring an LLDP VLT Proxy Gateway
You can configure a proxy gateway in a VLT domain to locally route packets destined to a L3 endpoint in another VLT domain.
To configure an LLDP proxy gateway:
834
VLT Proxy Gateway