Bonding issues

Issues related to configuring your network
Post Reply
TechBek
Posts: 1
Joined: 2014/02/17 12:15:52

Bonding issues

Post by TechBek » 2014/02/17 12:25:46

Hi all,

I have an HP DL380 G8 server with a 4 interface network card and I need to configure 2 bond interface:

bond0: eth0 + eth1
bond1: eth2 + eth3

This is my config (CentOS 5.10):

/etc/modprobe.conf

Code: Select all

alias eth0 tg3
alias eth1 tg3
alias eth2 tg3
alias eth3 tg3
alias scsi_hostadapter cciss
alias scsi_hostadapter1 ata_piix
alias bond0 bonding
alias bond1 bonding
/etc/sysconfig/network-scripts/ifcfg-eth0

Code: Select all

# Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
DEVICE=eth0
NM_CONTROLLED=no
ONBOOT=yes
HWADDR=2C:44:FD:84:12:04
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME="System eth0"
SLAVE=yes
MASTER=bond0
/etc/sysconfig/network-scripts/ifcfg-eth1

Code: Select all

# Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
DEVICE=eth1
HWADDR=2C:44:FD:84:12:05
NM_CONTROLLED=no
ONBOOT=yes
BOOTPROTO=none
SLAVE=yes
MASTER=bond0
/etc/sysconfig/network-scripts/ifcfg-bond0

Code: Select all

DEVICE=bond0
ONBOOT=yes
BOOTPROTO=static
NETWORK=172.22.0.0
NETMASK=255.255.0.0
IPADDR=172.22.23.6
GATEWAY=172.22.0.1
NAME=bond0
BONDING_OPTS="mode=1 miimon=100 primary=eth0"


/etc/sysconfig/network-scripts/ifcfg-eth2

Code: Select all

# Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
DEVICE=eth2
NM_CONTROLLED=no
ONBOOT=yes
HWADDR=2C:44:FD:84:12:06
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
NAME="System eth2"
SLAVE=yes
MASTER=bond1
/etc/sysconfig/network-scripts/ifcfg-eth3

Code: Select all

# Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe
DEVICE=eth3
HWADDR=2C:44:FD:84:12:07
NM_CONTROLLED=no
ONBOOT=yes
BOOTPROTO=none
SLAVE=yes
MASTER=bond1
/etc/sysconfig/network-scripts/ifcfg-bond1

Code: Select all

DEVICE=bond1
ONBOOT=yes
BOOTPROTO=static
NETWORK=172.22.0.0
NETMASK=255.255.0.0
IPADDR=172.22.23.7
GATEWAY=172.22.0.1
NAME=bond1
BONDING_OPTS="mode=1 miimon=100 primary=eth2"

The problem is that the bond0 reply to both IP (172.22.23.6 and 172.22.23.7), but if i disconnet all cable from bond0, I'm not able to reach the machine on bond1.

ifconfig

Code: Select all

bond0     Link encap:Ethernet  HWaddr 2C:44:FD:84:12:04  
          inet addr:172.22.23.6  Bcast:172.22.255.255  Mask:255.255.0.0
          inet6 addr: fe80::2e44:fdff:fe84:1204/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:27391 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4229 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3657938 (3.4 MiB)  TX bytes:546854 (534.0 KiB)

bond1     Link encap:Ethernet  HWaddr 2C:44:FD:84:12:06  
          inet addr:172.22.23.7  Bcast:172.22.255.255  Mask:255.255.0.0
          inet6 addr: fe80::2e44:fdff:fe84:1206/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:12962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1751640 (1.6 MiB)  TX bytes:2220 (2.1 KiB)

eth0      Link encap:Ethernet  HWaddr 2C:44:FD:84:12:04  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:15406 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4229 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1982155 (1.8 MiB)  TX bytes:546854 (534.0 KiB)
          Interrupt:178 Memory:faaf0000-fab00000 

eth1      Link encap:Ethernet  HWaddr 2C:44:FD:84:12:04  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:11985 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1675783 (1.5 MiB)  TX bytes:0 (0.0 b)
          Interrupt:186 Memory:faac0000-faad0000 

eth2      Link encap:Ethernet  HWaddr 2C:44:FD:84:12:06  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:12962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1751640 (1.6 MiB)  TX bytes:2220 (2.1 KiB)
          Interrupt:178 Memory:faa90000-faaa0000 

eth3      Link encap:Ethernet  HWaddr 2C:44:FD:84:12:06  
          UP BROADCAST SLAVE MULTICAST  MTU:1500  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:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:186 Memory:faa60000-faa70000 

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:1401 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1401 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2782562 (2.6 MiB)  TX bytes:2782562 (2.6 MiB)

Any ideas? :|
Thanks in advance

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Bonding issues

Post by TrevorH » 2014/02/17 12:33:12

Two problems: one you can't really have two interfaces on the same machine in the same subnet or strange things like this happen and 2) you have a GATEWAY= line in both ifcfg file so both will try to set the default route and only one will win. Depending on the order that the interfaces are (re)started that will end in one or other of them setting it to point to itself.

If you want to have two interfaces in the same subnet on the same machine then you will need to look into source based routing and set up /etc/iproute2/rt_tables and /etc/sysconfig/network-scripts/{route,rule}-$interface correctly. Getting this right can be a PITA.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Post Reply