Filter
Top Products
Chapter 8. Installing XenServer for CloudPlatform
106
Make note of the values you will need when you add this storage to the CloudPlatform later (see
Section 7.7, “Adding Primary Storage”). In the Add Primary Storage dialog, in Protocol, you will choose
PreSetup. In SR Name-Label, you will enter the same name used to create the SR.
If you encounter difficulty, address the support team for the SAN provided by your vendor. If they are
not able to solve your issue, see Contacting Support.
8.10. Physical Networking Setup for XenServer
Once XenServer has been installed, you may need to do some additional network configuration. At
this point in the installation, you should have a plan for what NICs the host will have and what traffic
each NIC will carry. The NICs should be cabled as necessary to implement your plan.
If you plan on using NIC bonding, the NICs on all hosts in the cluster must be cabled exactly the
same. For example, if eth0 is in the private bond on one host in a cluster, then eth0 must be in the
private bond on all hosts in the cluster.
The IP address assigned for the management network interface must be static. It can be set on the
host itself or obtained via static DHCP.
CloudPlatform configures network traffic of various types to use different NICs or bonds on the
XenServer host. You can control this process and provide input to the Management Server through
the use of XenServer network name labels. The name labels are placed on physical interfaces or
bonds and configured in CloudPlatform. In some simple cases the name labels are not required.
8.10.1. Configuring Public Network with a Dedicated NIC for
XenServer (Optional)
CloudPlatform supports the use of a second NIC (or bonded pair of NICs, described in Section 8.10.4,
“NIC Bonding for XenServer (Optional)”) for the public network. If bonding is not used, the public
network can be on any NIC and can be on different NICs on the hosts in a cluster. For example, the
public network can be on eth0 on node A and eth1 on node B. However, the XenServer name-label
for the public network must be identical across all hosts. The following examples set the network label
to "cloud-public". After the management server is installed and running you must configure it with the
name of the chosen network label (e.g. "cloud-public"); this is discussed in Section 5.4, “Management
Server Installation”.
If you are using two NICs bonded together to create a public network, see Section 8.10.4, “NIC
Bonding for XenServer (Optional)”.
If you are using a single dedicated NIC to provide public network access, follow this procedure on
each new host that is added to CloudPlatform before adding the host.
1. Run xe network-list and find the public network. This is usually attached to the NIC that is public.
Once you find the network make note of its UUID. Call this <UUID-Public>.
2. Run the following command.
# xe network-param-set name-label=cloud-public uuid=<UUID-Public>
8.10.2. Configuring Multiple Guest Networks for XenServer
(Optional)
CloudPlatform supports the use of multiple guest networks with the XenServer hypervisor. Each
network is assigned a name-label in XenServer. For example, you might have two networks with the