How to setup bond or team network cards in ubuntu 10.10/10.04

Sponsored Link
The Linux bonding driver provides a method for aggregating multiple network interfaces into a single logical
bonded interface.The behavior of the bonded interfaces depends upon the mode; generally speaking, modes provide either hot standby or load balancing services.

Additionally, link integrity monitoring may be performed.

You have to install ifenslave, it is a tool to attach and detach slave network interfaces to a bonding device.

sudo apt-get install ifenslave

Configuring your network interfaces and modules

You need to edit /etc/network/interfaces file and make it looks like

sudo nano /etc/network/interfaces

Add the following (This is just example enter you ip details)

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 10.0.0.254
netmask 255.255.255.0
gateway 10.0.0.1

iface eth1 inet manual

iface eth2 inet manual

auto bond0
iface bond0 inet static
bond_miimon  100
bond_mode balance-rr
address  10.0.0.3
netmask  255.255.255.0
gateway  10.0.0.1
up /sbin/ifenslave bond0 eth1 eth2
down /sbin/ifenslave -d bond0 eth1 eth2

Save and exit the file

Now you need to edit /etc/modprobe.d/aliases.conf file

sudo nano /etc/modprobe.d/aliases.conf

Add the following lines

alias bond0 bonding
options mode=0 miimon=100 downdelay=200 updelay=200

Save and exit the file

If you want more details about modes

mode=0 (balance-rr) Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.

mode=1 (active-backup) Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.

mode=2 (balance-xor) XOR policy: Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.

mode=3 (broadcast) Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.

mode=4 (802.3ad) IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.

* Pre-requisites:
* Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
* A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode.

mode=5 (balance-tlb) Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.

* Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.

mode=6 (balance-alb) Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.

Restart network services using the following command

sudo /etc/init.d/networking restart

Sponsored Link

Incoming search terms:

Related posts

9 thoughts on “How to setup bond or team network cards in ubuntu 10.10/10.04

  1. i cant get to the /etc/modprobe.d/aliases.conf file it just doesnt exist im using 10.10 adn ive completed the network config file and rebooted now no nics are showing

    my current /etc/network/interfaces file reads

    auto lo
    iface lo inet loopback

    iface eth0 inet manual
    iface eth1 inet manual

    auto bond0
    iface bond0 inet static
    bond_miimon 100
    bond_mode balance-xor
    address 10.0.0.3
    netmask 255.255.255.0
    gateway 10.0.0.1
    up /sbin/ifenslave bond0 eth0 eth1
    down /sbin/ifenslave -d bond0 eth0 eth1

    [Reply]

  2. This doesn’t work for 10.10 with two NICs (eth0 and eth1)

    where does this eth2 in your example come from? Third NIC???

    I did this exactly as it says and it no workie..

    ~# sudo /etc/init.d/networking restart
    * Reconfiguring network interfaces… SIOCDELRT: No such process
    Slave ‘eth2′: Error: get settings failed: No such device. Skipping
    Failed to bring up bond0.

    [Reply]

  3. THis is all that was needed in /etc/network/interfaces

    auto lo
    iface lo inet loopback

    auto bond0
    iface bond0 inet static
    address 192.168.1.121
    netmask 255.255.255.0
    #hwaddress ether 00:02:B3:48:50:2C
    gateway 192.168.1.1
    up ifenslave bond0 eth0 eth1
    down ifenslave -d bond0 eth0 eth1

    [Reply]

  4. The below worked for me in 10.10
    It failed when restarting networking until I add the lines under the comment #Failed…

    # The loopback network interface
    auto lo
    iface lo inet loopback

    #Failed until these two lines were added
    iface eth0 inet manual
    iface eth1 inet manual

    auto bond0
    iface bond0 inet static
    address 192.168.1.xxx
    netmask 255.255.255.0
    gateway 192.168.1.xxx
    up ifenslave bond0 eth0 eth1
    down ifenslave -d bond0 eth0 eth1

    To test I pulled out a patch cable and pinged the static address. The repeated for the second nic. All good.

    Regards

    Mark

    [Reply]

  5. Could anybody kindly let me know with a proper example that what is the gateway and IP to be mentioned in the iface bond0? are the two IPs virtual?

    [Reply]

  6. But you cant use networking restart any more, it even tells you when you use it that you shouldnt because it doesnt always bring all interfaces back up.

    If I do networking restart, bang, no connection cant SSH back in.

    [Reply]

  7. Your alieases.conf file content is incorrect, the second line must start with: options bonding …

    Here is the correct config:

    alias bond0 bonding
    options bonding mode=0 miimon=100 downdelay=200 updelay=200

    [Reply]

Leave a comment

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