Ethernet Bonding in LINUX
Ethernet Bonding in LINUX
by Johny Darwin
Ethernet bonding is also known as port teaming and port trunking.
When there is requirement for fault tolerance or load balancing you can consider ethernet bonding as an easy option.
Ethernet bonding is also known as port teaming and port trunking.
When there is requirement for fault tolerance or load balancing you can consider ethernet bonding as an easy option.
Fault tolerance
You can have one active and one backup network interfact. In case the active interface goes down the backup interfact takes over and provides fault tolerance.
Load balancing
There are algorithms in ethernet bonding which can provide load balancing, for example, by sending information sequentially starting with first interface to the last interface. For example, if there are 2 slave interfaces, first frame travel through first interface, and the second frame goes through the second frame, then the third frame goes through the first interface and so on. There are different modes available for load balancing, like the XOR mode.
The lab setup
For this setup I have setup a virtual machine using kvm virtual-manager running in RHEL 6.5 and added two ethernet interfaces, eth0 and eth1.
Start Bonding
This tutorial creates a bond using 2 ethernet interfaces, eth0 and eth1 to create a single bonded interface called bond0. You need to create three configuration files:
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
For your reference I am listing the files as below:
[root@vm-1 network-scripts]# cat ifcfg-bond0
DEVICE="bond0"
IPADDR=192.168.122.207
NETMASK=255.255.255.0
GATEWAY=192.168.122.1
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
USRCTL=no
##BONDING_OPTS="mode=active-backup" YES
BONDING_OPTS="mode=1"
The option BONDING_OPTS is set to mode 1, that means Bonding Mode: fault-tolerance (active-backup). You can change this to mode=0 to get the load balancing mode turned on. Always restart the network after changing the setup files.
[root@vm-1 network-scripts]# cat ifcfg-eth0
DEVICE="eth0"
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
MASTER=bond0
SLAVE=yes
USRCTL=no
[root@vm-1 network-scripts]# cat ifcfg-eth1
DEVICE="eth1"
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
MASTER=bond0
SLAVE=yes
USRCTL=no
You should note the settings SLAVE=yes and MASTER=bond0. The SLAVE setting indicates that eth1 will act as slave to the bond0 MASTER. In fact both the interfaces eth0 and eth1 are salves to bond0.
Without the bonding module loaded into your kernel, you cannot get your bonding setup to work. Load the bonding module persistently:
[root@vm-1 modules]# cat bond.modules
#!/bin/sh
exec /sbin/modprobe bonding >/dev/null 2>&1
You can also use the modprobe command to load the bonding module, but remember to make it persistent as mentioned above.
modprobe bonding
Verify that the bonding module has been loaded by the kernel:
[root@vm-1 modprobe.d]# lsmod | grep bond
bonding 125610 0
ipv6 322029 30 bonding,ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6
After creating the setup files as above, restart the network or reboot your computer.
[root@vm-1 network-scripts]# service network restart
Shutting down interface bond0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
To verify the status of your new bond interface, look into the bond0 kernel file as below, and you should get MII Status: up, if not check the you did not miss anything in the setup as told above, also check the /var/log/messages log file for any errors that you need to fix.
[root@vm-1 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 52:54:00:95:e3:57
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 52:54:00:dc:68:22
Slave queue ID: 0
Here is a dump of your active network interfaces after bonding has been done and running successfully.
[root@vm-1 network-scripts]# ifconfig
bond0 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
inet addr:192.168.122.207 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe95:e357/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:4233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1341 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:286667 (279.9 KiB) TX bytes:283533 (276.8 KiB)
eth0 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3642 errors:0 dropped:0 overruns:0 frame:0
TX packets:1183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:251024 (245.1 KiB) TX bytes:249492 (243.6 KiB)
eth1 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:593 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:35775 (34.9 KiB) TX bytes:34317 (33.5 KiB)
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1576 (1.5 KiB) TX bytes:1576 (1.5 KiB)
You can explore the miimon option, which tells the interval in milliseconds for link monitoring. Usually miimon=100 is sufficient.
BONDING_OPTS="mode=1 miimon=100"
This option is now deprecated as the bonding uses the netif_carrier_ok flag to find out the status of the slaves.
/etc/sysconfig/network-scripts/ifcfg-bond0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
For your reference I am listing the files as below:
[root@vm-1 network-scripts]# cat ifcfg-bond0
DEVICE="bond0"
IPADDR=192.168.122.207
NETMASK=255.255.255.0
GATEWAY=192.168.122.1
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
USRCTL=no
##BONDING_OPTS="mode=active-backup" YES
BONDING_OPTS="mode=1"
The option BONDING_OPTS is set to mode 1, that means Bonding Mode: fault-tolerance (active-backup). You can change this to mode=0 to get the load balancing mode turned on. Always restart the network after changing the setup files.
[root@vm-1 network-scripts]# cat ifcfg-eth0
DEVICE="eth0"
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
MASTER=bond0
SLAVE=yes
USRCTL=no
[root@vm-1 network-scripts]# cat ifcfg-eth1
DEVICE="eth1"
BOOTPROTO="none"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
MASTER=bond0
SLAVE=yes
USRCTL=no
You should note the settings SLAVE=yes and MASTER=bond0. The SLAVE setting indicates that eth1 will act as slave to the bond0 MASTER. In fact both the interfaces eth0 and eth1 are salves to bond0.
Without the bonding module loaded into your kernel, you cannot get your bonding setup to work. Load the bonding module persistently:
[root@vm-1 modules]# cat bond.modules
#!/bin/sh
exec /sbin/modprobe bonding >/dev/null 2>&1
You can also use the modprobe command to load the bonding module, but remember to make it persistent as mentioned above.
modprobe bonding
Verify that the bonding module has been loaded by the kernel:
[root@vm-1 modprobe.d]# lsmod | grep bond
bonding 125610 0
ipv6 322029 30 bonding,ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6
After creating the setup files as above, restart the network or reboot your computer.
[root@vm-1 network-scripts]# service network restart
Shutting down interface bond0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
To verify the status of your new bond interface, look into the bond0 kernel file as below, and you should get MII Status: up, if not check the you did not miss anything in the setup as told above, also check the /var/log/messages log file for any errors that you need to fix.
[root@vm-1 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 52:54:00:95:e3:57
Slave queue ID: 0
Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 52:54:00:dc:68:22
Slave queue ID: 0
Here is a dump of your active network interfaces after bonding has been done and running successfully.
[root@vm-1 network-scripts]# ifconfig
bond0 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
inet addr:192.168.122.207 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe95:e357/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:4233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1341 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:286667 (279.9 KiB) TX bytes:283533 (276.8 KiB)
eth0 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3642 errors:0 dropped:0 overruns:0 frame:0
TX packets:1183 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:251024 (245.1 KiB) TX bytes:249492 (243.6 KiB)
eth1 Link encap:Ethernet HWaddr 52:54:00:95:E3:57
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:593 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:35775 (34.9 KiB) TX bytes:34317 (33.5 KiB)
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1576 (1.5 KiB) TX bytes:1576 (1.5 KiB)
You can explore the miimon option, which tells the interval in milliseconds for link monitoring. Usually miimon=100 is sufficient.
BONDING_OPTS="mode=1 miimon=100"
This option is now deprecated as the bonding uses the netif_carrier_ok flag to find out the status of the slaves.
Testing your setup
[root@vm-1 ~]# cat /proc/net/bonding/bond0 | grep "Currently Active Slave"
Currently Active Slave: eth0
[root@vm-1 ~]# ifdown eth0
[root@vm-1 ~]# cat /proc/net/bonding/bond0 | grep "Currently Active Slave"
Currently Active Slave: eth1
The eth1 interface became active when eth0 was brought down.
We again bring up interface eth0, to see that nothing happens and eth1 remains active, an it will remain active unless eth1 itself becomes inactive.
[root@vm-1 ~]# ifup eth0
[root@vm-1 ~]# cat /proc/net/bonding/bond0 | grep "Currently Active Slave"
Currently Active Slave: eth1
Summary
This article tells what bonding is and how to setup bonding using 2 interfaces in Linux. The article also teaches how to test the setup using simple commands ifup and ifdown.
System Logs collected related only to bond0 interface:
[root@vm-1 log]# grep -i bond messages
Jan 26 16:54:30 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:54:30 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-bond0.
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-bond0.
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: read connection 'System bond0'
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-bond0
Jan 26 16:56:02 vm-1 NetworkManager[1545]: Activation (eth0) starting connection 'System bond0'
Jan 26 16:56:03 vm-1 NetworkManager[1545]: Policy set 'System bond0' (eth0) as default for IPv4 routing and DNS.
Jan 26 17:00:47 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:00:47 vm-1 NetworkManager[1545]: /sys/devices/virtual/net/bond0: couldn't determine device driver; ignoring...
Jan 26 17:01:37 vm-1 NetworkManager[1545]: Policy set 'System bond0' (eth0) as default for IPv4 routing and DNS.
Jan 26 17:01:37 vm-1 NetworkManager[1545]: Policy set 'System bond0' (eth0) as default for IPv4 routing and DNS.
Jan 26 17:01:37 vm-1 kernel: bonding: bond0: doing slave updates when interface is down.
Jan 26 17:01:37 vm-1 kernel: bonding: unable to remove non-existent slave eth1 for bond bond0.
Jan 26 17:01:37 vm-1 NetworkManager[1545]: Policy set 'System bond0' (eth0) as default for IPv4 routing and DNS.
Jan 26 17:01:37 vm-1 NetworkManager[1545]: Policy set 'System bond0' (eth0) as default for IPv4 routing and DNS.
Jan 26 17:01:41 vm-1 NetworkManager[1545]: Connection 'System bond0' auto-activation failed: (2) Device not managed by NetworkManager
Jan 26 17:28:44 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: doing slave updates when interface is down.
Jan 26 17:35:49 vm-1 kernel: bonding: unable to remove non-existent slave eth0 for bond bond0.
Jan 26 17:35:49 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:35:49 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:35:50 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:35:50 vm-1 kernel: bonding: bond0: enslaving eth1 as an active interface with an up link.
Jan 26 17:35:50 vm-1 kernel: bond0: IPv6 duplicate address fe80::5054:ff:fe95:e357 detected!
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:46:25 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:46:25 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:46:27 vm-1 avahi-daemon[1472]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Withdrawing address record for fe80::5054:ff:fe95:e357 on bond0.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: setting mode to balance-rr (0).
Jan 26 17:51:17 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:51:17 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: enslaving eth1 as an active interface with an up link.
Jan 26 17:51:17 vm-1 kernel: bond0: IPv6 duplicate address fe80::5054:ff:fe95:e357 detected!
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:51:41 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:51:41 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:51:42 vm-1 avahi-daemon[1472]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:59:13 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:59:57 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:59:57 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:59:57 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 18:01:03 vm-1 avahi-daemon[1519]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 18:01:52 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 18:01:52 vm-1 kernel: bonding: bond0 is being created...
Jan 26 18:01:52 vm-1 kernel: bonding: cannot add bond bond0; already exists
Jan 26 18:01:52 vm-1 kernel: bonding: Bond creation failed.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 18:01:52 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 18:01:52 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 19:02:58 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:02:58 vm-1 kernel: bonding: bond0: releasing backup interface eth1
Jan 26 19:03:20 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:03:20 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:04:19 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:04:19 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:05:52 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:05:52 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:08:42 vm-1 avahi-daemon[1544]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 19:13:12 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 19:13:12 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 19:13:12 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
That's all folks!
me @ jdarwin@rediffmail.com
Jan 26 16:54:30 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:54:30 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-bond0.
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:55:10 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: removed /etc/sysconfig/network-scripts/ifcfg-bond0.
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-bond0 ...
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: read connection 'System bond0'
Jan 26 16:56:02 vm-1 NetworkManager[1545]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-bond0
Jan 26 16:56:02 vm-1 NetworkManager[1545]:
Jan 26 16:56:03 vm-1 NetworkManager[1545]:
Jan 26 17:00:47 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:00:47 vm-1 NetworkManager[1545]:
Jan 26 17:01:37 vm-1 NetworkManager[1545]:
Jan 26 17:01:37 vm-1 NetworkManager[1545]:
Jan 26 17:01:37 vm-1 kernel: bonding: bond0: doing slave updates when interface is down.
Jan 26 17:01:37 vm-1 kernel: bonding: unable to remove non-existent slave eth1 for bond bond0.
Jan 26 17:01:37 vm-1 NetworkManager[1545]:
Jan 26 17:01:37 vm-1 NetworkManager[1545]:
Jan 26 17:01:41 vm-1 NetworkManager[1545]:
Jan 26 17:28:44 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: doing slave updates when interface is down.
Jan 26 17:35:49 vm-1 kernel: bonding: unable to remove non-existent slave eth0 for bond bond0.
Jan 26 17:35:49 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:35:49 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:35:49 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:35:50 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:35:50 vm-1 kernel: bonding: bond0: enslaving eth1 as an active interface with an up link.
Jan 26 17:35:50 vm-1 kernel: bond0: IPv6 duplicate address fe80::5054:ff:fe95:e357 detected!
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:35:51 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:46:25 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:46:25 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:46:25 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:46:25 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:46:26 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:46:27 vm-1 avahi-daemon[1472]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:51:17 vm-1 avahi-daemon[1472]: Withdrawing address record for fe80::5054:ff:fe95:e357 on bond0.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: setting mode to balance-rr (0).
Jan 26 17:51:17 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:51:17 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:51:17 vm-1 kernel: bonding: bond0: enslaving eth1 as an active interface with an up link.
Jan 26 17:51:17 vm-1 kernel: bond0: IPv6 duplicate address fe80::5054:ff:fe95:e357 detected!
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:51:18 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Withdrawing address record for 192.168.122.207 on bond0.
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:41 vm-1 avahi-daemon[1472]: Interface bond0.IPv4 no longer relevant for mDNS.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:51:41 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:51:41 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:51:41 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:51:42 vm-1 avahi-daemon[1472]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:51:45 vm-1 avahi-daemon[1472]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 17:59:13 vm-1 avahi-daemon[1472]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:59:57 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 17:59:57 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 17:59:57 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 17:59:57 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 17:59:58 vm-1 avahi-daemon[1519]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 18:01:03 vm-1 avahi-daemon[1519]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 18:01:52 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 18:01:52 vm-1 kernel: bonding: bond0 is being created...
Jan 26 18:01:52 vm-1 kernel: bonding: cannot add bond bond0; already exists
Jan 26 18:01:52 vm-1 kernel: bonding: Bond creation failed.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 18:01:52 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 18:01:52 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 18:01:52 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 18:01:52 vm-1 avahi-daemon[1544]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 19:02:58 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:02:58 vm-1 kernel: bonding: bond0: releasing backup interface eth1
Jan 26 19:03:20 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:03:20 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:03:41 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:03:50 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 19:04:02 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:04:19 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:04:19 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:04:45 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:04:58 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: Removing slave eth1
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: releasing active interface eth1
Jan 26 19:05:40 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:05:52 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:05:52 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:08:42 vm-1 avahi-daemon[1544]: Leaving mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 19:13:12 vm-1 kernel: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: setting mode to active-backup (1).
Jan 26 19:13:12 vm-1 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: making interface eth0 the new active one.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: first active interface up!
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: enslaving eth0 as an active interface with an up link.
Jan 26 19:13:12 vm-1 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: Adding slave eth1.
Jan 26 19:13:12 vm-1 kernel: bonding: bond0: enslaving eth1 as a backup interface with an up link.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.122.207.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: New relevant interface bond0.IPv4 for mDNS.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Registering new address record for fe80::5054:ff:fe95:e357 on bond0.*.
Jan 26 19:13:12 vm-1 avahi-daemon[1576]: Registering new address record for 192.168.122.207 on bond0.IPv4.
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: Removing slave eth0
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: Warning: the permanent HWaddr of eth0 - 52:54:00:95:e3:57 - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: releasing active interface eth0
Jan 26 19:14:14 vm-1 kernel: bonding: bond0: making interface eth1 the new active one.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: Adding slave eth0.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: Warning: failed to get speed and duplex from eth0, assumed to be 100Mb/sec and Full.
Jan 26 19:14:22 vm-1 kernel: bonding: bond0: enslaving eth0 as a backup interface with an up link.
That's all folks!
me @ jdarwin@rediffmail.com
Comments
Post a Comment