6.0

2 Click the Configuration tab.
3 Select Networking under Hardware, and click the Add Networking link.
The Add Network wizard appears.
4 Select VMkernel under Connection Types and click Next.
5 Select Create a virtual switch and click Next.
6 Provide a label for the switch.
7 Select either Use this port group for vMotion or Use this port group for Fault Tolerance logging and
click Next.
8 Provide an IP address and subnet mask and click Next.
9 Click Finish.
After you create both a vMotion and Fault Tolerance logging virtual switch, you can create other virtual
switches, as needed. You should then add the host to the cluster and complete any steps needed to turn on
Fault Tolerance.
What to do next
To confirm that you successfully enabled both vMotion and Fault Tolerance on the host, view its Summary
tab in the vSphere Client. In the General pane, the fields vMotion Enabled and Host Configured for FT
should show yes.
NOTE If you configure networking to support FT but subsequently disable the Fault Tolerance logging port,
pairs of fault tolerant virtual machines that are already powered on remain powered on. However, if a
failover situation occurs, when the Primary VM is replaced by its Secondary VM a new Secondary VM is not
started, causing the new Primary VM to run in a Not Protected state.
Fault Tolerance Host Networking Configuration Example
This example describes the host network configuration for Fault Tolerance in a typical deployment with
four 1GB NICs. This is one possible deployment that ensures adequate service to each of the traffic types
identified in the example and could be considered a best practice configuration.
Fault Tolerance provides full uptime during the course of a physical host failure due to power outage,
system panic, or similar reasons. Network or storage path failures or any other physical server components
that do not impact the host running state may not initiate a Fault Tolerance failover to the Secondary VM.
Therefore, customers are strongly encouraged to use appropriate redundancy (for example, NIC teaming) to
reduce that chance of losing virtual machine connectivity to infrastructure components like networks or
storage arrays.
NIC Teaming policies are configured on the vSwitch (vSS) Port Groups (or Distributed Virtual Port Groups
for vDS) and govern how the vSwitch will handle and distribute traffic over the physical NICs (vmnics)
from virtual machines and vmkernel ports. A unique Port Group is typically used for each traffic type with
each traffic type typically assigned to a different VLAN.
Figure 27-1 depicts the network configuration for a single ESXi host with four 1GB NICs supporting Fault
Tolerance. Other hosts in the FT cluster would be configured similarly.
This example uses four port groups configured as follows:
n
VLAN A: Virtual Machine Network Port Group-active on vmnic2 (to physical switch #1); standby on
vmnic0 (to physical switch #2.)
n
VLAN B: Management Network Port Group-active on vmnic0 (to physical switch #2); standby on
vmnic2 (to physical switch #1.)
vSphere Administration with the vSphere Client
394 VMware, Inc.