Bond adapters failed at same time

Solution Verified - Updated -

Issue

  • Bond adapters failed at same time
  • The logs reveal no 'link down' events. The bond just goes down and then comes back up:

The bonds going down:

Jul 17 18:19:11 hostname kernel: bond0: Removing slave eth0
Jul 17 18:19:11 hostname kernel: bond0: Releasing active interface eth0
Jul 17 18:19:11 hostname kernel: bond0: the permanent HWaddr of eth0 - 6a:2c:f4:e8:1a:a6 - is still in use by bond0 - set the HWaddr of eth0 to a different address to avoid conflicts
Jul 17 18:19:11 hostname kernel: bond0: making interface eth1 the new active one
Jul 17 18:19:11 hostname kernel: bond0: Removing slave eth1
Jul 17 18:19:11 hostname kernel: bond0: Releasing active interface eth1
Jul 17 18:19:11 hostname kernel: be2net 0000:03:00.1: MAC address changed to 4b:2e:a0:3e:bf:e2
Jul 17 18:19:11 hostname kernel: bond1: Removing slave eth
Jul 17 18:19:11 hostname kernel: bond1: Releasing active interface eth2
Jul 17 18:19:11 hostname kernel: bond1: the permanent HWaddr of eth2 - 23:13:bc:ec:86:1c - is still in use by bond1 - set the HWaddr of eth2 to a different address to avoid conflicts
Jul 17 18:19:11 hostname kernel: bond1: making interface eth3 the new active one
Jul 17 18:19:12 hostname kernel: bond1: Removing slave eth3
Jul 17 18:19:12 hostname kernel: bond1: Releasing active interface eth3

And the bonds coming back up:

Jul 17 18:19:13 hostname kernel: bond0: Setting MII monitoring interval to 100
Jul 17 18:19:13 hostname kernel: 8021q: adding VLAN 0 to HW filter on device bond0
Jul 17 18:19:13 hostname kernel: bond0: Setting MII monitoring interval to 100
Jul 17 18:19:13 hostname kernel: bond0: Adding slave eth0
Jul 17 18:19:13 hostname kernel: be2net 0000:03:00.0: eth0: Link is Up
Jul 17 18:19:13 hostname kernel: 8021q: adding VLAN 0 to HW filter on device eth0
Jul 17 18:19:13 hostname kernel: bond0: making interface eth0 the new active one
Jul 17 18:19:13 hostname kernel: bond0: Enslaving eth0 as an active interface with an up link
Jul 17 18:19:13 hostname kernel: bond0: Adding slave eth1
Jul 17 18:19:13 hostname kernel: be2net 0000:03:00.1: MAC address changed to 6a:2c:f4:e8:1a:a6
Jul 17 18:19:13 hostname kernel: be2net 0000:03:00.1: eth1: Link is Up
Jul 17 18:19:13 hostname kernel: 8021q: adding VLAN 0 to HW filter on device eth1
Jul 17 18:19:13 hostname kernel: bond0: Enslaving eth1 as a backup interface with an up link
Jul 17 18:19:13 hostname kernel: 8021q: adding VLAN 0 to HW filter on device bond0  
- - - - - - -8<- - - - - - -
Jul 17 18:19:22 hostname kernel: bond1: Setting MII monitoring interval to 100
Jul 17 18:19:22 hostname kernel: 8021q: adding VLAN 0 to HW filter on device bond1
Jul 17 18:19:22 hostname kernel: bond1: Setting MII monitoring interval to 100
Jul 17 18:19:22 hostname kernel: bond1: Adding slave eth2
Jul 17 18:19:23 hostname kernel: bnx2x 0000:20:00.0: eth2: using MSI-X  IRQs: sp 127  fp[0] 129 ... fp[7] 136
Jul 17 18:19:23 hostname kernel: 8021q: adding VLAN 0 to HW filter on device eth2
Jul 17 18:19:23 hostname kernel: bond1: Enslaving eth2 as a backup interface with a down link
Jul 17 18:19:23 hostname kernel: bond1: Adding slave eth3
Jul 17 18:19:23 hostname kernel: bnx2x 0000:20:00.0: eth2: NIC Link is Up, 10000 Mbps full duplex, Flow control: none
Jul 17 18:19:24 hostname kernel: bnx2x 0000:20:00.1: eth3: using MSI-X  IRQs: sp 137  fp[0] 139 ... fp[7] 146
Jul 17 18:19:24 hostname kernel: 8021q: adding VLAN 0 to HW filter on device eth3
Jul 17 18:19:24 hostname kernel: bnx2x 0000:21:00.1: eth3: NIC Link is Up, 10000 Mbps full duplex, Flow control: none
Jul 17 18:19:24 hostname kernel: bond1: Enslaving eth3 as a backup interface with a down link
Jul 17 18:19:24 hostname kernel: 8021q: adding VLAN 0 to HW filter on device bond1
Jul 17 18:19:24 hostname kernel: bond1: link status definitely up for interface eth2, 10000 Mbps full duplex
Jul 17 18:19:24 hostname kernel: bond1: making interface eth2 the new active one
Jul 17 18:19:24 hostname kernel: bond1: first active interface up!
Jul 17 18:19:24 hostname kernel: bond1: link status definitely up for interface eth3, 10000 Mbps full duplex    

Environment

  • Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content