guidance on nic teaming needed

[wb2]

Could someone shed some light on what is usually configured on the NIC Teaming tab for my vswitches?

My current setup is:

2 nics on management vswitch

3 nics on my iscsi vswtich

3 nics on my VM vswitch

2 nics on my vmotion vswitch

I currently have everything sitting at their defaults.

[AndreTheGiant]

It could work fine.

Just some question:

do you have a DMZ o Internet network?

why 3 NICs for iSCSI? Have you an Equallogic of what storage do you have?

Andrea

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[Texiwill]

Hello,

Check out http://kensvirtualreality.wordpress.com/tag/vswitch/ for all the information you seek. NIC Teaming enables Load Balancing and failover. Some of the vSwitches do not use load balancing but they do use failover.

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009, DABCC Analyst
====
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'
Also available 'VMWare ESX Server in the Enterprise'
SearchVMware Pro|Blue Gears|Top Virtualization Security Links|Virtualization Security Round Table Podcast

Message was edited by: Ken.Cline to correct URL

[digitalex]

That is a fine configuration. Just make sure to spread out the configuration to different NIC cards. 2 NIC configurations for redundancy and load balancing is ideal. A fellow vm admin of mine does his configuration with 4 4Port Intel Nic's (total 16 physical ports) and uses 4 ports for each. Total overkill but very reliable.

[wb2]

Do you think any changes have to done to the nic teaming tab? Or the defaults are ok?

[digitalex]

Just set to Full 1000 and moved both nics to Active/Active with Vlan id on vmotion.

[Texiwill]

Hello,

I use the defaults for most things in this configuration. Only set your NICs away from autonegotiate if your switch ports are also not set to autonegotiate. Autonegotiate is generally the best approach.

Best regards, Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, DABCC Analyst[/url]
Now Available on Rough-Cuts: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing ESX and the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]

[digitalex]

I would agree. Test your config to determine what is best in your environment.