XenServer Administrator's Guide 4.1.0

Networking
43
Procedure 4.8. To change the IP address of a pool member host:
1. Use the pif-reconfigure-ip CLI command to set the IP address as desired. See Chapter 5, Command
line interface for details on the parameters of the pif-reconfigure-ip command:
xe pif-reconfigure-ip uuid=<PIF UUID> mode=DHCP
2. Use the host-list CLI command to confirm that the member host has successfully reconnected to the
master host by checking that all the other XenServer Hosts in the pool are visible:
xe host-list
Changing the IP address of the master XenServer Host requires additional steps because each of the
member hosts uses the master's advertised IP address for communication and will not know how to contact
the master when its IP address changes.
Whenever possible, use a dedicated IP address that is not likely to change for the lifetime of the pool for
pool masters.
Procedure 4.9. To change the IP address of a pool master host
1. Use the pif-reconfigure-ip CLI command to set the IP address as desired. See Chapter 5, Command
line interface for details on the parameters of the pif-reconfigure-ip command:
xe pif-reconfigure-ip uuid=<PIF UUID> mode=DHCP
2. When the IP address of the pool master host is changed, all member hosts will enter into an emergency
mode when they fail to contact the master host.
3. On the master XenServer Host, use the pool-recover-slaves command to force the master to contact
each of the member servers and inform them of the master's new IP address:
xe pool-recover-slaves
Refer to the Section 2.7.2, “Master failures” for more information on emergency mode.
4.3.4. NIC/PIF ordering
It is possible for physical NIC devices to be discovered in different orders on different servers even though
the servers contain the same hardware. Verifying NIC ordering is recommended before using the pooling
features of XenServer.
4.3.4.1. Verifying NIC ordering
The pif-list command can be used to verify that NIC ordering is consistent across your XenServer Hosts.
Review the MAC address and carrier (link state) parameters associated with each PIF to verify that the
devices discovered (eth0, eth1, etc.) correspond to the appropriate physical port on the server.