ESX VMotion network question

I am having issues run VMotion in my ESX 5.1 environment.  Research I've been reading indicates I should have the VMotion network segregated.  I have a dedicated physical NIC for VMotion, but it keeps timing out.  I can create a new subnet and isolate it on its own switch between to the 2 hosts, but wouldn't the iSCSI SAN that hosts the VMs need access to this VMotion network as well?  I am attempting to migrate the VM from 1 host to another, as well as change it from a datastore on an older SAN to a new one.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's best practice and recommended to have a seperate network, physical, or VLAN, or different IP Address range for your vMotion VMKernel Portgroups....BUT it's not an absolute necessary or it will not work....

Can you upload a screenshot of your host networking.....

and we can use the command vmkping to test your communications between vMotion Portgroups...

So you are doing Storage vMotion ?
DTUserAuthor Commented:
I did a vmkping and it found the other host fine, but when I do a route print it only shows the iSCSI nic (not the one I currently had VMotion enabled on, which is in the same subnet)

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, so is the vMotion Interface.

How about change it's IP completely to and 1.2 on both servers.

then use vmkping, and use the new -i interface to send packets through vmk0

also make sure you have tag, selected these portgroups for vmotion.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DTUserAuthor Commented:
Yes, that's what I was intending to do, I just want to make sure that the SAN doesn't have to have access to this new subnet ( in your example)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
any private IP Address range will do 10.x, 172.x, 192.x
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.