vMotion and Management on same vswitch

I'm trying to setup vMotion and Management on the same vswitch using 3 vmnics. But vMotion doesn't work. It get stuck on 14% and then gives fails.

This is how it looks like..
vmotion and managementvSwitch0, > Properties
vSwitch > Edit > Nic Teaming
Active = vmnic0, vmnic7, vmnic11
standby = [none]
unused = [none]
vMotion > Edit > Nic Teaming
Active = vmnic11
standby = vmnic0, vmnic7
unused = [empty]
Management > Edit > Nic Teaming
active = vmnic0, vmnic7
standby = vmnic11
unused = [empty]
I have the relevant tick boxes against the management and vmotion traffic types within each port group. The vswitch configuration is mostly default stuff, promiscuous = reject, mac address change = accept, forged transmits = accept, traffic shaping = disabled. MTU across the vswitch, port groups and physical switches is 1500.
Load balancing= Route based on the originating virtual port ID
Network Failover Detection= Link status only
Notify Switches= Yes
Failback= Yes

The thing is that if try this configuration with only 2 vmics it works. So what's the deal using 3 vmnics?
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:
I notice that you are using a VLAN 300.

Are all you physical network ports, tagged with VLAN 300?

Have you confirmed using vmkping (source to target server IP Address)

there is good communication there?

do you not have another nic, and then create a two nic vSwitch dedicated for vMotion ?
Bes4dminAuthor Commented:
Yes, the ports on the physical switch are configured accordingly.  With pvid for the management vlan and tagged for the vmotion vlan.

I found it's kind of a bug, I was at first attempting to add the new vmk0 on the already existing management vswitch as I described above. After that I removed the existing vMotion vswitch that I had. The newly created vMotion didn't work.

Only when I deleted both vMotion vswitches, the original and the newly created. And then only created the one as per the description above it worked.

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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Not sure what is going on here, we would create a new vSwitch, dedicated for vMotion, with two physical nics, with failover as per iSCSI.

This is best practice and recommended.
Bes4dminAuthor Commented:
Yeah, that's the way to go but in this particular host I don't have enough nics to do that I'm afraid.
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.