bond0 up but individual eth device not up

[philipho827]

Hi,

I am facing some problems trying to bring up my bond0 interface. Configurations are as follows:
[root@pss1sitdb1a network-scripts]# more ifcfg-eth0
DEVICE=eth0
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
ONBOOT=yes
USERCTL=no
[root@pss1sitdb1a network-scripts]# more ifcfg-eth1
DEVICE=eth1
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no
ONBOOT=no
[root@pss1sitdb1a network-scripts]# more ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
IPADDR=10.106.247.5
NETMASK=255.255.255.248
ONBOOT=yes
USERCTL=no
BONDING_OPTS="mode=1"
[root@pss1sitdb1a network-scripts]#

In /etc/modprobe.conf
alias bond0 bonding
options bonding max_bonds=2

However, when i try to plump up bond0, eth0 and eth1 does not come up:
[root@pss1sitdb1a network-scripts]# ifconfig
bond0 Link encap:Ethernet HWaddr 00:17:08:50:79:F4
inet addr:10.106.247.5 Bcast:10.106.247.7 Mask:255.255.255.248
inet6 addr: fe80::217:8ff:fe50:79f4/64 Scope:Link
UP BROADCAST RUNNING MASTER 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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


[root@pss1sitdb1a network-scripts]# ethtool eth0 |grep Link
Link detected: no
[root@pss1sitdb1a network-scripts]# ethtool eth1 |grep Link
Link detected: no


Anyone able to advice on the reason why?

[Steven E. Protter]

Shalom,

Seems like a link problem

mii-tool eth0
mii-tool eth1

ethtool eth0
ethtool eth1

Lets see if we find a bad or mis-configured link.

SEP

[Ivan Ferreira]

In my systems, where everything is working correctly, the ONBOOT parameter is set to yes for the physical interfaces. Change the parameter for ifcfg-eth0 and ifcfg-eth1 to be:

ONBOOT=yes

[philipho827]

thanks for the replies.

I used the same set of configuration settings for another server, a c-class blade and it is able to bond.

The weird thing is i can do the bonding if i do the manual way:

/sbin/ifconfig bond0 10.106.247.5 netmask 255.255.255.248 up
/sbin/ifenslave bond0 eth0
/sbin/ifenslave bond0 eth1


I upgraded the kernel recently from 2.6.9-67 to 2.6.9-78 by running the following command:

rpm -U kernel-devel-2.6.9-78.0.8.EL.x86_64.rpm
and did a reboot, maybe i cannot upgrade the kernel this way?

[M. Rozin]

I am not sure that the kernel update is related to your problem but "rpm -U kernel-devel-2.6.9-78.0.8.EL.x86_64.rpm" didn't update your kernel. It updated only the kernel sources. In order to update the kernel binaries, you should update kernel-2.6.9-78.0.8.EL.x86_64.rpm.

My advise to you is never UPDATING the kernel, but INSTALLING additional newer version and adapting the boot loader files accordingly. This way you will always be able to boot with the old kernel in case your machine doesn't boot with the new one. Just use -i flag instead of -U.

Maxim Rozin.

[Vladimir Fabecic]

Do exactly what Ivan said.
I had some new installation and tested situation like yours. With "ONBOOT=no" interface does not come up.
Graphic configuration utility does not do the job well.