No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - VXLAN

CloudEngine 12800 and 12800E V200R003C00

This document describes the configurations of VXLAN.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring VXLAN in Centralized Gateway Mode Using BGP EVPN

Configuring VXLAN in Centralized Gateway Mode Using BGP EVPN

When VXLAN in centralized gateway mode using BGP EVPN is deployed, traffic across network segments is forwarded through Layer 3 VXLAN gateways to implement centralized traffic management.

Usage Scenario

An enterprise may allocate VMs in different locations to a tenant. Some of the VMs reside on the same network segment, and the others reside on different network segments. To allow communication between these VMs, Layer 2 and Layer 3 VXLAN gateways need to be deployed and VXLAN tunnels need to be established.

On the network shown in Figure 8-4, Server 2 and Server 3 belong to the same network segment and access the VXLAN through Device 1 and Device 2, respectively; Server 1 and Server 2 belong to different network segments and both access the VXLAN through Device 1.
  • To enable communication between VM 1 on Server 2 and VM 1 on Server 3, deploy Layer 2 VXLAN gateways on Device 1 and Device 2 and establish a VXLAN tunnel between Device 1 and Device 2 so that tenants on the same network segment can communicate.
  • To enable communication between VM 1 on Server 1 and VM 1 on Server 3, deploy a Layer 3 VXLAN gateway on Device 3 and establish VXLAN tunnels between Device 1 and Device 3 and between Device 2 and Device 3 so that tenants on different network segments can communicate.

Either IPv4 or IPv6 addresses can be configured for the VMs and Layer 3 VXLAN gateway. This means that a VXLAN overlay network can be an IPv4 or IPv6 network. Figure 8-4 shows an IPv4 overlay network.

Figure 8-4 VXLAN in centralized gateway mode

Prerequisites

Before configuring a VXLAN tunnel in centralized gateway mode, ensure that routes are reachable at Layer 3.

Configuration Process

NOTE:

In a VXLAN dual-active access scenario, two dual-homing devices are simulated as a VTEP node to prevent loops or MAC address flapping. Therefore, ensure that the two dual-homing devices have the same configurations of the VXLAN service access point and VXLAN tunnel.

Figure 8-5 Flowchart of configuring VXLAN in centralized gateway mode

NOTE:

If only VMs on the same network segment need to communicate with each other, Layer 3 VXLAN gateways do not need to be deployed. If VMs on different network segments need to communicate with each other or VMs on the same network segment need to communicate with external networks, Layer 3 VXLAN gateways must be deployed.

The following table lists the differences between the centralized gateway configuration procedures for an IPv4 overlay network and an IPv6 overlay network.

Configuration Task

IPv4 Overlay Network

IPv6 Overlay Network

Configure a Layer 3 VXLAN gateway.

Configure an IPv4 address for a VBDIF interface of the Layer 3 VXLAN gateway.

Configure an IPv6 address for a VBDIF interface of the Layer 3 VXLAN gateway.

(Optional) Configure ARP broadcast suppression.

Supported

Not supported

(Optional) Configure limits of static ARP/IPv6 neighbor/MAC address entry learning and MAC address learning.

Configuring static IPv6 neighbor entries is not supported.

Configuring static ARP entries is not supported.

(Optional) Configure Layer 2 proxy ARP.

Supported

Not supported

Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004207

Views: 29763

Downloads: 66

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next