Bonding with RHES5 on DL585 G7

[Celeda]

Hi!

Bondig with RHES5 on DL585 G7 does not work smoothly.

After every reboot the network ist not available. Only if we issu service network restart or ifdown/up bond0, network connectivity is established.

Here's our config:

modprobe.conf

alias eth0 bnx2
alias eth1 bnx2
alias eth2 netxen_nic
alias eth3 netxen_nic
alias eth4 netxen_nic
alias eth5 netxen_nic
alias bond0 bonding

ifcfg-bond0

DEVICE=bond0
BOOTPROTO=none
USERCTL=no
ONBOOT=yes
IPADDR=xxx.xxx.xxx.x
NETMASK=255.255.255.0
BROADCAST=xxx.xxx.xxx.255
BONDING_OPTS="mode=1 miimon=100"


ifcfg-eth0 and ifcfg-eth2

DEVICE=eth0
BOOTPROTO=none
HWADDR=1C:C1:DE:07:98:EC
ONBOOT=yes
MASTER=bond0
SLAVE=yes

Thank you all for your help.

Wolfgang

[S.N.S]

Pl give the o/p from

less /proc/net/bonding/bond0


Thx
SNS

[Celeda]

Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 1c:c1:de:07:98:ec

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 78:e7:d1:58:56:fc


But this is after a network restart is done.

Wolfgang

[Alzhy]

Wolfy,

On my biond configuration - I have bonding options in /etc/modprobe.conf instead of ifcfg-bind0 sir:

alias bond0 bonding
options bond0 mode=active-backup miimon=100 primary=eth0

Also.. did you do mkinitrd rebuild of your initrd sir?

[Celeda]

Regarding to the instructions from RH for RHEL5, bonding options should be configured in ifcfg-bondX.

And why should we use mkinitrd? we use the kernel supplied driver from RH.

Any other suggestions?

Thanks

Wolfgang

[Alzhy]

The mkinitrd suggestion was one of our fixes one other box that was exhibiting the same issue as yours. Listen or Not -- it is a free world.


Is there anything in your startup logs if you are able to capture them sir? Maybe thre is a clue in /var/adm/messages sir?

Also:
What else do you have in /etc/sysconfig/networking-scripts? do an "ls -lt" maybe there is one or 2 misconfigured file in there.

You can also check:

root@arrog01# chkconfig --list network

and see if it is ON at RLs where it should start (2,3...)

And Lastly:
Suggest to fall back to non Bond config if the network subsystem starts on boot.