Link to home
Start Free TrialLog in
Avatar of hongedit
hongeditFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Which network to vMotion over?

In the attached pic below (why cant I attach a pic to the OP?) it shows my VMWare network.

2 vSwitches, Data and iSCSI

At the moment my vMotion is enabled on the Management Network (on the Data vSwitch).

However questions have been raised to suggest that actually, it should be enabled on the iSCSI network instead.

This also brings up another question - what happens if vMotion is enabled on multple networks? Which does it use?
Avatar of hongedit
hongedit
Flag of United Kingdom of Great Britain and Northern Ireland image

ASKER

User generated image
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Due to the amount of traffic that vMotion can cause, it's actually recommended, to use a seperate network for vMotion.

Hence, why it's "normally" associated with the Managment Network, because management network is low traffic, unless you use it to backup.

So iSCSI vSwitch is probably not the best as it's responsible for your storage network.
So should my Management Network be attached to another vSwitch on a completely seperate subnet, and not on my Data network as I have it now?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
But yes in an ideal world - 4 vSwitches.

vSwitch0 - Management Network Only
vSwitch1 - VM Network Only
vSwitch2 - iSCSI Storage Network
vSwitch3 - vMotion Network

All at least teamed, with two pNics for redundancy across physical switches.

Now you only have six nics, so you need to make best use of six nics.

So you would probably put the vMotion, on the "lowest" vSwitch, theory is traffic will not get lost on a quiet vSwitch.

Have a look and analyse you network, and see if the third NIC, on both vSwitches is necessary.

One of the biggest management holes in vCenter of ESX is the vSphere Client can indicate that VM network traffic is causing a 1 GB Ethernet adapter to have a 99% utilization rate. But strangely, it doesn't display which kind of traffic is going across the virtual networks, where it came from or where it's going.

To learn which traffic is going across a virtual network, there's a free tool for vSphere: Xangati for ESX, a virtual appliance that tracks conversations on the virtual network. It's great for troubleshooting any virtual network issue, analyzing virtual desktop infrastructure and correlating vCenter performance stats with virtual network stats.

It's available as a fanastic FREE download here.

http://xangati.com/try-it-free/