Linux Admin Reference – Network Bonding – Redhat Enterprise Linux ( RHEL5 / RHEL6)

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

Loading Facebook Comments ...

19 Responses

  1. Avatar Kennedy says:

    Lovely! Very easy to follow instructions and simple explanation. Good job – Keep it up.!

  2. Avatar Karthick says:

    mode-0 is Balance-rr or Active-backup? The start of the article mentioned mode-0 as Balance-rr and then throughout the article mode-0 referred as Active-backup configuration. Please clarify.

    • Ramdev says:

      Karthik – sorry for the confusion. the mode-0 is balance-rr.
      For both mode-0 and mode-1 , interfaces will be configured as slaves.
      The only difference is, in mode-0 all the interfaces in use in round robin mode to provide load balancing and Fault tolerance. Where a in mode-1 there is one active slave at a time, and only provide the fault tolerance.

  3. Avatar vaibhav kanchan says:

    HI Ramdev,

    I have done the below steps.

    [root@cent62 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0
    DEVICE=bond0
    IPADDR=192.168.1.124
    NETMASK=255.255.255.0
    NETWORK=192.168.1.0
    USERCTL=no
    BOOTPROTO=none
    ONBOOT=yes
    [root@cent62 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
    DEVICE=eth0
    BOOTPROTO=none
    ONBOOT=yes
    MASTER=bond0
    SLAVE=yes
    USERCTL=no
    [root@cent62 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
    DEVICE=eth1
    BOOTPROTO=none
    ONBOOT=yes
    MASTER=bond0
    SLAVE=yes
    USERCTL=no
    [root@cent62 ~]# cat /etc/modprobe.d/bonding.conf
    alias bond0 bonding
    options bond0 mode=1 miimon=100
    [root@cent62 ~]# 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): 100
    Up Delay (ms): 0
    Down Delay (ms): 0

    Slave Interface: eth0
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 0
    Permanent HW addr: 08:00:27:88:80:0e
    Slave queue ID: 0

    Slave Interface: eth1
    MII Status: up
    Speed: 1000 Mbps
    Duplex: full
    Link Failure Count: 1
    Permanent HW addr: 08:00:27:c7:e1:e1
    Slave queue ID: 0

    but ifconfig -a is showing the below status.

    bond0 Link encap:Ethernet HWaddr 08:00:27:88:80:0E
    inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe88:800e/64 Scope:Link
    UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
    RX packets:515 errors:0 dropped:0 overruns:0 frame:0
    TX packets:390 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:45200 (44.1 KiB) TX bytes:54529 (53.2 KiB)

    eth0 Link encap:Ethernet HWaddr 08:00:27:88:80:0E
    inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
    RX packets:515 errors:0 dropped:0 overruns:0 frame:0
    TX packets:379 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:45200 (44.1 KiB) TX bytes:52055 (50.8 KiB)

    eth1 Link encap:Ethernet HWaddr 08:00:27:C7:E1:E1
    inet addr:192.168.1.124 Bcast:192.168.1.255 Mask:255.255.255.0
    UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:2474 (2.4 KiB)

    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:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

  4. Avatar vaibhav kanchan says:

    what is the issue in my case?

  5. Ramdev says:

    @vaibhav, I didn’t get your question completely, can you explain what is the issue you are talking?

  6. Avatar cuturrr says:

    options bond0 mode=1 miimon=100 should be options bonding mode=1 miimon=100 and i don’t knwo why you specified paramaters in both places 1:BONDING_OPTS && /etc/modprobe.d/bonding.conf

  7. Avatar rony says:

    Hi,
     I have Redhat 5.9 running on the hp blade server. I already have bond0 configure with mode=0 with eth0 and eth1 interface and its running fine. Now , my team wants to change mode=0 to mode =1 for this bonding bond0. What are the steps to change the bonding mode=0 to mode=1, while the bond0 is running

     Waiting for your reply as this is really urgent. Thanks

    thanks,
    Rony

  8. Avatar Javeed says:

    Nice explanation!!! keep it up

  9. Avatar Mahesh Vijapure says:

    [root@cent62 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
    DEVICE=eth0

    Please modify the device name in your example.. I know it must be typo. FYI.

    Thanks,
    Mahesh

  10. Avatar Mahesh Vijapure says:

    Cool.. Welcome.. You doing great Job Sir.. :)

  11. Avatar anon says:

    # cat > /etc/modprobe.d/bonding.conf

    alia bond0 bonding

    typo – ‘alia’ should be changed to ‘alias

  12. Avatar Manisha says:

    Hello Ramdev/team,
    I don’t see few updates in the sample box in the description. It shows blank. I found it in other topics as well.

    Cheers,
    Manisha

    • Avatar Manisha says:

      Please ignore the above message. I could highlight the boxes and see the content. Sorry for spamming the comment box.

What is in your mind, about this post ? Leave a Reply

Follow

Get every new post delivered to your Inbox

Join other followers