Unsolved
This post is more than 5 years old
4 Posts
0
15751
March 25th, 2010 06:00
Problems Creating a bonded interface with Redhat ES 5.3 on R710
I am building out an R710 with Redhat Linux ES 5.3but I’m having issues with the bonded interface. The machine has all sorts of trouble once I create the bonded interface. It gets into some sort of "Call Trace" mode (dump) and just locks up the box. I’ve tried a few different settings, but all seem to cause the problem.
This is what I have for the interface settings.:
Ifcfg-bond0:
DEVICE=bond0
IPADDR=192.168.XXX.XXX
NETMASK=255.255.192.0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
Ifcfg-eth0:
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
Ifcfg-eth1:
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
I added the bonding parameters in the /etc/modprobe.conf file.
modprobe.conf:
alias eth0 bnx2
alias eth1 bnx2
alias eth2 bnx2
alias eth3 bnx2
alias scsi_hostadapter megaraid_sas
alias scsi_hostadapter1 ata_piix
alias bond0 bonding
options bond0 mode=6 miimon=100
I also tried putting the bonding options in the ifcfg-bond0 file.
DEVICE=bond0
IPADDR=192.168.XXX.XXX
NETMASK=255.255.192.0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
BONDING_OPT="mode=1 miimon=100 primary=eth0"
I then ran ‘modprobe bonding’ and restarted the network service. Everything seemed OK. But after a reboot, there are all sorts of problems. Any ideas/suggestions? Do I need to add ‘modprobe bonding’ to the rc.local file?
,
# ethtool eth0
Settings for eth0:
Link detected: yes
If I run ethtool on any of the other 3 ports I get full stats:
# ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Link detected: yes
So, I changed the bonded pair to eth1 and eth2, and it seems a little better. The odd thing now is that both interfaces show the same HWaddr, even though the HWaddr is set in the ifcfg-eth1/2 files.
bond0 Link encap:Ethernet HWaddr A4:BA:DB:1A:CD:86
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XX.XXX Mask:255.255.192.0
inet6 addr: fe80::a6ba:dbff:fe1a:cd86/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:6788 errors:0 dropped:0 overruns:0 frame:0
TX packets:459 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:554635 (541.6 KiB) TX bytes:55072 (53.7 KiB)
eth0 Link encap:Ethernet HWaddr A4:BA:DB:1A:CD:84
inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.255.224
inet6 addr: fe80::a6ba:dbff:fe1a:cd84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:9204 (8.9 KiB)
eth1 Link encap:Ethernet HWaddr A4:BA:DB:1A:CD:86
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3395 errors:0 dropped:0 overruns:0 frame:0
TX packets:229 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:277027 (270.5 KiB) TX bytes:27629 (26.9 KiB)
Interrupt:25 Memory:d8000000-d8012100
eth2 Link encap:Ethernet HWaddr A4:BA:DB:1A:CD:86
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3393 errors:0 dropped:0 overruns:0 frame:0
TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:277608 (271.1 KiB) TX bytes:27443 (26.7 KiB)
Interrupt:26 Memory:da000000-da012100
I am beginning to think that this ES5.3 Kernel doesn’t support, or is at least missing some pieces, for interface bonding.
Dev Mgr
6 Operator
•
9.3K Posts
0
March 25th, 2010 07:00
Dell has a driver under their downloads for the Broadcom NICs. Are you using the kernel native driver, or the one from the Dell site? If you're on the kernel native driver, you may want to try the downloadable one. It's listed under RHEL 5.2, but I'd compare the driver versions and consider trying the Dell driver if it's newer.