77
a. Use the host-list command to find the UUID of the host being configured:
xe host-list
b. Use the pif-list command to determine the UUID of bond PIF on the new host. Include the host-
uuid parameter to list only the PIFs on the host being configured:
xe pif-list network-name-label=<network_name> host-uuid=<host_uuid>
c. Use the pif-reconfigure-ip command to configure the desired management interface IP address
settings for the bond PIF. See Appendix A, Command line interface, for more detail on the options
available for the pif-reconfigure-ip command. This command must be run directly on the host:
xe pif-reconfigure-ip uuid=<bond_pif_uuid> mode=DHCP
d. Use the host-management-reconfigure command to move the management interface from the
existing physical PIF to the bond PIF. This step activates the bond. This command must be run
directly on the host:
xe host-management-reconfigure pif-uuid=<bond_pif_uuid>
e. Use the pif-reconfigure-ip command to remove the IP address configuration from the non-bonded
PIF previously used for the management interface. This step is not strictly necessary but may help
reduce confusion when reviewing the host networking configuration. This command must be run
directly on the host server:
xe pif-reconfigure-ip uuid=<old_mgmt_pif_uuid> mode=None
4. For each additional host you want to join to the pool, repeat steps 3 and 4 to move the management
interface on the host and to enable the bond.
Adding NIC bonds to an existing pool
Warning:
Do not attempt to create network bonds while HA is enabled. The process of bond creation disturbs the
in-progress HA heartbeating and causes hosts to self-fence (shut themselves down); subsequently they will
likely fail to reboot properly and you will need to run the host-emergency-ha-disable command to recover
them.
Note:
If you are not using XenCenter for NIC bonding, the quickest way to create pool-wide NIC bonds is to create
the bond on the master, and then restart the other pool members. Alternately you can use the service xapi
restart command. This causes the bond and VLAN settings on the master to be inherited by each host. The
management interface of each host must, however, be manually reconfigured.
When adding a NIC bond to an existing pool, the bond must be manually created on each host in the pool.
The steps below can be used to add NIC bonds on both the pool master and other hosts with the following
requirements:
1. All VMs in the pool must be shut down
2. Add the bond to the pool master first, and then to other hosts.
3. The bond-create, host-management-reconfigure and host-management-disable commands affect
the host on which they are run and so are not suitable for use on one host in a pool to change the
configuration of another. Run these commands directly on the console of the host to be affected.