HP BL680c XenServer Administrator's Guide 4.1.0 - Page 44

Managing networking configuration for XenServer pools

Get HP BL680c - ProLiant - G5 PDF manuals and user guides
UPC - 884420396314
View all HP BL680c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 44 highlights

Networking xe pif-list 2. Use the pif-param-list command to verify the IP addressing configuration for the PIF that will be used for the management interface. If necessary, use the pif-reconfigure-ip command to configure IP addressing for the PIF to be used. See Chapter 5, Command line interface for more detail on the options available for the pif-reconfigure-ip command. xe pif-param-list uuid= 3. Use the host-management-reconfigure CLI command to change the PIF used for the management interface: xe host-management-reconfigure pif-uuid= 4.2.7.5. Disabling management access To disable remote access to the management console entirely, use the host-management-disable CLI command. But be careful! Once the management interface is disabled, you will have to log in on the physical host console to perform management tasks and external interfaces such as XenCenter will no longer work. 4.3. Managing networking configuration for XenServer pools 4.3.1. Networks in resource pools All XenServer Hosts in a resource pool should have the same number of physical network interface cards (NICs), although this requirement is not strictly enforced when a XenServer Host is joined to a pool. Having the same physical networking configuration for XenServer Hosts within a pool is important because all hosts in a pool share a common set of XenServer networks. PIFs on the individual hosts are connected to pool-wide networks based on device name. For example, all XenServer Hosts in a pool with an eth0 NIC will have a corresponding PIF plugged into the pool-wide "Network 0" network. The same will be true for hosts with eth1 NICs and "Network 1", as well as other NICs present in at least one XenServer Host in the pool. If one XenServer Host has a different number of NICs than other hosts in the pool, complications can arise because not all pool networks will be valid for all pool hosts. For example, if hosts A and B are in the same pool and host A has four NICs while host B only has two, only the networks connected to PIFs corresponding to eth0 and eth1 will be valid on host B. VMs on host A with VIFs connected to networks corresponding to eth2 and eth3 will not be able to migrate to host B. All NICs of all XenServer Hosts within a resource pool must be configured with the same MTU size. 4.3.2. Creating NIC bonds in resource pools Whenever possible, create NIC bonds as part of initial resource pool creation prior to joining additional member servers to the pool or creating VMs. Doing so allows the bond configuration to be automatically replicated to member servers as they are joined to the pool and reduces the number of steps required. Adding a NIC bond to an existing pool is also a disruptive operation - all VMs in the pool must be shut down. 38

  • 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
38
xe pif-list
2.
Use the
pif-param-list
command to verify the IP addressing configuration for the PIF that will be used
for the management interface. If necessary, use the
pif-reconfigure-ip
command to configure IP ad-
dressing for the PIF to be used. See Chapter 5,
Command line interface
for more detail on the options
available for the pif-reconfigure-ip command.
xe pif-param-list uuid=<PIF UUID>
3.
Use the
host-management-reconfigure
CLI command to change the PIF used for the management
interface:
xe host-management-reconfigure pif-uuid=<PIF UUID>
4.2.7.5. Disabling management access
To disable remote access to the management console entirely, use the
host-management-disable
CLI
command. But be careful! Once the management interface is disabled, you will have to log in on the physical
host console to perform management tasks and external interfaces such as XenCenter will no longer work.
4.3. Managing networking configuration for XenServer pools
4.3.1. Networks in resource pools
All XenServer Hosts in a resource pool should have the same number of physical network interface cards
(NICs), although this requirement is not strictly enforced when a XenServer Host is joined to a pool.
Having the same physical networking configuration for XenServer Hosts within a pool is important because
all hosts in a pool share a common set of XenServer networks. PIFs on the individual hosts are connected to
pool-wide networks based on device name. For example, all XenServer Hosts in a pool with an eth0 NIC will
have a corresponding PIF plugged into the pool-wide "Network 0" network. The same will be true for hosts
with eth1 NICs and "Network 1", as well as other NICs present in at least one XenServer Host in the pool.
If one XenServer Host has a different number of NICs than other hosts in the pool, complications can arise
because not all pool networks will be valid for all pool hosts. For example, if hosts A and B are in the same
pool and host A has four NICs while host B only has two, only the networks connected to PIFs corresponding
to eth0 and eth1 will be valid on host B. VMs on host A with VIFs connected to networks corresponding to
eth2 and eth3 will not be able to migrate to host B.
All NICs of all XenServer Hosts within a resource pool must be configured with the same MTU size.
4.3.2. Creating NIC bonds in resource pools
Whenever possible, create NIC bonds as part of initial resource pool creation prior to joining additional
member servers to the pool or creating VMs. Doing so allows the bond configuration to be automatically
replicated to member servers as they are joined to the pool and reduces the number of steps required.
Adding a NIC bond to an existing pool is also a disruptive operation - all VMs in the pool must be shut down.