• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Any VMWare specialists here?

SolMiester

Diamond Member
Hi, I have a new build (VM network) that is waiting to go live. I am working with 2 separate hosts, no Vmotion or HA, each host has own storage. Each host has 2 1Gb NICs, 1 already added with static address to v switches and has service console also.

I have the hosts connected to a D-Link 1216T gigabit backbone with twin ports already linked for trunking, however and this is the show stopper, when a connect 2nd cable for 2nd NIC, I lose connectivity!.

ESX server version 3.5, is there anyone here who has knowledge of procedure for teaming the vswitch on the host servers, or a step by step document link?.

Thanks all

Greg
 
Does this Dell article help?

4.1.4 Configuration 4:
In this configuration, NIC 0 is shared between the service console and the VMkernel. NIC 1 is dedicated to VMkernel. NIC 0 and NIC 1 are teamed by the VMkernel
provide a bond. This bonding provides for NIC redundancy and load balancing.
 
Hi, further info rec'd, ESX 3.5 does away with NIC team per sa, now its more like load balancing of the vswitch!....thanks anyway!
 
So to go along with this question, we have a few vm's showing that they really need more bandwidth at the vm level. We have 5 ESX servers with at least 5 NIC's in each. When looking at the VM, it shows it is using 1000 Mb. Is there a way to team 2 NIC's within the particular VM so that it is showing 2000 Mb? Through the VI Client, we have added a second network adapter, but the Windows OS sees it as 2 seperate NIC's.
 
Does the vSwitch NIC teaming features not give you enough bandwidth? Ignore what the OS says, how much bandwidth are you actually pushing (from esxtop or VI client)?

vmxnet doesn't support NIC teaming. There is one possibility that may work. If you are running Windows 64-bit you can install 2 e1000 NICs, then install the latest Intel e1000 drivers which support NIC teaming. haven't tried it.
 
Did you add both NICs to the vSwitch? Then on the physical switch you need to enable link aggregation on the two ports connected to the teamed nics on the ESX Server.
 
Originally posted by: Brazen
Did you add both NICs to the vSwitch? Then on the physical switch you need to enable link aggregation on the two ports connected to the teamed nics on the ESX Server.

No, sorry, this is wrong, ESX 3 did away with this. There is no teaming at all now, only load balancing.

You can add as many NICs as you like to the cswitch and phyiscal host, however you will create a loop if you try trunking at the pswitch.

I wasted many hours working this out.....
 
Back
Top