asked on

NIC teaming VMware vSwitch

I have four physical NICs and only one is used in the vSwitch. What is your recommedation by adding one more NIC to the vSwitch? How to do it with 10 VMs in production?

Mr Tortu(r)e

hi,
What type of vswitch are you using please, standard or distributed?

std
vswitch properties, NIC tab, add, OK, zero issue with running VM IF all your NICs are on the same network.

distributed
same process but you need to add "dvuplinks", and totally other menus, I can't remember them.

Member_2_7349958

ASKER

Please see attached file.

So run a cable from another port on the switch to the another NIC. Go to configuration -> networking -> vSwitch properties -> Network adapters Tab -> Add -> Ok. Is this correct?

Also what is your thoughts in adding another NIC, what are the benefits and how will improve performance?
vm1.jpg
vm2.jpg

ASKER CERTIFIED SOLUTION

Dariusz Tyka

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Mr Tortu(r)e

Hi,
+1 with above comment.

So run a cable from another port on the switch to the another NIC. Go to configuration -> networking -> vSwitch properties -> Network adapters Tab -> Add -> Ok. Is this correct?

yes correct

Also what is your thoughts in adding another NIC, what are the benefits and how will improve performance?

You could have this configuration :
vSwitch 0 - vmnic0 and vmnic1
ESX MGMT - vmnic 0 active and vmnic1 standby
VMotion - vmnic 1 active and vmnic0 standby

vSwitch1 - vmnic2 and vmnic3
VM port group with both NIC actives

Member_2_7349958

ASKER

1. I understand the security aspect as both mgmt and prod are on same vlan but does it affect performance in anyway?

2. Do I have to shutdown all VMs and put the host in maintenance mode to separate both the networks?

3. What is the mgmt port connected to the switch called? I see that is the far left port on the server.

4. What are the steps to change the mgmt static ip?

Mr Tortu(r)e

Hi,

1. I understand the security aspect as both mgmt and prod are on same vlan but does it affect performance in anyway?

yes
mgmt vmkernel, vmotion, and VM network should be separate
for example vmotion network has a specific use : almost always no traffic, then big hit at full speed for some minutes
It can slow down vm network.

2) to switch VM from vswitch to another there is no downtime, considering your network is the same
Then create your VLAN and do it from the physical switch part

3) which mgmt port?

4) do it locally or remotely (with remote server mgmt console idrac or ilo or imm etc.. depending on your material) from DCUI, meaning the ESX console screen

Member_2_7349958

ASKER

Can you list detailed steps to change the mgmt network to different vlan and separating the VMs to different vSwitch. Also let me know if this needs to schedule downtime. As right now both mgmt and vms are on same vlan. I really appreciate your help.

Member_2_7349958

ASKER

Mr. Tortur, can you please list detailed steps as per above request. Thank you.

Mr Tortu(r)e

Hi,

So strange I seem t be alone to answer on this know subject...
Sorry but I work hard these times and had no free time for EE lately.

create your vlan on your network physical switch.
Set your vlan ID on the vSwitch for each component.
Be carefull with mgmt, you could break your own connection. Generally I don't do that on mgmt kernel, maybe you 'll have different advices from other experts.
You will have to schedule a minimal downtime for VM I suppose, for switching from no vlan to vlan ID xx, but this is a network question, not a vmware specific one.