HP BL680c XenServer Administrator's Guide 4.1.0 - Page 47

Adding NIC bonds to an existing pool, Procedure 4.7. To add NIC bonds to existing pool master

Page 47 highlights

Networking xe pif-reconfigure-ip uuid= mode=None 5. For each member server, join it to the pool and repeat 3 and 4 to move the management interface on the member server to enable the bond. 4.3.2.2. Adding NIC bonds to an existing pool 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 member servers 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 member 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. Procedure 4.7. To add NIC bonds to existing pool master and member hosts 1. Use the network-create command to create a new pool-wide network for use with the bonded NICs. This step should only be performed once per pool. The UUID of the new network is returned. xe network-create name-label=bond0 2. Use XenCenter or the vm-shutdown command to shut down all VMs in the host pool to force all existing VIFs to be unplugged from their current networks. The existing VIFs will be invalid after the bond is enabled. xe vm-shutdown uuid= 3. Use the host-list command to find the UUID of the host being configured: xe host-list 4. Use the pif-list command to determine the UUIDs of the PIFs to use in the bond. Include the hostuuid parameter to list only the PIFs on the host being configured: xe pif-list host-uuid= 5. Use the bond-create command to create the bond, specifying the network UUID created in step 1 and the UUIDs of the PIFs to be bonded, separated by commas. The UUID for the bond is returned. 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108

Networking
41
xe pif-reconfigure-ip uuid=<old mgmt PIF UUID> mode=None
5.
For each member server, join it to the pool and repeat 3 and 4 to move the management interface on
the member server to enable the bond.
4.3.2.2. Adding NIC bonds to an existing pool
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 member servers 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 member 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.
Procedure 4.7. To add NIC bonds to existing pool master and member hosts
1.
Use the
network-create
command to create a new pool-wide network for use with the bonded NICs.
This step should only be performed once per pool. The UUID of the new network is returned.
xe network-create name-label=bond0
2.
Use XenCenter or the
vm-shutdown
command to shut down all VMs in the host pool to force all existing
VIFs to be unplugged from their current networks. The existing VIFs will be invalid after the bond is
enabled.
xe vm-shutdown uuid=<VM UUID>
3.
Use the
host-list
command to find the UUID of the host being configured:
xe host-list
4.
Use the
pif-list
command to determine the UUIDs of the PIFs to use in the bond. Include the
host-
uuid
parameter to list only the PIFs on the host being configured:
xe pif-list host-uuid=<host UUID>
5.
Use the
bond-create
command to create the bond, specifying the network UUID created in step 1 and
the UUIDs of the PIFs to be bonded, separated by commas. The UUID for the bond is returned.