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

Step 3: Creating a XenServer Network VLAN

At this point the LACP bond is ready to be used. Since this particular LACP bond is a trunk, it will be important to create tagged external networks so that traffic will have the proper VLAN tag.

Let’s visit this process now. The first step is to create a new network for this particular VLAN. This is the same as what was done to create the bond in the first place.

# xe network-create name-label=VLAN10 name-description="Tecmint test VLAN 10"

As with all of the other xe commands, this one when successful, will output the UUID of the newly created network. Keep this handy as it will be needed soon.

Create XenServer VLAN Network
Create XenServer VLAN Network

The next step is to determine the UUID of the PIF that this VLAN network will use. In this example, the LACP bond from the previous steps will be used to support VLANs. Using xe, the UUID of the bond interface can be determined.

# xe pif-list network-name-label="Tecmint-LACP-Bond"

This will return the UUID of the bond0 interface. This UUID will be necessary for the VLAN network so that the tagged traffic knows what interface to exit the XenServer.

List XenServer VLAN Network UUID
List XenServer VLAN Network UUID

From this point all the necessary information is available to build the xe command to create a VLAN tagged network.

# xe vlan-create network-uuid=cfe987f0-b37c-dbd7-39be-36e7bfd94cef pif-uuid=ca9a221c-d77f-a118-a274-badd85624fd3 vlan=10
Create XenServer VLAN Tagged Network
Create XenServer VLAN Tagged Network

The UUID returned here indicates the host that this new VLAN network was created on and isn’t actually needed for any further steps. As with all steps, it is always a good idea to confirm that the changes were applied.

To confirm the new VLAN network:

# xe vlan-list tag=10

This will return the information for the VLAN 10 network just created as well as the associated PIFs.

Check XenServer VLAN Network Information
Check XenServer VLAN Network Information

This XenServer now has a LACP bonded network as well as one network that is ready to tag traffic for a VLAN 10. This VLAN 10 network can be added to a VIF (virtual interface) on a guest to allow guest traffic to be tagged by the virtual switch and sent across the trunk setup between the switch and the XenServer.

If you read this far, tweet to the author to show them you care. Tweet a thanks
Rob Turner
Rob Turner is an avid Debian user as well as many of the derivatives of Debian such as Devuan, Mint, Ubuntu, and Kali. Rob holds a Masters in Information and Communication Sciences as well as several industry certifications from Cisco, EC-Council, ISC2, Linux Foundation, and LPI.

Each tutorial at TecMint is created by a team of experienced Linux system administrators so that it meets our high-quality standards.

Join the TecMint Weekly Newsletter (More Than 156,129 Linux Enthusiasts Have Subscribed)
Was this article helpful? Please add a comment or buy me a coffee to show your appreciation.

4 thoughts on “XenServer Network (LACP Bond, VLAN and Bonding) Configuration – Part 3”

  1. Thanks, Rob:

    Can you recommend some way of identifying the UUID of the XenServer host’s Primary Management Interface (PMI) from the command-line?

    Eric Pretorious
    Portland, Oregon

    • Eric,

      Sure! xe pif-list management=true host-name-label= or if you want only the UUID only you can run the following command: xe pif-list management=true host-name-label= | head -1 | awk -F ‘: ‘ ‘{print $2}’

      xe pif-list management=true host-name-label=


      uuid ( RO) : 2ba82249-cc18-8525-3a3a-289890665e08
      Device ( RO): eth0
      currently-attached ( RO): true
      VLAN ( RO): -1
      network-uuid ( RO): 5798e0f4-d84a-ae3e-c090-709f70a016ac

      xe pif-list management=true host-name-label= | head -1 | awk -F ‘: ‘ ‘{print $2}’





Got something to say? Join the discussion.

Thank you for taking the time to share your thoughts with us. We appreciate your decision to leave a comment and value your contribution to the discussion. It's important to note that we moderate all comments in accordance with our comment policy to ensure a respectful and constructive conversation.

Rest assured that your email address will remain private and will not be published or shared with anyone. We prioritize the privacy and security of our users.