RE: NIC Teaming

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2008-03-31 at 15:38 +0100, Gerrard Geldenhuis wrote:
> I have the same:
> 
> alias eth0 bnx2
> alias eth1 bnx2
> alias eth2 e1000
> alias eth3 e1000
> 
> my expierence was that by removing hwaddr from the interface config this
> aliases would be ignored. I would get randomize order on boot up. I
> consistently got random ordering of devices ;-)) I tested this by
> rebooting the same server 10 times...
> 
Not sure if it has been mentioned already, but you can fix the order
using udev. In my case I created the file
'/etc/udev/rules.d/local.rules' which contained (for a 2 NIC machine):

KERNEL=="eth?", SYSFS{address}=="00:0e:7f:f0:d2:5b", NAME="eth0"  # tg3
KERNEL=="eth?", SYSFS{address}=="00:0e:7f:f0:d2:5a", NAME="eth1"  # tg3

Now the '...5b' MAC address is always eth0, and likewise '...5a' is
always eth1. I don't use the HWADDR option in the ifcfg- files, yet
bonding works fine.



John.

-- 
---------------------------------------------------------------
John Horne, University of Plymouth, UK  Tel: +44 (0)1752 233914
E-mail: John.Horne@xxxxxxxxxxxxxx       Fax: +44 (0)1752 233839

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux