NIC bonding - unmanaged switch in LAN (no connection/no DHCP on VM)...

[jaceqp]

Hi there.
I'm testing out nic bonding since my test server has 3x1GB NICs. I want to achieve fault tolerance + increased performance. LAN environment has no advanced/managed switches so for example 802.3ad is not an option.

I've tried various types of bonding, for now I have balance-rr what's your suggestion on non-managed infrastructure?. PVE ping test shows sequential NIC LED activity. Disconnecting ethernet cables in various sequences keeps ping going so bond seem to work. However using same bond on a vm (via vmbr obviously) doesn't provide network/internet access to VM itself. VM's network adapter does not recieve DHCP settings from the main router. No network connection with manual IP setup aswell. Any ideas?

Here's my current /etc/network/interfaces setup:

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto eno3
iface eno3 inet manual

auto eno4
iface eno4 inet manual

auto bond0
iface bond0 inet manual
        bond-slaves eno2 eno3 eno4
        bond-miimon 100
        bond-mode balance-rr
#BOND LAN

# backup PM interface
auto vmbr0
iface vmbr0 inet static
        address 192.168.0.114/24
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.0.115/24
        gateway 192.168.0.200
        bridge-ports bond0
        bridge-stp off
        bridge-fd 0

And there's my VM (test win10) conf file:

/etc/pve/qemu-server/100.conf   [----]  0 L:[  1+ 0   1/ 18] *(0   / 509b) 0097 0x061                                    [*][X]
agent: 1
boot: order=scsi0;ide2;net0
cores: 2
ide0: local:iso/virtio-win-0.1.190.iso,media=cdrom,size=489986K
ide2: none,media=cdrom
machine: pc-q35-5.2
memory: 4096
name: testW10
net0: virtio=16:52:D5:04:C7:0F,bridge=vmbr1,firewall=1
numa: 0
ostype: win10
scsi0: local-lvm:vm-100-disk-0,backup=0,discard=on,size=50G
scsi1: local-lvm:vm-100-disk-1,backup=0,discard=on,size=30G
scsihw: virtio-scsi-pci
smbios1: uuid=afc53342-f064-4fd2-b9d0-fbea59048d6a
sockets: 1
vmgenid: 97b8d3bf-f924-4aaf-bba0-fbdc020cef1e

 

[spirit]

for bonding mode, see:
https://www.kernel.org/doc/Documentation/networking/bonding.txt

5. Switch Configuration
=======================

    For this section, "switch" refers to whatever system the
bonded devices are directly connected to (i.e., where the other end of
the cable plugs into).  This may be an actual dedicated switch device,
or it may be another regular system (e.g., another computer running
Linux),

    The active-backup, balance-tlb and balance-alb modes do not
require any specific configuration of the switch.

    The 802.3ad mode requires that the switch have the appropriate
ports configured as an 802.3ad aggregation.  The precise method used
to configure this varies from switch to switch, but, for example, a
Cisco 3550 series switch requires that the appropriate ports first be
grouped together in a single etherchannel instance, then that
etherchannel is set to mode "lacp" to enable 802.3ad (instead of
standard EtherChannel).

    The balance-rr, balance-xor and broadcast modes generally
require that the switch have the appropriate ports grouped together.
The nomenclature for such a group differs between switches, it may be
called an "etherchannel" (as in the Cisco example, above), a "trunk
group" or some other similar variation.  For these modes, each switch
will also have its own configuration options for the switch's transmit
policy to the bond.  Typical choices include XOR of either the MAC or
IP addresses.  The transmit policy of the two peers does not need to
match.  For these three modes, the bonding mode really selects a
transmit policy for an EtherChannel group; all three will interoperate
with another EtherChannel group.

so: " The active-backup, balance-tlb and balance-alb modes do not
require any specific configuration of the switch.

 

[jaceqp]

I've reconfigured bond to balance-tlb, then balance-alb - same thing - no network under VM. I've also installed ubuntu CT - same thing. Ping 1.1.1.1 = network is unreachable.
BTW: on my test environment I'm using 8-port Netgear gigabit desktop switch plus TL-R470+ router...