Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The thing we were trying to avoid would be the vMotion/FT traffic affecting the VM traffic. VM traffic is much more important to us than the vMotion/FT traffic.
No i understand, my point is there are other ways to do that.
Well the switches are stacked so from what I understand they will be seen as "the same" switch. I'm not entirely sure on this though.
Standby adapters were suggested to keep redundancy but to not use the adapters unless absolutely necessary.
Or buy the Enterprise Plus license and use Network I/O Control.
Licensing already purchased. As of right now the features of Plus weren't needed. We will deal with I/O control by separating out the traffic on different cards and lose the redundancy if we need to go that route.
Hopefully later down the line I will get the budget to upgrade to Enterprise Plus.
Could be worse. I just did a design for a customer with blades that had 2 Gb ports and that was it.
haha and here i was complaining about not having 10.
I would change all the adapters to Active. Setup the adapters on your physical switch with Link Aggregation. Change the Load Balance to IP HASH, failover detection to Beacon Probing, that way it detects misconfigurations as well.
You have logically segmented your traffic using Vlans. I wouldn't be too concerned about Vmotion traffic, FT, etc during failover. How often do you estimate that's going to occurr? If you're that worried about it, physically segment the VT/FT network adapters. You just wont get the benefits of using all 4 in the team.
I agree with Netjunkie and nitro...I would rather be able to pull from all resources for any function, with the exception of IP based storage.
Does Enterprise Plus work with ESXi and ESX 4.x?
And say you have only the two GB ports, the Vswitch is the one logically load balancing the Console, VMotion and VMs traffic to the physical NICs, which might be using LaCP to the physical switch?
Yeah..that's my bad...I was just reading about this..should've picked up on this...yes..Link Status only..but definately Link Aggregation on the physical switch side...what are you using for the stack, a few 3750's?
I'll be damn I got something right. I'm just so proud of myself I had to reply. Glad it all got tested out, very useful information for sure. I wonder how many times this thread will get hit with google searches
Now heres more of a networking question. With the stacking modules, would there be any reason to stack both the front-end and the back-end switches?
I wanted to ask you, really in general is why I rarely see anyone using vDistributed switches instead of creating multiple vSwitches for each ESXi host. It seems that it would be much easier to manage one or two distributed switches than to manage and setup the same vSwitch setup for every host?
General question really, but wanted to see if you considered that for your build? Since we are a Cisco shop, and for the reasons mentioned above, wee are currently looking into a couple of Cisco Nexus 1000v switches. Looking at the cost, it looks to be a bargin.
IP Hash gives you better load balancing than say Virtual Port ID or Source MAC (basically the same thing). Will it be a problem? Very doubtful. The majority of vSphere clusters use the default Virtual Port ID. I wouldn't stress it. If it turns out to be a problem just add two more NICs to each host.
to bump an older thread, I was wondering how this setup would change if I used Distributed switches? Do I need to do all the fancy port teaming or does that magical happen when setting up vDS?