What should the optimum configuration be on the Cisco switch side to allow for seamless failover in the event of a failed port.

This is asking more for confirmation that the below is correct rather than troubleshooting an issue although I am a little unsure as to the reasons why I should disable STP on the VLAN (as generally recommended).

I have set up a connection between an ESXi host 5.1 (2 teamed vmnics) and 2 Cisco 3850 stacked switches. The configuration is a follows;
 
The vSwitch Properties (2 vmnics);
Load Balancing: Route Based on the originating  Virtual Port ID
Network Failover Detection: Link Status
Notify Switches: Yes
Failback: Yes
Both vmnics are active active
The port group for the VM's use VLAN 50
 
On the Stacked Switches;
The 2 ports that the vmnics are connected to are both have portfast enabled and are configured as trunking ports. The ports are configured for VLAN 50. STP is disabled for that VLAN. Etherchannel hasn't been configured.  

Does this look ok?
raven7602Asked:
Who is Participating?
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:
That looks okay, are you having any issues ?

Have you tested ?
0

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
raven7602Author Commented:
I was having issues with using the 'Route based on IP hash' load balancing policy whereby the switch ports were in a flapping state. It transpires I shouldn't have been using Failback within the policy. As it happens using the  'Route Based on the originating  Virtual Port ID' seems to be working as an alternative but with Failback enabled. Thanks for your reply.
0
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
Network Architecture

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.