Try setting a manual MAC address on the bond interface that is different then
any of the physical ones.
-Ross
-----Original Message-----
From: centos-bounces at centos.org <centos-bounces at centos.org>
To: centos at centos.org <centos at centos.org>
Sent: Mon Dec 17 07:44:21 2007
Subject: [CentOS] Bonding problem in CENTOS4
I use bonding under CENTOS4.5 x32_62.
I have these weird messages when I'm restarting network.
Do you have any ideas how to fix this?
(there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but
the author says that it worked for him in centos4...)
Thanks
Vitaly
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.
Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth0
Dec 17 08:34:21 3_10 kernel: bonding: bond0: making interface eth1 the new
active one.
Dec 17 08:34:21 3_10 kernel: bonding: bond0: releasing active interface eth1
Dec 17 08:34:21 3_10 network: Shutting down interface bond0: succeeded
Dec 17 08:34:21 3_10 network: Shutting down interface eth2: succeeded
........
Dec 17 08:35:16 3_10 kernel: ADDRCONF(NETDEV_UP): bond0: link is not ready
Dec 17 08:35:20 3_10 ifup: Enslaving eth0 to bond0
Dec 17 08:35:20 3_10 kernel: bnx2: eth0: using MSI
Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth0 as a backup
interface with a down link.
Dec 17 08:35:20 3_10 ifup: Enslaving eth1 to bond0
Dec 17 08:35:20 3_10 kernel: bnx2: eth1: using MSI
Dec 17 08:35:20 3_10 kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
Dec 17 08:35:20 3_10 kernel: bonding: bond0: enslaving eth1 as a backup
interface with a down link.
Dec 17 08:35:20 3_10 network: Bringing up interface bond0: succeeded
Dec 17 08:35:21 3_10 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
Dec 17 08:35:23 3_10 kernel: bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex
Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for
interface eth0.
Dec 17 08:35:23 3_10 kernel: bonding: bond0: making interface eth0 the new
active one.
Dec 17 08:35:23 3_10 kernel: bonding: bond0: first active interface up!
Dec 17 08:35:23 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 17 08:35:23 3_10 kernel: bnx2: eth1 NIC Link is Up, 1000 Mbps full duplex
Dec 17 08:35:23 3_10 kernel: bonding: bond0: link status definitely up for
interface eth1.
Dec 17 08:35:23 3_10 kernel: tg3: eth2: Link is up at 1000 Mbps, full duplex.
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Dec 17 08:35:24 3_10 kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Dec 17 08:35:24 3_10 kernel: bond0: duplicate address detected!
Dec 17 08:35:25 3_10 network: Bringing up interface eth2: succeeded
_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos
______________________________________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20071217/0ae7eaba/attachment-0002.html>