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).
Using VXLAN to Implement DCI

Using VXLAN to Implement DCI

Usage Scenario

To meet the requirements of geographical redundancy, inter-regional operations, and user access, an increasing number of enterprises are deploying data centers (DCs) across multiple regions. Data Center Interconnect (DCI) is a solution that enables intercommunication between the VMs of multiple DCs. Using technologies such as VXLAN and BGP EVPN, DCI securely and reliably transmits DC packets over carrier networks. With DCI, intercommunication between the VMs of multiple DCs is possible regardless of whether these VMs reside on the same VLAN.

Three DCI solutions are currently available: end-to-end VXLAN, VLAN hand-off, and segment VXLAN. These solutions are described in the following table.
Table 10-1 DCI interconnection solutions

Solution

Scenario

Functionality

Advantage

Disadvantage

Using End-to-End VXLAN to Implement DCI

One end-to-end VXLAN tunnel is established between two DCs.

This solution is recommended for small-scale DCs.

  • Layer 2 interconnection is implemented between VMs on the same subnet.
  • Layer 3 interconnection is implemented between VMs on different subnets.
  • The VXLAN tunnel is logically created within a DC and is easy to configure and maintain.
  • DCI devices are not required to maintain tenant MAC or IP address information.
  • The VNI and the routing protocols used in all DCs must be identical.
  • The VXLAN settings, including tenant MAC addresses, IP routing information, and RTs, for different DCs must be planned uniformly.
Using VLAN Hand-off to Implement DCI

One VXLAN tunnel is established in each DC. One VXLAN tunnel is also established between the DCI-VTEPs. Leaf nodes deployed on the edge of the DC network provide VLAN access for services. DCI-VTEPs process these services and send them to the peer DC.

This solution is recommended for large-scale, modular DCs.

Layer 2 interconnection is implemented between VMs on the same subnet.

  • The routing protocols running in different DCs are independent. DCs are not required to use the same protocols.
  • VXLAN can encapsulate different information in different DCs. The solution is architecture-agnostic and allows interconnection between heterogeneous DCs.
  • It is not necessary to orchestrate information between DCs.
  • Bandwidth, policy, and broadcast storm control can be conveniently performed at the DCI ingress.
  • Performance requirements on DCI devices are high. DCI devices are required to maintain tenant MAC and IP address information.
  • Inter-DC communication is possible only for services on the same subnet.
Using Segment VXLAN to Implement DCI

One VXLAN tunnel segment is established in each of the two DCs. One VXLAN tunnel segment is also established between the DCs.

This solution is recommended for large-scale, modular DCs.

  • Layer 2 interconnection is implemented between VMs on the same subnet.
  • Layer 3 interconnection is implemented between VMs on different subnets.
  • The routing protocols running in different DCs are independent. DCs are not required to use the same protocols.
  • VXLAN can encapsulate different information in different DCs. The solution is architecture-agnostic and allows interconnection between heterogeneous DCs.
  • It is not necessary to orchestrate information between DCs.
  • The solution uses Layer 3 interconnection, which reduces Layer 2 flooding and prevents broadcast storms in one DC from affecting other DCs.
  • Performance requirements on DCI devices are high. DCI devices are required to maintain tenant MAC or IP address information.
  • It is necessary to maintain multiple VXLAN tunnel segments, which increases the complexity of O&M.

Pre-configuration Tasks

Before configuring VXLAN to implement DCI, complete the following task:

  • Configure an IGP in DC A and DC B.

    NOTE:

    Check that BDs do not need to be configured on DC edge devices (Leaf 2 and Leaf 3). BD configurations do not affect the creation of a VXLAN tunnel between Leaf 2 and Leaf 3 in a distributed gateway (BGP EVPN) scenario. But in this scenario, VMs attached to Leaf 2 or Leaf 3 cannot access the network through Layer 2 sub-interfaces associated with a BD.

Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004207

Views: 24993

Downloads: 65

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