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 - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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).
VXLAN Deployment Solution (VMware NSX Controller Mode)

VXLAN Deployment Solution (VMware NSX Controller Mode)

The device supports configuration of the virtual extensible LAN (VXLAN) network and bidirectional forwarding detection (BFD) for VXLAN through the VMware NSX controller mode in addition to the single-node mode and the AC controller mode.

Overview

In the VMware NSX controller mode, the VMware NSX controller is used to dynamically create VXLAN tunnels. The VMware NSX controller controls VXLAN tunnel establishment of the CE switch through open vSwitch database (OVSDB).

As shown in Figure 6-7, the VMware NSX controller directly manages the virtual network and respectively establishes an OVSDB connection with the NSX OVS and the CE switch. The VMware NSX controller delivers VXLAN-related configurations to the CE switch and configures it to be a VXLAN Layer 2 gateway. In this way, the CE switch serving as a virtual tunnel end point (VTEP) can establish a VXLAN tunnel with the NSX OVS.

The VMware NSX controller uses the replicator to replicate BUM packets in a centralized way. To ensure a reliable link between the CE switch and the replicator, the VMware NSX controller delivers BFD for VXLAN to the leaf device. A BFD check mechanism is used to check the connectivity of the VXLAN tunnel between the leaf device and the replicator. When the replicator is faulty, the VXLAN gateway can identify the fault rapidly and switch traffic to another normal replicator, avoiding traffic loss due to slow fault perception.

Figure 6-7 Network structure based on the VMware NSX controller and VXLAN solution

Pre-configuration

Before using the VMware NSX controller to deploy the VXLAN network, you need to configure the CE switch according to the following procedure. Otherwise, the VXLAN network cannot be deployed through the VMware NSX controller.

  1. In the system view, run the interface nve 1 command to configure NVE interface 1 to be the interface for deploying VXLAN tunnel-related information, and enter the NVE interface view.

  2. In the NVE interface view, run the source ip-address command to configure the IP address of the source VTEP.

NOTE:
When using the VMware NSX controller to deploy a VXLAN network, pay attention to the following:
  • Configure NVE interface 1 to be the interface for deploying VXLAN tunnel-related information. Otherwise, the VXLAN network cannot be deployed through the VMware NSX controller.
  • Only VTEP IPv4 address can be configured.

Configurations Delivered by the VMware NSX Controller

The VMware NSX controller can only deliver VXLAN-related configurations to the CE switch. For this controller, only the CE switch is allowed to serve as a VXLAN Layer 2 gateway. Table 6-4 shows the configurations that can be delivered by the VMware NSX controller.

Table 6-4 Configurations delivered by the VMware NSX controller

Configuration

Description

In the NVE interface view: vni vni-id head-end peer-list ip-address &<1-10>

Configure the unicast VXLAN tunnel.

In the NVE interface view: vni vni-id flood-vtep ip-address &<1-10>

Enable the replicator to process BUM packets.

  1. In the system view: interface interface-type interface-number.subnum mode l2

  2. In the Layer 2 sub-interface view: encapsulation { dot1q [ vid ce-vid ] | untag }

  3. In the Layer 2 sub-interface view: bridge-domain bd-id

Configure the access point for the VXLAN service. The encapsulation type can be Dot1q or Untag.

On the web page of the VMware NSX controller, if the CE switch port is bound to a logical switch and the VLAN ID is 0, the encapsulation type is Untag. If the VLAN ID is not 0, the encapsulation type is Dot1q.

  1. In the system view: bridge-domain bd-id

  2. In the bridge domain (BD) view: vxlan vni vni-id

  3. In the BD view: ovsdb enable

Configure the BD.

In the system view: bfd session-name bind vxlan peer-ip peer-ip-address source-ip source-ip-address peer-mac peer-mac-address auto

In the BFD session view: min-rx-interval interval

Configure BFD for VXLAN.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 37190

Downloads: 125

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