greetings,
I'll try this here hope someone will be able to answer or point me to the right direction.
here is the scenario: lets say I have a 'diskless server' (will be virtuallized essentially), this specific server serves workstations without physical disk to be able to boot windows. However, with diskless technology, the ethernet/nics are the most being hammered with heavy workloads, 2nd is the harddisk (if they are plater based) while the processor mostly sleeps.
Mostly and currently with these diskless software, only 1 ethernet/nic is used, never seen they use more than 1 'natively'.
What if I have 3 identical ethernet/nics which supports bonding (specifically balance-alb) and bond them together?, and a thing to note that I only have a 'dumb' single switch (no lacp support)
am not expecting miracles here but my question(s) are:
-- does bonding help out in the scenario above?
-- compared to single connection vs bonding 2 or more on a regular switch, is there improvement in speed and/or load?
I'll try this here hope someone will be able to answer or point me to the right direction.
here is the scenario: lets say I have a 'diskless server' (will be virtuallized essentially), this specific server serves workstations without physical disk to be able to boot windows. However, with diskless technology, the ethernet/nics are the most being hammered with heavy workloads, 2nd is the harddisk (if they are plater based) while the processor mostly sleeps.
Mostly and currently with these diskless software, only 1 ethernet/nic is used, never seen they use more than 1 'natively'.
What if I have 3 identical ethernet/nics which supports bonding (specifically balance-alb) and bond them together?, and a thing to note that I only have a 'dumb' single switch (no lacp support)
am not expecting miracles here but my question(s) are:
-- does bonding help out in the scenario above?
-- compared to single connection vs bonding 2 or more on a regular switch, is there improvement in speed and/or load?