Install Guide

Table Of Contents
NOTE: You must configure a virtual link local (fe80) address for each VRRPv3 group created for an interface. The VRRPv3
group becomes active as soon as you configure the link local address. Afterwards, you can configure the groups virtual
IPv6 address.
NOTE: The virtual IPv6 address you configure should be the same as the IPv6 subnet to which the interface belongs.
NOTE: Although R2 and R3 have the same default priority (100), R2 is elected master in the VRRPv3 group because the
interface has a higher IPv6 address than the interface on R3.
Proxy Gateway with VRRP
VLT proxy gateway solves the inefficient traffic trombone problem when VLANs are extended between date centers and when
VMs are migrated between the two DCs. Starting from Dell EMC Networking OS 9.14.0.0, VRRP provides a much simpler
method to solve the traffic trombone problem.
This is achieved by configuring same VRRP group IDs to the extended L3 VLANs and VRRP stays active-active across all four
VLT nodes even though they are in two different VLT domains.
The following illustration shows a sample configuration with two data centers:
Server racks, Rack 1 and Rack 2, are part of data centers DC1 and DC2, respectively.
Rack 1 is connected to devices A1 and B1 in a Layer 2 network segment.
Rack 2 is connected to devices A2 and B2 in a Layer 2 network segment.
A VLT link aggregation group (LAG) is present between A1 and B1 as well as A2 and B2.
A1 and B1 are connected to core routers, C1 and D1 with VLT routing enabled.
A2 and B2 are connected to core routers, C2 and D2, with VLT routing enabled.
Virtual Router Redundancy Protocol (VRRP)
943