[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [rhelv5-list] Bonding Configuration Question
- From: Domenico Viggiani <dviggiani tiscali it>
- To: "'Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list'" <rhelv5-list redhat com>
- Subject: Re: [rhelv5-list] Bonding Configuration Question
- Date: Wed, 1 Jun 2011 17:11:11 +0200
>From: Trutwin, Joshua
>
>Ive seen this warning a few times in dmesg:
>
>bonding: bond0: Warning: the permanent HWaddr of eth0 - 00:17:AA:BB:CC:14 -
is still in >use by bond0. Set the HWaddr of eth0 to a different address to
avoid conflicts.
>
>Checked the kbase and found this article:
https://access.redhat.com/kb/docs/DOC-37419
>that says you can specify a hardware address in the ifcfg-bond0 file. Can
this address
>be arbitrary? I put in MACADDR=11:22:33:44:55 and it seemed to work. Is
it a problem if
>two servers use the same MAC address for their bonding interface?
I was unable to understand the real nature of this message.
Instead of putting arbitrary and possibly problematic MAC addresses, I
suggest to ignore this warning, bonding works perfectly.
I have these conf files:
-> ifcfg-eth0
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:1C:C4:E2:44:32
NOZEROCONF=1
ONBOOT=yes
IPV6INIT=no
MASTER=bond0
SLAVE=yes
USERCTL=no
-> ifcfg-eth1
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth1
HWADDR=00:1C:C4:E2:44:30
ONBOOT=no
BOOTPROTO=none
NOZEROCONF=yes
IPV6INIT=no
MASTER=bond0
SLAVE=yes
USERCTL=no
-> ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
IPADDR=10.61.1.200
NETMASK=255.255.255.0
GATEWAY=10.61.1.254
NOZEROCONF=1
USERCTL=no
--
DV
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]