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

Best Affordable Linux and WordPress Services For Your Business
Outsource Your Linux and WordPress Project and Get it Promptly Completed Remotely and Delivered Online.

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Gabriel Cánepa

Gabriel Cánepa is a GNU/Linux sysadmin and web developer from Villa Mercedes, San Luis, Argentina. He works for a worldwide leading consumer product company and takes great pleasure in using FOSS tools to increase productivity in all areas of his daily work.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

8 Responses

  1. David says:

    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?

  2. Sunil says:

    Thank you for this guide.

  3. Lotfi Lakhal says:

    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.

  4. Jason says:

    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

  5. Kaustubh Ghanekar says:

    How can we do the same non-interactively (add within script)? Is there a nmcli or something?

Leave a Reply to Ravi Saive Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.