Best practices for managing network cards with xenserver bond

 

During xenserver installation, the system creates a network for each physical network interface card (NIC. Add servers to a resource pool

These default networks are merged so that all physical NICs with the same device name are connected to the same network.

Generally, if you want to create an internal network, use an existing Nic to set a new VLAN or create a NIC binding, you only need to add a new network.

In xenserver, you can configure four different types of networks:

External network, associated with physical network interfaces, can provide bridging between virtual machines and physical network interfaces connected to the network, so that virtual machines can connect to available resources through the physical network interface card of the server.

You can create a binding between two NICs to create a high-performance channel between the virtual machine and the network.

A dedicated network for a single server, which is not associated with a physical network interface, can be used to provide connections between virtual machines on a specified host, but not to the outside.

The cross-server dedicated network is extended to the single-server dedicated network concept, allowing VM usage on different hosts

Vswitches communicate with each other.

Here I will introduce the best practices for binding management networks.

As we know when implementing xenserver, we plan and configure high availability according to the best practices of xenserver, nic binding is required on the Management Network to achieve high availability of the management network. At the same time, our management CIDR blocks and business and storage do not belong to the same CIDR blocks. Therefore, management, business, and storage are different VLANs. People who are not familiar with xenserver implementation and deployment will encounter a problem where the management network card cannot be bound during implementation and deployment of xenserver. If the implementation process follows the standard, there will be no such problem.

 

Xenserver supports active-active, active-passive, and lacp binding modes. The number of supported NICs and the supported binding mode vary depending on the network stack:

Lacp binding only applies to vswitches, while active-active and active-passive applies to vswitch and Linux bridging.

When a vswitch is a network stack, You can bind two, three, or four NICs.

When Linux bridging is a network stack, you can only bind two NICs.

Xenserver supports two types of network stacks. One is the open-source open vswitch, that is, the aforementioned vswitch and the other is the bridge, that is, the aforementioned Linux bridge.

After installing xenserver, We need to bind the network adapter for network management. Ensure that xenserver has the following conditions:

A single xenserver is bound to a management network card:

1. network stack mode: Open vswitch or bridge. To bind more than two NICs, open vswitch is required.

2. Prepare the physical network card of the xenserver to be bound, and configure the management address to another network card. {when binding a management network card, do not configure the management IP address for the network card to be bound. Otherwise, the binding error may occur. The management address must be configured with another Nic, And the NIC must be temporarily connected to the Management Network }.

 

In Pool Mode, multiple xenservers are bound to the Management Network:

1. network stack mode: Open vswitch or bridge. To bind more than two NICs, open vswitch is required. Ensure that the network stack of the seat socket xenserver is consistent.

2. Do not bind the NIC before all xenservers are added to the pool.

3. Therefore, the xenserver needs to prepare the physical network card of the xenserver to be bound, and the management address needs to be configured on another network card. {when binding a management network card, do not configure the management IP address for the network card to be bound, otherwise, a binding error occurs. The management address must be configured with another Nic, And the NIC must be temporarily connected to the Management Network }.

4. If you manage network card binding before adding a pool, the following error occurs:

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/6C/A1/wKiom1VOKpLBruh5AAEv4h5sI0A386.jpg "Title =" 1.jpg" alt = "wkiom1vokplbruh5aaev4h5si0a386.jpg"/>

With the xenserver that meets the above conditions, you can manage the bond of the network without hindrance.

The following is an experiment:

1. Install and optimize xenserver, and confirm that the version and network stack Are consistent:

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/A1/wKiom1VOK12SUpDQAAW-J9PQ6Wo602.jpg "Title =" 1.png" alt = "wKiom1VOK12SUpDQAAW-J9PQ6Wo602.jpg"/>

 

2. Join the resource pool

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/6C/A1/wKiom1VOK5nxWxa8AAWGB8H3YOI102.jpg "Title =" 1.png" alt = "wkiom1vok5nxwxa8aawgb8h3yoi102.jpg"/>

3. Create a resource pool and Add hosts

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/6C/9C/wKioL1VOLW7BsnsXAAQ5VLCHeI4729.jpg "Title =" 1.png" alt = "wkiol1volw7bsnsxaaq5vlchei4729.jpg"/>

4. I want to bind two NICs to the management network of xenserver. These two NICs are Nic 6 and nic 7. Note that my current management IP address is on Nic 2, that is to say, the two NICs I bound do not have a network IP address configured.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/A1/wKiom1VOLJHAkFfNAATfCjMOVTI341.jpg "Title =" 1.png" alt = "wkiom1voljhakffnaatfcjmovti341.jpg"/>

5. Start Nic binding

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/6C/9C/wKioL1VOLjXTev8RAASQZn7uC6A673.jpg "Title =" 1.png" alt = "wkiol1voljxtev8raasqzn7uc6a673.jpg"/>

6. Bind Nic 6 and nic 7 in active-passive mode.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/A1/wKiom1VOLOfQt26eAAUJvi7Cri8274.jpg "Title =" 1.png" alt = "wkiom1volofqt26eaaujvi7cri8274.jpg"/>

7. Enable the NIC bond in the Pool Mode. You only need to do it on the master host. The remaining hosts will know the configuration of the synchronization master.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/9C/wKioL1VOLsTia8eOAAUA3HVqSDs491.jpg "Title =" 1.png" alt = "wkiol1volstia8eoaaua3hvqsds491.jpg"/>

8. Binding completed

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/6C/9C/wKioL1VOLunSzuliAATmjjO1Wyw440.jpg "Title =" 1.png" alt = "wkiol1volunszuliaatm jjo1wyw440.jpg"/>

9. After the management network card is bound, we also need to move the management IP address to the bound network card and select the configuration

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M01/6C/A1/wKiom1VOLbrQ4P6AAASu_K4Df_Y316.jpg "Title =" 1.png" alt = "wkiom1volbrq4p6aaasu_k4df_y316.jpg"/>

10. Select the NIC whose management address needs to be moved from the drop-down list.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/9C/wKioL1VOL27Q64IXAATAaDNdSpM336.jpg "Title =" 1.png" alt = "wkiol1vol27q64ixaataadndspm336.jpg"/>

11. Select Manage network and bind network card, and click OK.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M02/6C/A1/wKiom1VOLhCjduWHAATB8Ntjn7I533.jpg "Title =" 1.png" alt = "wkiom1volhcjduwhaatb8ntjn7i533.jpg"/>

12. Click to reconfigure

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/6C/9C/wKioL1VOL7yg-RmPAASvOPnHhoE499.jpg "Title =" 1.png" alt = "wKioL1VOL7yg-RmPAASvOPnHhoE499.jpg"/>

13. We have moved the management address back to the bound Management Network, and the rest will be able to move Nic 2 to another VLAN for other services to use.

650) This. width = 650; "src =" http://s3.51cto.com/wyfs02/M00/6C/A1/wKiom1VOLn3j0DwkAATq1NWqFoM105.jpg "Title =" 1.png" alt = "wkiom1voln3j0dwkaatq1nwqfom105.jpg"/>

This article is from the blog "I get a year of chaos Floating Life", please be sure to keep this source http://tasnrh.blog.51cto.com/4141731/1649918

Best practices for managing network cards with xenserver bond