Long post below. Decided to edit and get to the point.
We have four servers.
1 and 2 are the same model number, NICs, etc.
3 NICs for DATA.
3 NICs for iSCSI.
My networking guy set it up so that vSwitch0 is for data and vSwitch1 is for iSCSI.
Servers 3 and 4 are the same.
4 NICs for DATA.
4 NICs for iSCSI.
Server 3 and 4 are FAR from consistent with vSwitch networking...
He had an iSCSI NIC in the DATA vSwitch...
My question is - none of these network adapters are set for load balancing or teaming.
If I have 4 data NICs and it isn't set for NIC teaming, is data only going out through one network interface? OR does it use all four Ethernet cables?
I wanted to set this up myself as I've been working with it for a long time... but was told I have too much to do and to hand it off to someone who has been doing it for a very long time.
So I did and server 3 and 4 networking was very inconsistent.
So now I'm fixing it and need some recommendations on the networking part of it so that I am balancing traffic through all interfaces.
My question is on the very bottom.
So, I need some suggestions.
I have been working with vSphere for many years.
I was given a project to complete, but was told to have someone else do it for me since he's certified in 'everything' as I'm told.
He's smart, nothing against him.
I needed his help because this set-up involves iSCSI going to our QNAPs and I haven't played with iSCSI in my lifetime.
I reviewed his work and vSwitch's across all four servers are all different...
Server 1 and 2 are the same exact model number, same hardware, same NICs, and connected exactly the same.
3 Ethernet going into our physical switch for DATA and 3 Ethernet going into the switch for iSCSI.
Server 3 and 4 are the same exact model number, same hardware, same NICs, and physically connected exactly the same.
4 ports for DATA and 4 ports for iSCSI.
Each server has two vSwitch's.
vSwitch0 is DATA.
vSwitch1 is iSCSI.
Server 4
vSwitch0 - 4 DATA NICs and 1 iSCSI NIC. 1 NIC for management. For the VM network kernel, it uses all 4 DATA NICs and the iSCSI...
Isn't that a no-no? iSCSI is useless if it's going to vSwitch0, correct?
vSwitch1 had 3 iSCSI NICs... we're missing 1 which is connected to the data vSwitch0.
Server 3 is worse.
vSwitch0 has three DATA NICs. TWO for management... All three for VM network kernel. We're missing a data NIC.
vSwitch1 has only two iSCSI NICs configured.
We are missing two DATA NICs and 1 iSCSI NIC.
Between two identical servers, there is no consistency.
Server 1 and 2 are configured the same.
vSwitch0 has three DATA. One for management. Three for VM network.
vSwitch1 has three iSCSI - one on standby.
So instead of people telling me "Oh no give this project to so and so, you don't have time to do it!", I feel like I need to figure this out myself before something breaks and I'm blamed.
There is not any load balancing or NIC teaming set up for any adapter on any server on any vSwitch.
Here is my question -
I fear that all data is passing through a single wire... is this not correct thinking?
Shouldn't I configure NIC teaming so that there is more throughput? OR is that option there for a different scenario?
I know I need to fix servers 3 and 4 and put the physical adapters in the correct switch, but how could I configure this correctly so that all physical adapters are being used to their full capability?
Is NIC teaming and failover already 'configured' based on which physical adapters are going to the kernel?