Check out this FAQ entry:
http://www.open-mpi.org/faq/?category=tcp#tcp-routability
We've long-since talked about adding an MCA param to tell Open MPI
"just assume all TCP addresses are reachable from each other" for
cases similar to yours, but it unfortunately hasn't happened yet. :-(
Hi,
To answer your question 172.x.y.z are not behind a NAT .
Moreover, I check the netstat command on the remote host and it seems like
the connection is ok
tcp0 0 10.160.x.x:39794172.x.y.z:50858
ESTABLISHED 20956/orted
unix 3 [ ] STREAM CONNECTED 763
>
> are the 172.x.y.z nodes behind a NAT (hence the communication back
> isn't possible - only the stdout from the rsh/ssh is working in this
> case)?
>
> -- Reuti
Actually I dont know exactly , I am asking extra informations to my
network architect
Interesting thing to notice is that LAM work
Hi,
Am 30.06.2008 um 17:29 schrieb Geoffroy Pignot:
Hi,
Does anybody face problems running Openmpi on two hosts with
different networks (gateway to reach the other) ?
Let say compil02 ip adress is 172.3.9.10 and r009n001 is 10.160.4.1
There is no problem with MPI_init free executables (for
Hi,
Does anybody face problems running Openmpi on two hosts with different
networks (gateway to reach the other) ?
Let say compil02 ip adress is 172.3.9.10 and r009n001 is 10.160.4.1
There is no problem with MPI_init free executables (for example hostname)
compil02% /tmp/HALMPI/openmpi-1.2.2/bin
