Blue Gears - 4 Physical NICs with VMware ESX

Virtualization running on hosts with only 2 on-board pNICs and 2 pNIC in a slot have security, redundancy, and performance challenges. Administrators are forced to make choices on how much redundancy is required and where to place it.

How to setup virtual networking when 4 pNICs are involved follows:


pNIC0 -> vSwitch0 -> Portgroup0 (service console)
................. -> Portgroup1 (VMotion)
pNIC1 -> vSwitch0 -> Portgroup2 (Storage Network)
pNIC2 -> vSwitch1 -> Portgroup3 (VM Network)
pNIC3 -> vSwitch1 -> Portgroup3 (VM Network)


With 4 pNICs you can setup two redundant vSwitches each for different purposes one for the service console/management appliance, VMotion, and your Storage Network. While the second vSwitch is solely for the VM Network granted a higher level of redundancy.

The networks attached to vSwitch0 for Service Console and VMotion work best with VLANs however subnets will also work. In addition, it is important to keep the Storage Network on its own pNIC except in a failure case as this will increase its performance.

In this configuration pNIC0 is the failover pNIC for Portgroup2, while pNIC1 is the failover pNIC for Portgroup0. For vSwitch1 there is no need for predefined failover modes, just the default which includes vSwitch Port ID based load balancing. In other words, load balancing is outbound only and based on the port to which the VM is connected.

This method will grant the most redundancy, security, and performance for a 4 pNIC configuration.

• Network Management
• Blue Gears
• ESX
• Haletky
• pNIC
• Texiwill
• VMware