HP BladeSystem Networking Reference Architecture: HP Virtual Connect FlexFabric Module and VMware vSphere 4
13
Virtual Machine
FT Logging
iSCSI
NFS
Service Console Management
vMotion
NetIOC can be used to control identified traffic, when multiple types of traffic are sharing the same
pNIC. In our design example, FT Logging could share the same vDS as the vmkernel, and NetIOC
would be used to control the two types of traffic.
With the design example given, there are three options one could choose to incorporate FT Logging:
Table 2-2 VMware Fault Tolerance Options
FT Desi
g
n Choice Justification
Ratin
g
Share with VMotion
network
The design choice to keep VMotion traffic internally to the Enclosure
allows the use of low latency links for inter-Enclosure communication.
By giving enough bandwidth for VMotion and FT traffic, while
defining a NetIOC policy, latency should not be an issue.
***
Non-redundant VMotion
and FT networks
Dedicate one pNIC for VMotion traffic, and the other for FT logging
traffic. Neither network will provide pNIC redundancy.
**
A
dd additional
FlexFabric Adapters
and Modules
This option increases the overall CapEx to the solution, but will
provide more bandwidth options.
*
Hypervisor Load Balancing Algorithms
VMware provides a number of different NIC teaming algorithms, which are outlined in Table 2-2. As
the table shows, any of the available algorithms can be used, except IP Hash. IP Hash requires
switch assisted load balancing (802.3ad), which Virtual Connect does not support 802.3ad with
server downlink ports. HP and VMware recommend using Originating Virtual Port ID, as shown in
Table 2-2.
Table 2-3 VMware Load Balancing Algorithms
Name Al
g
orithm
Works with VC
Originating Virtual Port
ID
Choose an uplink based on the virtual port where the
traffic entered the virtual switch.
Yes
Source MAC Address MAC Address seen on vnic port
Yes
IP Hash
Hash of Source and Destination IP’s. Requires switch
assisted load balancing, 802.3ad. Virtual Connect
does not support 802.3ad on server downlink ports,
as 802.3ad is a Point-to-Point bonding protocol.
No
Explicit Failover Highest order uplink from the list of Active pNICs. Yes