Hi Allan, Thanks for the tip. But since oscar-devel list apparently was stuck for a couple of days I had to dig for a solution myself. I found a nice example of how to achieve what I needed by using post-install scripts, posted by Andrea Righi on sisuite-users list about two years ago. So I was able to model around his script and make it do the trick. If someone else interested I can post it here. The problem was that BOEL kernel and kernel in the golden image (which are of course different) enumerated NICs on clients differently. So when autoinstall script run on a client under network boot it uses different value of $DEVICE variable to generate ifcfg-ethN file (eth1). Now when local kernel booted, the same interface was enumerated as eth0 and never got configured. I had to hardwire eth0 NIC name in my post-install script and also delete all other ifcfg-ethN script created by autoinstall script. After that the network was configured correctly. Andrea actually had a more generic solution that can be used to configure any arbitrary number of interfaces on a client in any desirable way (by using a separate config file with a list of all NICs configuration parameters).
--Ivan On Tuesday 12 June 2007 08:42:25 pm Allan Menezes wrote: > Hi Ivan, > Here's my 2 cents: > Suppose your clients are x1, x2, x3 ... > then suppose they have one or two nics and you know the mac addresses of > each nic ( ifconfig ..) > then make a directory say 'tc' of ifcfg-eth0 ifcfg-eth1 ... within each > sub dir x1, x2 and put in in the master nodes client image > /var/lib/systemimager/images/oscarimage/etc/sysconfig/network-scripts/tc > I use pxe boot so each node boots and then i just reboot the node after > copyining say on xn : cd /etc/sysconfig/network-scripts/tc/xn: cp * > /etc/sysconfig/network-scripts. > This will write over the oscar created ifcfg-ethn with your own from the > master node but thats provided you know the mac addresses of each nic. > You store this dir tc ( testcluster) on to a flash drive for each time > you have to reinstall > your cluster( saves you future work for any distro) > Thank you, > Hope this helps > Allan Menezes > > Ivan Adzhubey wrote: > >Hi, > > > >Is there an easy way to configure system image to bind client's network > >interface to a particular MAC hardware address on boot? With RedHat/Fedora > >all I need to do is insert 'HWADDR=<client's NIC MAC address>' line > >to /etc/sysconfig/network-scripts/ifcfg-eth0, but how would I figure a > >correct MAC for a client? > > > >--Ivan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
