On Friday 10 October 2003 10:30, you wrote:
> Hi Andreas,
>
> Hum,, this listen me strange because i give with file lamboot -d -v
> lamfile where lamfile are the file with contains the ip on the machine ,
> the real ip , but anyway still have the problems, i just can give the
> alias name or i can give the ip number?
>
Hi,
it should work with alias names and with IP-addresses. My lam-boot-scheme
file looks like this:
lilian
lilian2
lilian3
lilian4
while the /etc/hosts file on lilian, which I use as the lam-home-node is
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.1.2 lilian2
192.168.1.3 lilian3
192.168.1.4 lilian4
192.168.1.1 lilian.eas.iis.fhg.de lilian
153.96.107.115 lilian.eas.iis.fhg.de
As you can see, lilian has two NICs, the cluster works on the 192.168.1 net.
If a setup like this doesn't work, you must give some more information on
what your cluster looks like. Supposing your machines have the IP-numbers
192.168.1.1, 192.168.1.2, ... , and your lam-boot-scheme looks like
192.168.1.1
192.168.1.2
...
and lamboot fails, then you probably have a misconfigured network, like in my
case.
andreas
--
________________________________________________
Andreas Wilde
Fraunhofer-Institut fuer Integrierte Schaltungen
Aussenstelle Entwurfsautomatisierung
Zeunerstr. 38
D-01069 Dresden
Tel.: 49 (0) 351 4640 852
Fax : 49 (0) 351 4640 703
E-Mail: Andreas.Wilde_at_[hidden]
________________________________________________
|
