Comments on: How to Setup and Configure Network Bonding or Teaming in RHEL/CentOS 7 – Part 11

By: Ravi Saive

Ravi Saive — Fri, 08 Mar 2019 04:51:10 +0000

In reply to David.

@David,

You can use nmtui or nmcli tool to create network bonding..

By: David

David — Thu, 07 Mar 2019 16:05:55 +0000

I got some good info form this article. But I do have one question. After figure 1 you state, "To create bond0, we can either use nmtui". Either implies there is another option. I'm looking for another way to configure bonding w/o using nmtui or nmcli. Did you have another option you were going to mention?

By: Sunil

Sunil — Sun, 03 Jun 2018 13:37:24 +0000

Thank you for this guide.

By: Lotfi Lakhal

Lotfi Lakhal — Fri, 17 Mar 2017 04:47:59 +0000

Hello. I noticed a serious problem that needs your attention: How to configure automatic recovery of a failed port in RHEL7.0 teaming ? I successfully configured teaming (active backup) by following a similar procedure, in a RHEL 7.0 server.

The failover from port1 to port2 (from main to backup) was also successful by just applying the proper command, but when I tried to failover again from port2 to port1 (from backup to main), it was not possible.

I found port1 still in a failed state (down) and I had to recover it up manually. This is a big problem because if the backup (port2) also fails, the network will remain in a failed state and never recovers.

So is there a solution to this problem: a command to (try to) immediately recover (stimulate) a failed port after a failover, so that it becomes soon ready to switch back to main (active) again if/when necessary. This means the config must always try keeping both ports UP so that failover never fails. Thanks.

By: Jason

Jason — Wed, 28 Sep 2016 13:07:45 +0000

Great article. However, when a server reboots, the bond0 link doesn't come up because there's a bug in centos7 that doesn't start up the bond0 interface automatically. To resolve my issue, I added this command below which stated above to the "/etc/rc.d/rc.local" and then run "chmod +x /etc/rc.d/rc.local" to ensure that this script will be executed during boot. Reason being that /etc/rc.local or /etc/rc.d/rc.local are no longer executed by default due to systemd-changes. To still use those, you need to make /etc/rc.d/rc.local executable. So again, 1. Open this file /etc/rc.d/rc.local 2. Add "ip link set dev bond0 up" to it (bond0 is your bonding interface or whatever it was named as). 3. Save and run "chmod +x /etc/rc.d/rc.local"