Hello all,
I am running fedora 12 and have two bonded interfaces. Everything works fine if I manually start my bonded interface (bond0). It also works fine if I put (ifup bond0) in /etc/rc.d/rc.local. However, it refuses to start on boot otherwise and rc.local is kinda late in the boot sequence. Things that require the network to be running become very unhappy.
NM is not running so that can not be interfering. I have three systems all using Intel NICs but otherwise different hardware. They are all having this issue. What am I missing (ID 10 T error probably)? As always, any help would be appreciated.
Here is some system information:
# chkconfig|grep Network NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
# uname -a Linux test 2.6.32.19-163.fc12.x86_64 #1 SMP Wed Aug 18 11:38:54 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/modprobe.conf alias bond0 bonding options bond0 miimon=100 mode=4
# cat ifcfg-bond0 DEVICE=bond0 IPADDR=10.64.236.67 NETMASK=255.255.255.0 NETWORK=10.64.236.0 BROADCAST=10.64.236.255 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS="miimon=100 mode=4" NM_CONTROLLED=no GATEWAY=10.64.236.1 TYPE=Ethernet IPV6INIT=no NAME="system bond0" IPV4_FAILURE_FATAL=yes
# cat ifcfg-eth0 # Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) DEVICE=eth0 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none HWADDR=00:14:4F:78:4D:64 TYPE=Ethernet NM_CONTROLLED=no IPV6INIT=no NAME="system eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
# cat ifcfg-eth1 # Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) DEVICE=eth1 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none HWADDR=00:14:4F:78:4D:65 NM_CONTROLLED=no TYPE=Ethernet IPV6INIT=no NAME="system eth1"
# ifconfig
bond0 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64
inet addr:10.64.236.67 Bcast:10.64.236.255 Mask:255.255.255.0
inet6 addr: fe80::214:4fff:fe78:4d64/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:1097 errors:0 dropped:0 overruns:0 frame:0
TX packets:658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 RX bytes:141477 (138.1 KiB) TX bytes:137257 (134.0 KiB)
eth0 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:582 errors:0 dropped:0 overruns:0 frame:0
TX packets:271 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:77525 (75.7 KiB) TX bytes:56514 (55.1 KiB)
eth1 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:516 errors:0 dropped:0 overruns:0 frame:0
TX packets:388 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:64012 (62.5 KiB) TX bytes:80977 (79.0 KiB)
--- Will Y.
Hi again,
I thought I would add this tidbit:
/etc/init.d/network stop and then /etc/init.d/network start brings the bond0 interface down and up as expected. Could there be an issue with when the aliases are available from /etc/modprobe.conf? There is nothing in dmesg or /var/log/messages that show the system even trying to start this interface on boot. However, when done manually:
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008) bonding: MII link monitoring set to 100 ms bonding: bond0: Setting MII monitoring interval to 100. bonding: bond0: setting mode to 802.3ad (4). ADDRCONF(NETDEV_UP): bond0: link is not ready bonding: bond0: Adding slave eth0. e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX bonding: bond0: enslaving eth0 as a backup interface with an up link. bonding: bond0: Adding slave eth1. e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX bonding: bond0: enslaving eth1 as a backup interface with an up link. ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready bond0: no IPv6 routers present
As always, any help would be appreciated.
--- Will Y.
Hi,
/etc/init.d/network stop and then /etc/init.d/network start brings the bond0 interface down and up as expected. Could there be an issue with when the aliases are available from /etc/modprobe.conf? There is nothing in dmesg or /var/log/messages that show the system even trying to start this interface on boot.
/sbin/chkconfig network on
Regards, Fernando.
/etc/init.d/network stop and then /etc/init.d/network start
brings the
bond0 interface down and up as expected.
Could there be an issue
with when the aliases are available
from /etc/modprobe.conf? There
is nothing in dmesg or
/var/log/messages that show the system even
trying to start this interface on boot.
/sbin/chkconfig network on
Hello,
Thank you for responding. I should have been more specific. Other network interfaces start normally. Just not the bonded one. The network is set to start at run level 5 like expected:
# chkconfig|grep network network 0:off 1:off 2:off 3:off 4:off 5:on 6:off
--- Will Y.
On 09/01/2010 04:39 PM, aragonx@dcsnow.com wrote:
Hello all,
I am running fedora 12 and have two bonded interfaces. Everything works fine if I manually start my bonded interface (bond0). It also works fine if I put (ifup bond0) in /etc/rc.d/rc.local. However, it refuses to start on boot otherwise and rc.local is kinda late in the boot sequence. Things that require the network to be running become very unhappy.
NM is not running so that can not be interfering. I have three systems all using Intel NICs but otherwise different hardware. They are all having this issue. What am I missing (ID 10 T error probably)? As always, any help would be appreciated.
Here is some system information:
# chkconfig|grep Network NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
# uname -a Linux test 2.6.32.19-163.fc12.x86_64 #1 SMP Wed Aug 18 11:38:54 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/modprobe.conf alias bond0 bonding options bond0 miimon=100 mode=4
# cat ifcfg-bond0 DEVICE=bond0 IPADDR=10.64.236.67 NETMASK=255.255.255.0 NETWORK=10.64.236.0 BROADCAST=10.64.236.255 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_OPTS="miimon=100 mode=4" NM_CONTROLLED=no GATEWAY=10.64.236.1 TYPE=Ethernet IPV6INIT=no NAME="system bond0" IPV4_FAILURE_FATAL=yes
# cat ifcfg-eth0 # Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) DEVICE=eth0 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none HWADDR=00:14:4F:78:4D:64 TYPE=Ethernet NM_CONTROLLED=no IPV6INIT=no NAME="system eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
# cat ifcfg-eth1 # Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) DEVICE=eth1 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none HWADDR=00:14:4F:78:4D:65 NM_CONTROLLED=no TYPE=Ethernet IPV6INIT=no NAME="system eth1"
# ifconfig bond0 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64 inet addr:10.64.236.67 Bcast:10.64.236.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe78:4d64/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:1097 errors:0 dropped:0 overruns:0 frame:0 TX packets:658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:141477 (138.1 KiB) TX bytes:137257 (134.0 KiB)
eth0 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:582 errors:0 dropped:0 overruns:0 frame:0 TX packets:271 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:77525 (75.7 KiB) TX bytes:56514 (55.1 KiB)
eth1 Link encap:Ethernet HWaddr 00:14:4F:78:4D:64 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:516 errors:0 dropped:0 overruns:0 frame:0 TX packets:388 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:64012 (62.5 KiB) TX bytes:80977 (79.0 KiB)
Will Y.
This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean.
Here is sample from a system here. Looks very close to yours. We have never had a problem with them coming up ...
[root@kvm1 network-scripts]# cat *bond0 DEVICE=bond0 IPADDR=172.20.17.1 NETMASK=255.255.240.0 MTU=9000 ONBOOT=yes BOOTPROTO=none USERCTL=no BONDING_MASTER="yes" BONDING_MODULE_OPTS="mode=802.3ad miimon=100" BONDING_SLAVE0="eth2" BONDING_SLAVE1="eth3"
[root@kvm1 network-scripts]# cat *eth2 DEVICE=eth2 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none MTU=9000
[root@kvm1 network-scripts]# cat *eth3 DEVICE=eth3 USERCTL=no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none MTU=9000
-
Fernando Gozalo -
Phil Meyer -
Will Yonker