Re: [OSR-devel] IPs in cluster.conf and manual startup

[<go...@bo...>]

On Tue, 6 Nov 2007, Mark Hlawatschek wrote:

>> I'm having a problem with the way the ifcfg-eth* files are being handled
>> for the initrd. My ifcfg-eth1 file doesn't get transferred across
>> verbatim. This is a problem because I have to explicitly specify the
>> HWADDR in my ifcfg files (therwise they come up on wrong subnets).
> The initrd creates new ifcfg-ethX files for the defined ethernet interface for
> its internal use. I.e. for all <eth /> entries for the node in the
> cluster.conf. These file are only valid inside the initrd.

Sure, but the iSCSI interface has to be the same in root and initrd, 
otherwise it won't work.

>> It looks as if mkinitrd removes some lines from the file, and this causes
>> eth1 to be physical eth0, which puts it on the wrong subnet, and that
>> means it can't see the iSCSI shares.  :-(
>>
>> I checked the /etc/sysconfig/network-scripts/ifcfg-eth1 in the initrd, and
>> it is indeed lacking the HWADDR line (and a few others).
>>
>> Am I missing something here? Does mkinitrd mangle the ifcfg-eth* files?
> The mkinitd does not modify the ifcfg-ethX files.
> If you want to define the HWADDR parameter in the ifcfg-ethX files, you have
> to make them hostdependent.

I did, but network-lib.sh checks if it's in the initrd, and if so saves 
a backup and creates a new one from the parameters that come from 
elsewhere (I'm assuimg from cluster.conf).

The new one doesn't have the HWADDR parameter in it, because it isn't one 
of the things passed to network-lib.sh. So, any interface that are bound 
by MAC address rather than the default ordering won't work properly in the 
initrd. I have interface name, ip and mac specified in cluster.conf, but 
it never gets included in the built ifcfg file. :-(

Gordan