Moreno's setpe alternative to solve the 2 NIC node setup. Please test.

"Bruce Knox" <[email protected]>
Newsgroups gmane.linux.cluster.openmosix.devel,gmane.linux.cluster.openmosix.general
Message-ID <[email protected]>
This is about a possible replacement or alternate for setpe.  We need some user testing and feedback on Moreno's document below.  Thanks, Bruce
>>From: 	Moreno Baricevic <[email protected]>
To:	Bruce Knox <[email protected]>
Date: 	11/29/05 4:11AM
Subject: 	Re: [openMosix-general] Starting with openMosix

Hi guys,

I wanted to be as much detailed as possible but, perhaps, it's going to
be too verbose. Do you suggest any cut or modification?

Ciao

Moreno

==============================================

I have two NICs and I get this message: setpe: the supplied table is
well-formatted, but my IP address (xxx.xxx.xxx.xxx) is not there!:
---------

Setpe scans the openmosix.map file and tries to find a match with the
"hostname" IP. The compared IP depends on the current hostname (short
host name, as returned by gethostname()) and on the first resolved match
in /etc/hosts or on the dns server (gethostbyname() depends on "order"
line of /etc/host.conf). In the case of 2 or more network interfaces,
the one which owns the IP associated to the short hostname wins,
therefore setpe is not able to find a match for a second interface.

Assuming you have one NIC on the cluster network (192.168.10.250) and
one NIC on a public network (111.111.111.111), to make setpe stop
complaining you have some alternatives. You can tweak your hostname and
/etc/hosts entries, but this solution could lead to other problems if
misconfigured:

1) Assuming hostname == bar:
	/etc/hosts:111.111.111.111	foo.public	foo
	/etc/hosts:192.168.10.250	bar.cluster	bar
   effects:
	hostname -s == bar
	hostname -f == bar.cluster
	IP (setpe)  == 192.168.10.250
2) Assuming hostname == foo:
	/etc/hosts:192.168.10.250	foo.cluster	foo
	/etc/hosts:111.111.111.111	foo.public	# short name != foo
   effects:
	hostname -s = foo
	hostname -f = foo.cluster
	IP (setpe)  == 192.168.10.250
3) Assuming hostname == foo:
	/etc/hosts:192.168.10.250	bar.cluster	bar	foo
	/etc/hosts:111.111.111.111	foo.public	# short name != foo
   effects:
	hostname -s == foo
	hostname -f == bar.cluster
	IP (setpe)  == 192.168.10.250

If you prefer a different and, IMHO, safer solution, you can use the
modified version of setpe available here:
	http://www.democritos.it/~baro/sw/setpe/
This version of setpe scans the openmosix.map file and looks for a match
with the IP of each available network interface (if_nameindex() makes it
independent from the hostname and hosts order). In case of failure
(network not configured), it just falls back to old behaviour and tries
to find a match with hostname (with all that it implies, as described
above).




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.