HP ProLiant BL660c HP BladeSystem Networking Reference Architecture: HP Virtua - Page 8

Important, Table 2-1 VMware vDS Configuration Example

Page 8 highlights

Table 2-1 VMware vDS Configuration Example VMkernel Function VM NetworkingN vDS Name dvs3_vmnet dvPortGroup Name dvPortGroupN_vmnetNNN Figure 2-1: Hypervisor Networking Design Important: Please know that for HP CloudSystem Matrix installations, the dvPortGroup for the Service Console must be named "Management Network." Mixing vSphere Standard Switches and vSphere Distributed Switches is possible. The current scalability limits to the vDS may require some designs to incorporate both. HP would recommend vmkernel functions (vMotion, Management, IP Storage, FT) be assigned to Standard vSwitches, and use vDS for Virtual Machine networking. VMware Fault Tolerance (FT) could introduce more complexity in to the overall design. VMware states that a single 1Gb NIC should be dedicated for FT logging, which would have the potential to starve any shared pNIC with that of another vmkernel function (i.e. VMotion traffic.) FT has not been taken into consideration within this document. Even though FT could be shared with another vmkernel 8

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14

8
Table 2-1 VMware vDS Configuration Example
VMkernel Function
vDS Name
dvPortGroup Name
VM Networking
N
dvs3_vmnet
dvPortGroup
N
_vmnet
NNN
Figure 2-1:
Hypervisor Networking Design
Important
:
Please know that for HP CloudSystem Matrix installations, the dvPortGroup for
the Service Console must be named “Management Network.”
Mixing vSphere Standard Switches and vSphere Distributed Switches is possible.
The current
scalability limits to the vDS may require some designs to incorporate both.
HP would recommend
vmkernel functions (vMotion, Management, IP Storage, FT) be assigned to Standard vSwitches, and
use vDS for Virtual Machine networking.
VMware Fault Tolerance (FT) could introduce more complexity in to the overall design.
VMware
states that a single 1Gb NIC should be dedicated for FT logging, which would have the potential to
starve any shared pNIC with that of another vmkernel function (i.e. VMotion traffic.)
FT has not been
taken into consideration within this document.
Even though FT could be shared with another vmkernel