bonding wierd issue
 

Hello networkers

I configured bonding in a Red Hat (5.5) HP server with 4 NICs ,I did everything fine :
1- /etc/modprobe.conf
:alias bond0 bonding
options bond0 mode=4 miimon=100

2- configured /etc/sysconfig/network-scripts/
:ifcfg-bond0
ifcfg-eth0 (SLAVE=yes , MASTER=bond0)
ifcfg-eth1 (SLAVE=yes , MASTER=bond0)
ifcfg-eth2 (SLAVE=yes , MASTER=bond0)
ifcfg-eth4 (SALVE=yes , MASTER=bond0)

the weird thing is : when I restart the server , at boot it shows that Bringing up interface bond0 is ..... [ok] , but after I login i find out that the server is not connected to the LAN at all (it can not ping any local machine nor other machine in the LAN can ping the server) , but after I restart the network service:
service network restart or
ifdown bond0
ifup bond0

the bond0 is working fine with no errors at all .

why cant bond0 just boot up normally like real interface and got connected immediate ?? why it needs restarting the network service ir put down and then up bond0 .


Please help , your help is highly highly appreciated .



Regards
Mosawer

Did the ifcfg-bond0 and file for each nic (ifcfg-ethx) contains the below listed line?

Dear

Yes , they have this line .

Regards
Mosawer

Then please show the contents of the files

Sorry for delay , here is the contents of the files :

ifcfg-bond0:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
DEVICE=bond0
BOOTPROTO=static
ONBOOT=yes
USERCTL=no
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NETWORK=192.168.1.0
----------------------------
ifcfg-eth0:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
DEVICE=eth0
BOOTPROTO=none
ONBOOT=ye
MASTER=bond0
SLAVE=yes
USERCTL=no
-----------------------------
ifcfg-eth1:
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
----------------------------
ifcfg-eth2:
# NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter
DEVICE=eth2
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
ONBOOT=yes
USERCTL=no
--------------------------
ifcfg-eth3:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
DEVICE=eth3
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
=============================
/etc/modprobe.conf:
alias eth0 netxen_nic
alias eth1 netxen_nic
alias eth2 netxen_nic
alias eth3 netxen_nic
alias scsi_hostadapter cciss
alias scsi_hostadapter1 ata_piix
alias bond0 bonding
options bond0 mode=4 miimon=100
###BEGINPP
include /etc/modprobe.conf.pp
###ENDPP
==============================

I hope that helps solve my problem ..

Regards
Mosawer

I think the issue is same, that i have told you to check in my first post.
ye != yes

So replace ye with yes and try :)

Chief

I dont think this is the cause because I tried many time , before the configuration I sent above I tried like this :
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
==============
#TYPE=Ethernet
DEVICE=eth0
BOOTPROTO=none
ONBOOT=no
STARTMODE=off
MASTER=bond0
SLAVE=yes
USERCTL=no
#IPV6INIT=no
#PEERDNS=yes
HWADDR=b4:b5:2f:5d:61:34
=====================
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
#TYPE=Ethernet
DEVICE=bond0
BOOTPROTO=static
ONBOOT=yes
STARTMODE=on
USERCTL=no
#IPV6INIT=no
#PEERDNS=yes
#HWADDR=b4:b5:2f:5d:61:34
IPADDR=159.159.9.2
NETMASK=255.255.255.0
NETWORK=159.159.9.0
==========================
I think this is the 20th time im restarting the server , eatch time i remove the ifcfg* files and create new ones ,. If this time I missed to type "yes" correctly I dont think I did the same mistake the 19th times earlier ...
I think it is something related to bonding of module ?? or May be the network service starting before the NIC kernel module was loaded ?

Please advise ...


Regards
Mosawer

As far as I know, it seems bonding module is working fine. The only thing is some how NIC card/networking is not up automatically after boot. So to fix that one thing is ONBOOT=yes. Even in this file content
ONBOOT=no

As far as my understanding, if NIC is not up after boot, bonding wont work. But when you start manually it works fine. So it seems bonding module is not an issue. It seems NIC card. You can also try to look into the output of dmesg or /var/log/syslog or /var/log/messages may be some error message about NIC/Bonding. It seems silly but check one more thing

The /etc/sysconfig/network file should contain the following line:
Hope it helps

All

I had to use this workaround since i had tested all the suggestions you gave me but problem still existed :

I created a script file named S10renetwork in /etc/rc.d/rc5.d & /etc/rc.d/rc3.d as the following :
----------------------------
#!/bin/bash
/sbin/service network restart
sleep 15
----------------------------
problem solved ...


Thanks all for you suggestions and cooperation
Mosawer