Ubuntu 16.04.03 bonding issues

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Ubuntu 16.04.03 bonding issues

Konstantin Raskoshnyi
Hello everyone,
I set up bonding, here's the config

root@host:/etc/network# cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback
# eth0
auto eth0
  iface eth0 inet manual
  bond-master bond0
  bond-primary eth0

# eth1
auto eth1
  iface eth1 inet manual
  pre-up sleep 5
  bond-master bond0


# bond0
auto bond0
iface bond0 inet static
  address 192.168.56.208
  gateway 192.168.56.1
  netmask 255.255.255.0
  bond-mode 1
  bond-miimon 100
  bond-slaves none
root@host:/etc/network#



eth0 becomes master by default and works just fine, when I unplug the cable from eth0, the logs tell me that eth1 now is master and eth0 is down. But I cannot ping, ssh to the machine. Also machine cannot ping def gw after that. 

before wire unplugged,

root@host:/etc/network# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0 (primary_reselect always)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 2
Permanent HW addr: 08:00:27:99:b8:97
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:2b:f0:2f
Slave queue ID: 0

after 

root@host:/etc/network# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0 (primary_reselect always)
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 3
Permanent HW addr: 08:00:27:99:b8:97
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:2b:f0:2f
Slave queue ID: 0

Any thoughts?
Thank you

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Ubuntu 16.04.03 bonding issues

Tom H
On Fri, Feb 2, 2018 at 10:15 PM, Konstantin Raskoshnyi
<[hidden email]> wrote:

>
> I set up bonding, here's the config
>
> root@host:/etc/network# cat interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
> # eth0
> auto eth0
>   iface eth0 inet manual
>   bond-master bond0
>   bond-primary eth0
>
> # eth1
> auto eth1
>   iface eth1 inet manual
>   pre-up sleep 5
>   bond-master bond0
>
> # bond0
> auto bond0
> iface bond0 inet static
>   address 192.168.56.208
>   gateway 192.168.56.1
>   netmask 255.255.255.0
>   bond-mode 1
>   bond-miimon 100
>   bond-slaves none
> root@host:/etc/network#
>
> eth0 becomes master by default and works just fine, when I unplug the cable
> from eth0, the logs tell me that eth1 now is master and eth0 is down. But I
> cannot ping, ssh to the machine. Also machine cannot ping def gw after that.
>
> before wire unplugged,
>
> root@host:/etc/network# cat /proc/net/bonding/bond0
> Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
>
> Bonding Mode: fault-tolerance (active-backup)
> Primary Slave: eth0 (primary_reselect always)
> Currently Active Slave: eth0
> MII Status: up
> MII Polling Interval (ms): 100
> Up Delay (ms): 0
> Down Delay (ms): 0
>
> Slave Interface: eth0
> MII Status: up
> Speed: 1000 Mbps
> Duplex: full
> Link Failure Count: 2
> Permanent HW addr: 08:00:27:99:b8:97
> Slave queue ID: 0
>
> Slave Interface: eth1
> MII Status: up
> Speed: 1000 Mbps
> Duplex: full
> Link Failure Count: 0
> Permanent HW addr: 08:00:27:2b:f0:2f
> Slave queue ID: 0
>
> after
>
> root@host:/etc/network# cat /proc/net/bonding/bond0
> Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
>
> Bonding Mode: fault-tolerance (active-backup)
> Primary Slave: eth0 (primary_reselect always)
> Currently Active Slave: eth1
> MII Status: up
> MII Polling Interval (ms): 100
> Up Delay (ms): 0
> Down Delay (ms): 0
>
> Slave Interface: eth0
> MII Status: down
> Speed: Unknown
> Duplex: Unknown
> Link Failure Count: 3
> Permanent HW addr: 08:00:27:99:b8:97
> Slave queue ID: 0
>
> Slave Interface: eth1
> MII Status: up
> Speed: 1000 Mbps
> Duplex: full
> Link Failure Count: 0
> Permanent HW addr: 08:00:27:2b:f0:2f
> Slave queue ID: 0

Your config looks fine, except perhaps "pre-up sleep 5" which isn't
needed since you have "bond-primary eth0".

Does bond0 failover successfully if you use "bond-mode 0" (as a test)?

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users