Sorry for the top posting (Outlook, need to configure still)

I would highly recommend you place the real HWADDRs in there, for each
device. The actual ones should be in /etc/sysconfig/hwconf (I think the
ones in /sys/class/net are the ones ifconfig will report)

The bond will usually grab the MAC from the first active device and use
that from there on out, but, in your case if they somehow manage to be
the same for both devices all sorts of chaos can ensure. Having them in
there almost makes sure no reordering occurs and prevents kudzu from
ever touching them if it thinks it has found a "new" device.


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Nick Lunt
Sent: Friday, January 29, 2010 8:38 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: Re: [rhelv5-list] Suspect bonding errors

> -----Original Message-----
> From: [email protected] [mailto:rhelv5-list-
> [email protected]] On Behalf Of Kinzel, David
> Sent: 29 January 2010 15:19
> To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
> Subject: Re: [rhelv5-list] Suspect bonding errors
> 
> Nick,
> 
> Do each of your ifcfg-eth* files contain the real HWADDR for your
> ethernet devices? I've seen a lot of setups (every place I have walked
> into) where they are either duplicated from other ifcfg-eth files or
> bashed together in a non-consistent way that casuses grief when it
> comes
> to the bond picking which MAC address to use, etc (it's actually
> possible to tell the bond to use a totally different one, but I'm not
> sure what the recommended practice is -- I've always just ensured the
> real HW addrs are in there). The logs seem to imply that this is one
of
> the conflict you are running into.
> 
> Sounds simple, but I've seen a lot of things blow up because of it.

Hi David,

no the ifcfg- files do not have the HW address in them.

The bond used eth2 and eth3 -

# cat ifcfg-eth2
DEVICE=eth2
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none
TYPE=Ethernet

# cat ifcfg-eth3
DEVICE=eth3
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none
TYPE=Ethernet

Now that the bond is up and running, ifconfig on each eth shows the MAC
address to be the MAC address of the bond:

# ifconfig eth2|grep HWaddr
eth2      Link encap:Ethernet  HWaddr 00:1E:C9:CD:D9:4C

# ifconfig eth3|grep HWaddr
eth3      Link encap:Ethernet  HWaddr 00:1E:C9:CD:D9:4C

# ifconfig bond1 | grep HWaddr
bond1     Link encap:Ethernet  HWaddr 00:1E:C9:CD:D9:4C

So you suggest getting the real HWaddr for each device and put that in
the relevant ifcfg- files ?

Thanks
Nick

 

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4818 (20100129) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

This email communication and any files transmitted with it may contain 
confidential and or proprietary information and is provided for the use of the 
intended recipient only.  Any review, retransmission or dissemination of this 
information by anyone other than the intended recipient is prohibited.  If you 
receive this email in error, please contact the sender and delete this 
communication and any copies immediately.  Thank you.
http://www.encana.com



_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to