HP BL680c XenServer Administrator's Guide 4.1.0 - Page 37

Networking

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

Chapter 4. Networking This chapter discusses how physical network interface cards (NICs) in XenServer Hosts are used to enable networking within Virtual Machines (VMs). XenServer supports up to 4 physical NICs per XenServer Host and up to 7 virtual network interfaces (VIFs) per VM. XenServer 4.1 provides automated configuration and management of NICs via the xe command line interface (CLI). As VIFs, PIFs, and networks are created and configured the XenServer Host will perform all required configuration of the physical NICs. Note Unlike previous XenServer versions, the host's networking configuration files should not be edited directly in most cases; where a CLI command is available, do not edit the underlying files. Some networking options have different behaviors when used with standalone XenServer Hosts compared to resource pools. This chapter contains sections on general information that applies to both standalone hosts and pools, and additional information that applies when using pools. The xe CLI can be used to create, destroy and modify three types of server-side objects which represent networking entities. These objects are: • A PIF, which represents a physical network interface on a XenServer Host. • A VIF, which represents a virtual interface on a Virtual Machine. • A network, which is a virtual Ethernet switch on a XenServer Host. Network objects have a name and description, a globally unique UUID, and the collection of VIFs and PIFs connected to the network. Additional CLI commands allow configuration of networking options, control over which NIC is used for management operations, and creation of advanced networking features such as virtual local area networks (VLANs) and NIC bonds. The examples in this chapter assume familiarity with the xe CLI. For more information on using the xe CLI, see Chapter 5, Command line interface. 4.1. Networking configuration performed during Host installation The networking configuration for a XenServer Host is specified during initial host installation. Options such as IP address configuration (DHCP/static), the NIC used as the management interface, and hostname are set based on the values provided during installation. When a XenServer Host has a single NIC, the follow configuration will be present after installation: • a single PIF is created corresponding to the host's single NIC • the PIF is configured with the IP addressing options specified during installation and to enable management of the host • the PIF is set for use in host management operations • a single network, network 0, is created • network 0 is connected to the PIF to enable external connectivity to VMs 31

  • 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
31
Chapter 4. Networking
This chapter discusses how physical network interface cards (NICs) in XenServer Hosts are used to enable
networking within Virtual Machines (VMs). XenServer supports up to 4 physical NICs per XenServer Host
and up to 7 virtual network interfaces (VIFs) per VM.
XenServer 4.1 provides automated configuration and management of NICs via the xe command line inter-
face (CLI). As VIFs, PIFs, and networks are created and configured the XenServer Host will perform all
required configuration of the physical NICs.
Note
Unlike previous XenServer versions, the host's networking configuration files should not be edited
directly in most cases; where a CLI command is available, do not edit the underlying files.
Some networking options have different behaviors when used with standalone XenServer Hosts compared
to resource pools. This chapter contains sections on general information that applies to both standalone
hosts and pools, and additional information that applies when using pools.
The xe CLI can be used to create, destroy and modify three types of server-side objects which represent
networking entities. These objects are:
•
A
PIF
, which represents a physical network interface on a XenServer Host.
•
A
VIF
, which represents a virtual interface on a Virtual Machine.
•
A
network
, which is a virtual Ethernet switch on a XenServer Host. Network objects have a name and
description, a globally unique UUID, and the collection of VIFs and PIFs connected to the network.
Additional CLI commands allow configuration of networking options, control over which NIC is used for
management operations, and creation of advanced networking features such as virtual local area networks
(VLANs) and NIC bonds.
The examples in this chapter assume familiarity with the xe CLI. For more information on using the xe CLI,
see Chapter 5,
Command line interface
.
4.1. Networking configuration performed during Host installa-
tion
The networking configuration for a XenServer Host is specified during initial host installation. Options such
as IP address configuration (DHCP/static), the NIC used as the management interface, and hostname are
set based on the values provided during installation.
When a XenServer Host has a single NIC, the follow configuration will be present after installation:
•
a single PIF is created corresponding to the host's single NIC
•
the PIF is configured with the IP addressing options specified during installation and to enable manage-
ment of the host
•
the PIF is set for use in host management operations
•
a single network, network 0, is created
•
network 0 is connected to the PIF to enable external connectivity to VMs