<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Re: [CentOS] Bonding problem in CENTOS4</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>Try setting a manual MAC address on the bond interface that is different then any of the physical ones.<BR>
<BR>
-Ross<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: centos-bounces@centos.org <centos-bounces@centos.org><BR>
To: centos@centos.org <centos@centos.org><BR>
Sent: Mon Dec 17 07:44:21 2007<BR>
Subject: [CentOS] Bonding problem in CENTOS4<BR>
<BR>
I use bonding under CENTOS4.5 x32_62.<BR>
I have these weird messages when I'm restarting network.<BR>
Do you have any ideas how to fix this?<BR>
(there is similar bug for centos5 <A HREF="http://bugs.centos.org/view.php?id=2404">http://bugs.centos.org/view.php?id=2404</A>, but the author says that it worked for him in centos4...)<BR>
<BR>
Thanks<BR>
Vitaly<BR>
<BR>
Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in use by bond0. Set the HWaddr of eth0 to a different address to avoid conflicts.<BR>
Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth0<BR>
Dec 17 08:34:21 3_10 kernel: bonding: bond0: making interface eth1 the new active one.<BR>
Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth1<BR>
Dec 17 08:34:21 3_10 network: Shutting down interface bond0: succeeded<BR>
Dec 17 08:34:21 3_10 network: Shutting down interface eth2: succeeded<BR>
........<BR>
<BR>
Dec 17 08:35:16 3_10 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready<BR>
Dec 17 08:35:20 3_10 ifup: Enslaving eth0 to bond0<BR>
Dec 17 08:35:20 3_10 kernel: bnx2: eth0: using MSI<BR>
Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready<BR>
Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth0 as a backup interface with a down link.<BR>
Dec 17 08:35:20 3_10 ifup: Enslaving eth1 to bond0<BR>
Dec 17 08:35:20 3_10 kernel: bnx2: eth1: using MSI<BR>
Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready<BR>
Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth1 as a backup interface with a down link.<BR>
Dec 17 08:35:20 3_10 network: Bringing up interface bond0: succeeded<BR>
Dec 17 08:35:21 3_10 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready<BR>
Dec 17 08:35:23 3_10 kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex<BR>
Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth0.<BR>
Dec 17 08:35:23 3_10 kernel: bonding: bond0: making interface eth0 the new active one.<BR>
Dec 17 08:35:23 3_10 kernel: bonding: bond0: first active interface up!<BR>
Dec 17 08:35:23 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<BR>
Dec 17 08:35:23 3_10 kernel: bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex<BR>
Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for interface eth1.<BR>
Dec 17 08:35:23 3_10 kernel: tg3: eth2: Link is up at 1000 Mbps, full duplex.<BR>
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready<BR>
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready<BR>
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready<BR>
Dec 17 08:35:24 3_10 kernel: bond0: duplicate address detected!<BR>
Dec 17 08:35:25 3_10 network: Bringing up interface eth2: succeeded<BR>
<BR>
<BR>
_______________________________________________<BR>
CentOS mailing list<BR>
CentOS@centos.org<BR>
<A HREF="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</A><BR>
</FONT>
</P>
<P></P>
<HR WIDTH="100%">
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.
</BODY>
</HTML>