NIC Bonding

jeewiz · 10-14-2011, 10:08 AM

I'm having some issue with first setting up NIC bonding, I've had to create additional configs to make it function. Once it does work initially, it doesn't work well or reliably. I get delay from ssh, never losing connection but the delay grows to minutes long and needs to be reset to function at all.

I'm running with 6 NICs, 4 active, those 4 are broken into 2 bonds (bond0 and bond1). Here's a sample config for a NIC:

(All in /etc/sysconfig/network-scripts/)
ifcfg-eth0:

Code:

DEVICE=eth0
HWADDR=00:00:00:...
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

ifcfg-bond0:

Code:

DEVICE=bond0
IPADDR=192.168.0.1
NETWORK=192.168.0.0
NETMASK=255.255.254.0
GATEWAY=192.168.1.250
USERCTL=no
BOOTPROTO=none
ONBOOT=yes

route-bond0: (aa=short name of network)

Code:

192.168.0.0/23 dev bond0 src 192.168.0.1 table aa
default via 192.168.1.250 dev bond0 table aa

rule-bond0:

Code:

from 192.168.0.1/23 table aa

/etc/modprobe.conf: (appended lines)

Code:

alias bond0 bonding
options bond0 mode=balance-alb miimon=100

The config follows the same convention for 4 NICs, and 2 bonds. Without the route-bond# and rule-bond# files, they come up, but they can't ping anything or be pinged.

Like I said, with the above config, they function but very poorly with growing delays. My ssh terminal only stays good for about 3 minutes before it needs to be re-opened.

Thanks!

jeewiz · 10-14-2011, 02:21 PM

Experiencing a new issue with the above config....

I can reach the server from anywhere, but the server itself is not routing to other networks. It can ping the network routers, but cannot reach through them to the other networks.

Executing a "netstat -arp" shows no gateway set. I need both to point to their network gateway.

travisdh1 · 10-14-2011, 03:21 PM

Do they both use the same gateway? If so specifying the default gateway twice in the config files for the bonds could muck things up. (At least it did when I did the same thing without the bonds.)

Also might want to take a look at the routing table (I've gotten to be outmoded these days still using the route command. They use something else nowadays but it still works for looking at things.)