• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

vSwitch(s) and NIC teaming

H

h0mez

Limp Gawd
Joined
Nov 6, 2006
Messages
444
I think I finally figured out how to setup my vSwitches, I have 2, one for vMotion/IP storage port and then another for the rest. Thats how I setup all 3 hosts.

One of my hosts has 4 nics, so I split them up 2 and 2 between the vswitches. vSwitch0 still has a VMKernal port with vMotion/Ip storage that was setup initially automatically, do I want to remove that since I want all that traffic to go through the vSwitch1.

vSwitch0 has the vSwitch Port(which has NIC teaming enabled), and VM Network(which doesnt have NIC teaming enabled), do I want all those ports to have NIC teaming enabled? Or to go beyond that, do I want every port that can have NIC teaming to have it enabled?
 
How do you have the physical switches configured(LACP/Static LAG,nooftheabove)?

Are you using iSCSI?
 
I have LACP configured for all the sets of NICS, 2 setup for the quad nic so I can get an IP for both vswitchs. Then my other two boxes just have dual nics, so each box has 1 LACP configured for their two ports where I don't have multiple vSwitches(I'm not sure if its beneficial to have two vSwitchs if I only have two nics).

I am not, I am just using NFS.
 
30ro7qe.jpg

r0d27o.jpg

2rqyid5.jpg
 
Last edited:
1. I don't believe LACP is supported without using a dvSwitch. What brand of switch are you using? You are probably better off using a static lag with ip hash.

2. The storage port is not going to benefit performance wise from a LAG, you will still be capped at 1g. On the NFS server side though multiple ports will balance the load. If you are going for fault tolerance though, yes it will protect against the loss of one link.

3. On the dual port servers I would keep with 2 nics in the vSwitch. Override the failover order. Assign one nic to the top of the list for storage, the other for vMotion/vm traffic. Make sure to set a limit on the vMotion vm kernel port though.

4.Make sure to have a different subnet for your management vmkernel and nfs vmkernel interfaces. The nfs traffic is going to default to any interface that resides on the same subnet as the nfs server.
 
geiger said:
1. I don't believe LACP is supported without using a dvSwitch. What brand of switch are you using? You are probably better off using a static lag with ip hash.

2. The storage port is not going to benefit performance wise from a LAG, you will still be capped at 1g. On the NFS server side though multiple ports will balance the load. If you are going for fault tolerance though, yes it will protect against the loss of one link.

3. On the dual port servers I would keep with 2 nics in the vSwitch. Override the failover order. Assign one nic to the top of the list for storage, the other for vMotion/vm traffic. Make sure to set a limit on the vMotion vm kernel port though.

4.Make sure to have a different subnet for your management vmkernel and nfs vmkernel interfaces. The nfs traffic is going to default to any interface that resides on the same subnet as the nfs server.
Click to expand...

I'm using a Dell 5324.

I can switch the Subnet on the quad NIC server, but not the dual NIC servers since I have LACP/LAG and they have 1 IP. I believe I would also have to disable that on the physical switch?
 
You must log in or register to reply here.
Back
Top