Chapter 10. Installing VMware for CloudPlatform
120
10.3. vSphere Installation Steps
1. If you haven't already, you'll need to download and purchase vSphere from the VMware Website
(https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1) and install it by
following the VMware vSphere Installation Guide.
2. Following installation, perform the following configuration steps, which are described in the next
few sections:
Required Optional
ESXi host setup NIC bonding
Configure host physical networking, virtual
switch, vCenter Management Network, and
extended port range
Multipath storage
Prepare storage for iSCSI
Configure clusters in vCenter and add hosts to
them, or add hosts without clusters to vCenter
10.4. ESXi Host setup
All ESXi hosts should enable CPU hardware virtualization support in BIOS. Please note hardware
virtualization support is not enabled by default on most servers.
10.5. Physical Host Networking
You should have a plan for cabling the vSphere hosts. Proper network configuration is required before
adding a vSphere host to CloudPlatform. To configure an ESXi host, you can use vClient to add it as
standalone host to vCenter first. Once you see the host appearing in the vCenter inventory tree, click
the host node in the inventory tree, and navigate to the Configuration tab.
In the host configuration tab, click the "Hardware/Networking" link to bring up the networking
configuration page as above.

10.5.1. Configure Virtual Switch

A default virtual switch vSwitch0 is created. CloudPlatform requires all ESXi hosts in the cloud to use
the same set of virtual switch names. If you change the default virtual switch name, you will need to
configure one or more CloudPlatform configuration variables as well.

10.5.1.1. Separating Traffic

CloudPlatform allows you to use vCenter to configure three separate networks per ESXi host. These
networks are identified by the name of the vSwitch they are connected to. The allowed networks
for configuration are public (for traffic to/from the public internet), guest (for guest-guest traffic), and
private (for management and usually storage traffic). You can use the default virtual switch for all
three, or create one or two other vSwitches for those traffic types.
If you want to separate traffic in this way you should first create and configure vSwitches in vCenter
according to the vCenter instructions. Take note of the vSwitch names you have used for each traffic
type. You will configure CloudPlatform to use these vSwitches.
For example, in the following figure, you can see that the Standard vSwitch name is used in
CloudPlatform as the VMware traffic label.