Gerrard Geldenhuis wrote:
anaconda adds these lines at build time to the eth devices. We have a
sript in the kickstart that configures bonding and remove these lines
from the eth0 and eth2 devices.
I can change the script to not do that but I am still unsure that this
would always be persistent at build time. If I build a 1000 servers will
they all build with the same interface eth0 and eth2? If it is random
for normal boot then I don't believe it will be any other way for
building. I am also not keen on hand editing a large amount of servers
to fix this.
The bonding driver suggest trying to add this:
BONDING_SLAVE1="bus-pci-0000:06:08.1"
to the ifcfg-bond0 file.
I still need to try that. That looks like a sure fire way for it to work
predictably everytime.
Regards
Detecting the PCI devices is not random, but determined via MB-BIOSs &
how the PCI bus is scanned... usually pci devices closest to the CPU are
detected first. IIRC, you can move cards around to different slots &
make the PCI-IDs change, which in turn will change the order of eth#
detection if swapping NICs. Motherboard/Chipbased NIC PCI-IDs are
determined by the order which BIOS scans those devices.
We discussed something similar on another list recently, here a summary
from Michael & Jan...
The HWADDR line is required when:
* you need to have an IP go onto a specific NIC and
* when the server may auto-assign PCI addresses to NIC's on boot
It is recommended to always use HWADDR to guarantee that a NIC is on a
specific IP, if you don't use it you do stand the chance that an IP
assigned in ifcfg-eth? can
go to a different physical NIC.
...
Drivers evolve and add support for new devices (example using lscpi to
identify a realtek r8169 ethernet driver)...
To verify:
try "lspci", identify your network card slot (e.g. '01:0d.0'). Run
"lspci -vvn -s 01:0d.0". This gives the PCI Id in numeric form (01:0d.0
Class 0280: MAJOR MINOR..)
Then run "modinfo r8169". This will give a list of PCI IDs (major and
minor ID concatenated into one big hex number) this driver feels
responsible for. If your card isn't in there, the driver will ignore it.
If it is there, the driver still may look at the "Subsystem" ID and
decide it cannot handle that flavour of the card - unfortunately there
you would need to look into the driver source code to make sure.
The "modinfo" command is something you can run. With the PCI ID, you can
the start Googling for which exact version of the driver added support
for your card... or for other drivers that also might be able to support
this.
================
It occurred to me you may be able to script the lscpi & modinfo commands
to determine your PCI-ID Major/Minor numbers & tie the MACs to them
automatically. A number of the large labs & cluster suites have tackled
these issues already, you may find more info & support there or on the
Kickstart & Cobbler lists.
Here is a method of Automatically determining the MAC Addresses for
large scale installations...
How to Install Red Hat Linux via PXE and Kickstart - Automatic MAC
address detection
http://www.stanford.edu/~alfw/PXE-Kickstart/PXE-Kickstart-5.html
Cobbler - DHCP Features, Kickstart & AutoRegistration Wiki Docs
http://cobbler.et.redhat.com/cobbler-dhcp.php
https://fedorahosted.org/cobbler/wiki/UserDocs
Anaconda + Kickstart Network Issues (Fedora Wiki)
http://fedoraproject.org/wiki/Anaconda/NetworkIssues
-HTH [EMAIL PROTECTED]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
