XenServer Network (LACP Bond, VLAN and Bonding) Configuration - Part 3 - Part 4

Step 4: XenServer Active/Passive Network Bonding

Now let’s take a look at storage and management traffic. This server currently only has two PIFs left for use and as such there are two options for how to proceed.

Each of the remaining PIFs could be used for one type of traffic or the two PIFs could be bonded together in an active/passive fail-over with both management and storage traffic going across the same set of PIFs (please note that according to Citrix, the management interface doesn’t support load balancing).

This process will be completed in a similar fashion to the LACP bond previously. The first step is to create the network for this bond.

# xe network-create name-label="Management/Storage Bond"
# xe network-list name-label="Management/Storage Bond"

Create XenServer Active/Passive Bonding Confirm XenServer Active/Passive Bonding

Again don’t forget to keep track of the UUID as it will be needed to attach PIFs to the bond network that is about to be created. The next step is to actually create the bond and in order to do this, the UUID for the other two PIFs will need to be determined.

# xe pif-list device=eth2 
# xe pif-list device=eth3
# xe bond-create mode=active-backup network-uuid=<network_UUID> pif-uuids=<PIF_UUIDs>

Be sure to substitute the proper information from the prior commands for the UUIDs in the last command. At this point the system will return the UUID of the bond that was created.

Create XenServer Network Bond

Then the creation of the bond can be confirmed with another xe command.

# xe bond-list 

Confirm XenServer Network Bond UUID’s

From the output here, the UUIDs of the bonds can be compared. Notice that the second UUID matches the UUID returned from the bond-create command in the above photo.

At this point the 4 PIF interfaces on this XenServer are members of bonds. One of the bonds is a trunk and has one VLAN tag network ready to be sent across this trunk bond. The other bond is an active/passive bond that is used for network storage as well as management of the XenServer itself.

For illustrative purposes, once these networks have been created, they can also be verified within Citrix’s XenCenter application rather than the command line. This guide has used the CLI for these tasks as XenCenter is not installable on Linux.

Verify XenServer Network Configuration

This concludes this brief introduction to networking in XenServer. The next article in this series will begin working with XenServer storage solutions. Please feel free to leave any comments or questions below!

Pages: 1 2 3 4