Example for Configuring Static VXLAN in an Active-Active Scenario (Layer 2 Communication)

In a scenario where a data center is interconnected with an enterprise site, a CE is dual-homed to a VXLAN network. Carriers can enhance VXLAN access reliability to improve the stability of user services so that rapid convergence can be implemented in the case of a fault.

Networking Requirements

On the network shown in Figure 1, CE1 is dual-homed to PE1 and PE2 through an Eth-Trunk. PE1 and PE2 use the same virtual address as the source VTEP address of an NVE interface, namely, an anycast VTEP address. In this way, the CPE is aware of only one remote NVE interface and establishes a static VXLAN tunnel with the anycast VTEP address.

The packets from the CPE can reach CE1 through either PE1 or PE2. However, single-homed CEs may exist, such as CE2 and CE3. As a result, after reaching a PE, the packets from the CPE may need to be forwarded by the other PE to a single-homed CE. Therefore, a bypass VXLAN tunnel needs to be established between PE1 and PE2.

Figure 1 Networking for configuring static VXLAN in an active-active scenario (Layer 2 communication)

Interfaces 1 through 3 in this example represent GE 0/1/1, GE 0/1/2, and GE 0/1/3, respectively.

**Table 1** Interface IP addresses
Device	Interface	IP Address
PE1	GE 0/1/1	10.1.20.1/24
	GE 0/1/2	-
	GE 0/1/3	10.1.1.1/24
	Loopback 1	1.1.1.1/32
	Loopback 2	3.3.3.3/32
PE2	GE 0/1/1	10.1.20.2/24
	GE 0/1/2	-
	GE 0/1/3	10.1.2.1/24
	Loopback 1	2.2.2.2/32
	Loopback 2	3.3.3.3/32
CE1	GE 0/1/1	-
CE1	GE 0/1/2	-
CPE	GE 0/1/1	10.1.1.2/24
	GE 0/1/2	10.1.2.2/24
	GE 0/1/3	-
	Loopback 1	4.4.4.4/32

Configuration Roadmap

The configuration roadmap is as follows:

Configure an IGP on the PEs and CPE to implement network connectivity.
On PE1 and PE2, Configure service access points and set the same ESI for the access links of CE1 so that CE1 is dual-homed to PE1 and PE2.
Configure the same virtual anycast VTEP address on PE1 and PE2 as the source NVE interface address to establish a VXLAN tunnel with the CPE. Establish static VXLAN tunnels between the PEs and CPE so that the PEs and CEP can communicate.
Establish an EVPN peer relationship between PE1 and PE2 to receive and send VXLAN EVPN routes.
Configure EVPN instances in BD mode on PE1 and PE2 and bind the BD to the corresponding EVPN instances.
Enable the inter-chassis VXLAN function on PE1 and PE2, configure different bypass addresses for PE1 and PE2, and establish a bypass VXLAN tunnel on PE1 and PE2 so that PE1 and PE2 can communicate.
(Optional) Configure a UDP port on the PEs to prevent the receiving of replicated packets.
Configure a BD on PE1 and PE2.
On PE1 and PE2, enable routes to be sent to carry extended community attributes and the function of redirecting received routes carrying the extended VLAN community attribute.
On PE1 and PE2, enable FRR for MAC routes between the local and remote ends. When a PE fails, the downstream traffic of the CPE can quickly switch to the other PE.
(Optional) When PE1 and PE2 establish an EBGP peer relationship, set the function of not changing the next-hop addresses of routes. When PE1 and PE2 establish an IBGP peer relationship, this function is not required.

Data Preparation

To complete the configuration, you need the following data:

Interfaces and their IP addresses
Names of VPN and EVPN instances
VPN targets of the received and sent routes in VPN and EVPN instances

Procedure

Assign an IP address to each interface on each node, and configure loopback interface addresses.
For detailed configurations, see Configuration Files.
Configure an IGP. In this example, IS-IS is used.
For detailed configurations, see Configuration Files.

Enable EVPN capabilities.

# Configure PE1.

<PE1> system-view
[~PE1] evpn
[*PE1-evpn] vlan-extend private enable
[*PE1-evpn] vlan-extend redirect enable
[*PE1-evpn] local-remote frr enable
[*PE1-evpn] bypass-vxlan enable
[*PE1-evpn] quit
[*PE1] commit