This chapter provides an overview of XenServer networking, including networks, VLANs, and NIC bonds. It also discusses how to manage your networking configuration and troubleshoot it.
The XenServer default network stack is the vSwitch; however, you can use the Linux network stack if desired by using the instructions in the section called “vSwitch Networks”.
If you are already familiar with XenServer networking concepts, you may want to skip ahead to one of the following sections:
To create networks for standalone XenServer hosts, see the section called “Creating Networks in a Standalone Server”.
To create private networks across XenServer hosts, see the section called “Cross-Server Private Networks”
To create networks for XenServer hosts that are configured in a resource pool, see the section called “Creating Networks in Resource Pools”.
To create VLANs for XenServer hosts, either standalone or part of a resource pool, see the section called “Creating VLANs”.
To create bonds for standalone XenServer hosts, see the section called “Creating NIC Bonds on a Standalone Host”.
To create bonds for XenServer hosts that are configured in a resource pool, see the section called “Creating NIC Bonds in Resource Pools”.
For additional information about networking and network design, see Designing XenServer Network Configurations in the Citrix Knowledge Center.
For consistency with XenCenter terminology changes in this release, this chapter now uses the term management interface to refer to the IP-enabled NIC that carries the management traffic. In the last release, this chapter used the term primary management interface for this purpose. Likewise, this chapter now uses the term secondary interface to refer to an IP-enabled NIC configured for storage traffic.
XenServer supports up to 16 physical network interfaces (or up to 8 bonded network interfaces) per XenServer host and up to 7 virtual network interfaces per VM.
XenServer provides automated configuration and management of NICs using the xe command line interface (CLI). Unlike previous XenServer versions, the host networking configuration files should not be edited directly in most cases; where a CLI command is available, do not edit the underlying files.