[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] Regd: Ethernet Channel Bonding issue in Cluster



>> I have configured Ethernet Channel Bonding in Each Cluster Nodes and
>> Channel Bonding Configuration Details are

This is not a cluster issue, it's an OS issue.

This works on both my RHEL and CentOS machines, both 4 and 5. Take a close 
look at your configuration, perhaps you have an error in one of your files. 
That's about the only problems I've had. Here are my own notes which you can 
use to follow along.

Mike

Test Links;
ethtool <interface-name> | grep "Link detected:" This is used to check eth0 
Interfaces for example, not bond0 interfaces.
 
Check the bond0 interface;
# cat /proc/net/bonding/bond0
 
List all Interfaces;
ip -a
List Routes;
ip r
 
In CentOS5;
 
In the /etc/modprobe.conf file add the following:
alias bond0 bonding
options bond0 miimon=80 mode=5
 
In the /etc/sysconfig/network-scripts/ directory create ifcfg-bond0:
DEVICE=bond0
IPADDR=x.x.x.x
NETMASK=x.x.x.x
NETWORK=x.x.x.x
BROADCAST=x.x.x.255
GATEWAY=x.x.x.x
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
 
Change the ifcfg-eth0 to:
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
 
Change the ifcfg-eth1 to:
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
MASTER=bond0
SLAVE=yes
 
Change additional interfaces, ifcfg-ethx, etc.
 
Restart network services;
---
Diverse modes of bonding:
 
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.
 
* Prerequisites:
o Ethtool support in the base drivers for retrieving the speed and duplex of 
each slave.
o 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.
Also you can use multiple bond interface but for that you must load the 
bonding module as many as you need.
 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]