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. :-(
On Jul 3, 2008, at 3:05 AM, Geoffroy Pignot wrote:
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
tcp 0 0 10.160.x.x:39794 172.x.y.z:
50858 ESTABLISHED 20956/orted
unix 3 [ ] STREAM CONNECTED 76348311 20956/orted
unix 3 [ ] STREAM CONNECTED 76348310 20956/orted
I hope it'll help
Does anyone run openmpi program in such environment ???
Thanks again
Geoffroy
2008/7/2 Geoffroy Pignot <geopig...@gmail.com>:
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 worked in such kind of
network configuration.
I keep you inform as soon as I have more infos.
Regards
Geoffroy
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
Cisco Systems