Bonding configuration

Jan Hugo Prins jhp at jhprins.org
Mon Jan 29 15:38:29 UTC 2007


Hello,

I'm currently trying to get some bonding configurations working with 
servers that have 2 Intel 1Gb adapters.
The config files I created are as follows:

ifcfg-bond0:
DEVICE=bond0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Bonding
PERSISTENT_DHCLIENT=yes

ifcfg-eth0:
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

ifcfg-eth1:
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

During initialization the network-functions script runs a  check_ethtool 
and a check_mii_tool to see if the interfaces are up and running before 
it starts DHCP.
In these functions mii-tool returns a status 0, which means "interface 
down" and ethtool returns a status 2 which means "no information available".
The script says that if both return 2, then you should just start 
dhclient because we really don't know if it is going to work.
If either one returns 1, which means "interface up", then you can asume 
that the other tool failed and everything is ok. So you can start dhclient.
But I run into the situation where one tools fails and returns a down 
status and the other one doesn't know. Resulting in not starting the 
dhcp client.

I am now wandering, did I misconfigure something should mii-tool or 
ethtool return a corect value. Or did I run into a bug??

Jan Hugo Prins




More information about the fedora-list mailing list