Shulou(Shulou.com)06/01 Report--

After completing the environment preparation for NSX, we came to the configuration preparation of Virtual Extensible LAN (VXLAN), one of the most important technologies for NSX to implement the sophomore layer. VXLAN is an open technical standard that allows you to create a logical network for virtual machines on different networks. It is possible to realize the Layer 2 network across Layer 3, which is commonly known as large layer 2 network.

The VXLAN transport network is built by creating a VXLAN dedicated VMkernel interface on each ESXi Host. This interface will be used to encapsulate Segments Packets when the virtual machine is not on the current ESXi Host but needs to communicate. Encapsulation through the VMkernel interface does not lead to what the user needs to do in the transmission process, and the encapsulation process is transparent to the user. Whether or not two transport objects need to span a multi-layer L3 network, they can still be in the same Segment. That's the wonder of the second floor.

1. To configure VXLAN, you also need to configure it in vSphere Web Client Networking & Security Installation Host Preparation Configure, this window. When you follow the steps here to go to the configuration VXLAN window, you can see the interface shown in figure 01. In this interface, click Configure of the VXLAN option, and the configuration VXLAN configuration wizard will be activated. During this configuration, a new VMkernel interface will be created on each host in the Cluster, which will be used for VXLAN Tunnel Endpoint (VTEP) purposes:

Figure 01

The working contents of the VTEP VMkernel API are as follows:

Switch-it establishes the basic communication relationship with ESXi Host's virtual switch by selecting a vDS.

VLAN-you need to set VLAN ID for the VXLAN VMkernel interface. If you do not want to set it, you can set it to 0, which means that all communications can be passed.

MTU-this parameter defaults to 1600, and the standard MTU value is generally 1500. The reason why it is set to 1600 here is that there will be an increase in packet headers in the encapsulation of VXLAN. Normally, the increase in the number of headers will be more than 50, coupled with the increase in the number of headers that may exist in physical links, so the MTU value is recommended to be more than 1600; (note: if you do not know the number of VXLAN headers and want to know the details, please click here to go to the virtual human website for detailed instructions, basically to add Ethernet Header, IP Header, UDP Header, VXLAN Header)

Vmk IP-An IP address is required. The IP here can be obtained through IP Pool or DHCP. It is recommended to set it through IP Pool.

2. After clicking Configure according to the instructions in step 1, you will come to the window shown in figure 02. The relevant content in the window has been explained in step 1, and you can enter it as follows:

Figure 02

3. Since you chose IP Pool to set the IP address for VMkernel, you need to add a new IP Pool. Click the New IP Pool of the VMKNic IP Addressing option in figure 02. Option, you will come to the Add IP Pool window shown in figure 03, where the options you need to set include:

Name-the name of the IP Pool, which is recommended to be entered by purpose, such as VXLAN IP Pool in this article.

Gateway-the default gateway address assigned to the VMkernel by this IP Pool

Prefix Length-Subnet Siz

Primary DNS-DNS server message

DNS Suffix-DNS query suffix, such as vmanager.cn in this example

Static IP Pool-an address range that represents the IP address field that can be assigned to VXLAN VMkernel in the format: x.x.x.x-x.x.x.z, note the format

Figure 03

3. Since the study of VXLAN environment usually involves spanning three layers, you need to add a new Cluster so that you can continue the second-tier experiment, which is why in this series of documents, virtual human recommends that you prepare 2 Cluster. In addition to this factor, there are two things not covered in step 1 of this article in the Configure VXLANnetworking window, and that is:

VMKNic Teaming Policy-this option represents the Teaming Policy selection of the uplink physical network card for this VTEP Port Group. It supports Failover, StaticEtherChannel, etc., so this column can be set as needed.

VTEP-the use of VTEP has been described in step 1, and its settings need to be set in this window, but it is not allowed to be configured in Fail Over and Static EtherChannel modes

So, in this step, repeat the previous actions 1-2 to create another VXLAN

4. After completing the configuration of VXLAN, go to Host Preparation again, and you can see that the VXLAN status of Cluster has changed to Enabled status, as shown in figure 04:

Figure 04

5. At this point, click Inventory ESXi Host Manage Networking VMkernel adapters and go to the window shown in figure 05. You can see that a VMkernel named vxw-vmknicPg-dvs-xxxxxx has been created successfully. Moreover, with the IP address from the IP Pool planned in step 2, you can see the display in TCP/IP Stack: every CVM in vxlan,Cluster can see it, but the IP is different:

Figure 05

6. The above message can also be seen in the VMKNic IP Addressing option shown in Networking & Security Installation Logical Network Preparation VXLAN Transport in figure 06:

Figure 06

There are as many hosts as there are hosts that can successfully configure the VXLAN option in the previous manner. More details will be introduced later.

To be continued.

Please download the details of the picture and text from the blogger's download center.

National Day is coming. I hope you all have a good holiday.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.