Iscsi & Vmotion

[MosheFriedman]

When Setting up the Networking for Iscsi A new standard Switch was created

    

Should any of the VMkernal ports be Vmotion enabled

[weinstein5]

You could but best practice is to create a seperate vmkernel port for vmotion on its own isolated network - 

[MosheFriedman]

Thanks, but where should I put it?, on theRegular Network (which is in the 192.168.168.x range) or on the Storage network (which is in the 10.10.10.x range)

Thanks

Moshe

[iw123]

Strictly speaking you should have a separate range. Another VLAN with no routing so that it is isolated. Or if it is convenient, use dedicated nics using an isolated switch. Normally due to the number of nics on the server, vlan tagging is preferred.

[weinstein5]

Use a completely seperate network segment or vLan  - if you do not have the physical infrastructure to support vlans use a completely different network say 192.168.68.0 since the network traffic will only be between the vmotion enabled vmkernel ports and will not need to be routed anywhere you do not have to worry about a gateway address -

[golddiggie]

We have a VLAN setup just for vMotion traffic... Depending on your network topology, and capability, you could do that too. If nothing else, you do want to isolate the network subnet so that only vMotion traffic flows over it. We have to pNIC's assigned to that vSwitch, in an active/active configuration. Allows for higher bandwidth during normal conditions as well as tolerance of a section going dark (swtich, NIC, etc.). Remember, "no single point of failure" should be your norm...

[MosheFriedman]

That would be great for regular vmotion, but how about Storage Vmotion?

[weinstein5]

the vmotion port does not need to communicate to the SAN - it is only used for communicatioin between ESX hosts - the communication to the SAN is done through the HBAs communicating to the SAN - either FC or iSCSI