Service Manual

11. VRRP and IPv6 routing is not supported.
12. Private VLANs (PVLANs) are not supported.
13. When a Virtual Machine (VM) moves from one VLT domain to the another VLT domain, the VM host send the gratuitous ARP
(GARP) , which in-turn triggers a mac movement from the previous VLT domain to the newer VLT domain.
14. After a station move, if a host sends a TTL1 packet destined to its gateway; for example, a previous VLT node, the packet may
be dropped.
15. After a station move, if a host rst PINGs its gateway; for example, a previous VLT node it results a 40 to 60% success rate
considering it takes a longer path.
16. L3 frames can be received out-of-order at the L3 cloud when you remove and add back a MAC. This can happen when proxy
gateway routing and sub-optimal routing intersperse witth each other.
Enabling the VLT Proxy Gateway
To enable the VLT Proxy Gateway feature, the system mac addresses of C and D in the local VLT domain must be installed in C1 and
D1 in the remote VLT domain and vice versa. You can install the mac address in two methods - the proxy-gateway lldp
method or the proxy-gateway static conguration. Proxy-gateway LLDP is a dynamic method of installing the local mac
addresses in the remote VLT domain, which is achieved using a new organizational TLV in LLDP packets.
The VLT proxy gateway can be congured in a VLT domain context using the cli command proxy-gateway LLDP. You enter the
proxy-gateway Conguration mode when you enter this command. The port-channel interface of the square VLT link on which LLDP
packets are to be sent is specied by thepeer-domain-link port-channel command.
Conguring the proxy gateway lldp and the peer-domain-link port channel, LLDP sets TLV ags on the interfaces for
receiving and transmitting private TLV packets. After dening these organizational TLV settings, LLDP encodes the local system
mac-addresses as organizational TLVs for transmitting to the peer. If you specify the no proxy gateway LLDP interface
command, LLDP stops transmitting and receiving proxy gateway TLV packets on the specied interfaces. However, other TLVs are
not aected. From the interfaces on which proxy gateway LLDP is enabled, LLDP decodes TLV packets from the remote LLDP by
using the new organizational TLV.
The following requirements must be satised for LLDP proxy gateway to function correctly:
• As LLDP is a direct link protocol, data centers must be directly connected.
• LLDP has a limited TLV size. As a result, information that is carried by this new TLV is limited to only one or two MAC addresses.
• You must ensure proper conguration and physical setup on all related systems.
LLDP Organizational TLV for Proxy Gateway
Dene a new organizational TLV :
• LLDP denes an organizationally specic TLV (type 127) with an organizationally unique identier (0x0001E8) and
organizationally dened subtype (0x01) for sending or receiving this information.
• LLDP will uses the existing infrastructure and adds the new TLV, and sends and receives only on the congured ports.
• There are only a couple of MAC addresses for each unit to transmit so all currently active MAC addresses are carried on the
newly dened TLV.
• This TLV is recognizable only by Dell Networking devices with this feature support. Other device ignore this eld and are able to
process other standard TLVs.
The LLDP organizational TLV passes local destination MAC address information to peer VLT domain devices so they can act as the
proxy gateway. Two congurations are required to enable Proxy Gateway LLDP:
• Global proxy gateway LLDP conguration to enable this feature
• Interface proxy gateway LLDP conguration to enable/disable proxy-gateway LLDP TLV on particular interfaces
• The interface is typically a VLT port-channel which connects to a remote VLT domain
VLT Proxy Gateway
785