6
Restrictions and guidelines
DRNI configuration
When Leaf 1 and Leaf 2 create VXLAN tunnels over the IPL, the tunnel source IP address is
the virtual VTEP address of the DR system. The tunnel destination IP address is the VTEP
address of the local leaf device. When traffic from a single-homed server is forwarded from
one DR member to the other DR member through a VXLAN tunnel created on the IPL, the
latter DR member cannot decapsulate the traffic. To resolve this issue, use the vxlan
default-decapsulation source interface loopback 0 command on the latter DR
member so that the DR member can decapsulate the traffic.
In this example, Leaf 1 is the primary device and Leaf 2 is the secondary device in the DR
system. When the IPL is disconnected, the links connecting Leaf 1 to Sever A and Sever B are
also disconnected. However, the EBGP connections to Sever A and Sever B go down only
when the BGP peer relationship expires. The convergence time is up to dozens seconds and
even more than 100 seconds. To resolve this issue, use the drni mad include interface
command on Leaf 1 to add the interfaces connected to Server A and Server B to the
user-configured list of included ports. The interfaces will be shut down by DRNI MAD when the
DR system splits.
When GIR is configured on a DR member device and the DR member device is isolated, traffic
from single-homed interfaces on the DR member device still can be forwarded to a leaf device.
In an EVPN distributed relay network, AC interfaces and VSI interfaces support QoS rate limit.
To avoid packet loss or other forwarding issues when the secondary device that has a large
number of entries or is being upgraded joins the DR system, use the drni restore-delay
command to increase the data restoration interval.
Routing configuration
You can configure a router ID for an OSPF process or BGP instance. If you do not configure a
router ID, the OSPF process or BGP instance uses the global router ID. Make sure the router
ID for each device is unique in the network.
For the remote leaf and border devices to establish tunnels only with the DR system
(represented by the virtual VTEP address), use the nexthop evpn-drni group-address
command in BGP EVPN address family view on the DR member devices. When this command
is used, the VXLAN tunnels established between the DR member devices go down. To resolve
this issue, configure a routing policy for each DR member device to use its local VTEP address
as the next hop of BGP EVPN routes advertised to the other DR member device. The following
information shows the settings:
#
route-policy 1 permit node 1
if-match route-type bgp-evpn-ip-prefix
apply ip-address next-hop 1.1.1.1
#
route-policy 1 deny node 10
#
bgp 20
address-family l2vpn evpn
nexthop evpn-drni group-address
peer 2.2.2.2 route-policy 1 export
#