HP BL680c XenServer Administrator's Guide 4.1.0 - Page 38

Managing networking configuration for standalone, XenServer Hosts

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 38 highlights

Networking When a host has multiple NICs the configuration present after installation depends on which NIC is selected for management operations during installation: • PIFs are created for each NIC in the host • the PIF of the NIC selected for use as the management interface is configured with the IP addressing options specified during installation • a network is created for each PIF ("network 0", "network 1", etc.) • each network is connected to one PIF • the IP addressing options of all other PIFs are left unconfigured In both cases the resulting networking configuration allows connection to the XenServer Host by XenCenter, the xe CLI, and any other management software running on separate machines via the IP address of the management interface. The configuration also provides external networking for VMs created on the host. The PIF used for management operations is the only PIF ever configured with an IP address. External networking for VMs is achieved by bridging PIFs to VIFs via the network object which acts as a virtual Ethernet switch. The steps required for networking features such as VLANs, NIC bonds, and dedicating a NIC to storage traffic are covered in the following sections. 4.2. Managing networking configuration for standalone XenServer Hosts 4.2.1. Creating networks Each XenServer Host has one or more networks, which are virtual Ethernet switches. Networks without an association to a PIF are considered internal, and can be used to provide connectivity only between VMs on a given XenServer Host, with no connection to the outside world. Networks with a PIF association are considered external, and provide a bridge between VIFs and the PIF connected to the network, enabling connectivity to resources available through the PIF's NIC. Because external networks are created for each PIF during host installation, creating additional networks is typically only required to: • use an internal network • support advanced operations such as VLANs or NIC bonding To add or remove networks using XenCenter, refer to the XenCenter online Help. Procedure 4.1. To add a new network via the CLI 1. Open the XenServer Host text console. 2. Create the network with the network-create command, which returns the UUID of the newly created network: xe network-create name-label= At this point the network is not connected to a PIF and therefore is internal. 32

  • 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
32
When a host has multiple NICs the configuration present after installation depends on which NIC is selected
for management operations during installation:
•
PIFs are created for each NIC in the host
•
the PIF of the NIC selected for use as the management interface is configured with the IP addressing
options specified during installation
•
a network is created for each PIF ("network 0", "network 1", etc.)
•
each network is connected to one PIF
•
the IP addressing options of all other PIFs are left unconfigured
In both cases the resulting networking configuration allows connection to the XenServer Host by XenCenter,
the xe CLI, and any other management software running on separate machines via the IP address of the
management interface. The configuration also provides external networking for VMs created on the host.
The PIF used for management operations is the only PIF ever configured with an IP address. External
networking for VMs is achieved by bridging PIFs to VIFs via the network object which acts as a virtual
Ethernet switch.
The steps required for networking features such as VLANs, NIC bonds, and dedicating a NIC to storage
traffic are covered in the following sections.
4.2. Managing networking configuration for standalone
XenServer Hosts
4.2.1. Creating networks
Each XenServer Host has one or more networks, which are virtual Ethernet switches. Networks without an
association to a PIF are considered
internal
, and can be used to provide connectivity only between VMs
on a given XenServer Host, with no connection to the outside world. Networks with a PIF association are
considered
external
, and provide a bridge between VIFs and the PIF connected to the network, enabling
connectivity to resources available through the PIF's NIC.
Because external networks are created for each PIF during host installation, creating additional networks
is typically only required to:
•
use an internal network
•
support advanced operations such as VLANs or NIC bonding
To add or remove networks using XenCenter, refer to the XenCenter online Help.
Procedure 4.1. To add a new network via the CLI
1.
Open the XenServer Host text console.
2.
Create the network with the network-create command, which returns the UUID of the newly created
network:
xe network-create name-label=<mynetwork>
At this point the network is not connected to a PIF and therefore is internal.