XenServer multi-NIC binding implementation tutorial

xenserver XenCenter can bind the network card, support Active-Active and Active-Standby mode, but only two network cards can be bound to one group through Xencenter. More, such as 3 blocks, 4 blocks, but can not be implemented here, this time you need to operate through the CLI.

Before starting to bind multiple NICs, we need to understand some of the processing methods and processes for binding in XenServer.

First, create a Network object in XenServer, and finally Bond will be associated with the object, and assigned to the VM to be bound to the physical network card and binding mode to create a binding (bond-create), associated Network Objects. We can automatically complete the above process when creating bindings using XenCenter, but to create bindings through the CLI, we need to manually create related objects, and I will also list related screenshots. Easy to understand.

Network Card List Icon

We can see that the display in XenCenter, the host defaults to 4 network cards, and defaults to one Network object per network card.

Command manual binding process

Binding process:

#Create Network object, return Network object UUIDxe network-create name-label=” Bond 1+2+3″ #View physical network card UUIDxe pif-list params=device, uuid# bind eth1, eth2, eth3, and associated to the pre-created network object # can specify the binding mode, XenServer6.0 provides modes supported active-back and balance-slbxe bond-create pif-uuids = & lt; eth1, eth2, eth3 & lsquo; s uuid & gt; network-uuid = & lt; network uuid & gt;

in a first step After the creation of the Network object is completed, we can see the newly created Network object in the Network tab, and the Network objects corresponding to the other four physical NICs can also be seen.
After completing the creation of Bond and correlating the Network object, we can find that in the Network display, the MAC address of Bond 1+2+3 has been automatically generated, and the previous physical network card eth1, eth2, eth3 object Network 1, Network 2, Network 3 has disappeared. This is because, in the process of creating a network bond, XenServer will unlink the physical NIC to the previous NIC object, preventing the use of a separate physical NIC. BTW: This is just to say that the association to the Network object is resolved, and the corresponding internal Bridge still exists. You can understand it yourself.