The current version of Open MPI doesn't handle such situations. You either have
to configure your NAT differently or try to get your hands on one of the
NAT-aware versions as described here
http://www-lipn.univ-paris13.fr/~coti/QosCosGrid/qcgompi.php.
george.
On Oct 10, 2011, at 12:14 , (.-=
I'm confused... my IPs right now are:
Computer 1 (192.168.31.2 internal / 210.1.1.39 external)
Computer 2 (192.168.31.3 internal / 210.1.1.40 external)
Computer 3 (210.1.1.137)
I want Computer 1 to launch mpirun and Computer 3 to do the task.
I tried both these commands first on Computer 1 and t
The real solution is to evict the private addresses from both levels (MPI and
ORTE). However, based on the ordering of the interfaces, I guess you cannot do
it by name (eth0 has a private address on one side but a public one on the
other).
No panic! There is support for this.
Look at the outpu
Ah...you're dealing with NAT. Sorry, I didn't understand that.
OMPI currently doesn't handle NAT well. :-(
There was some work at U. Tennessee to handle NAT nicely, but I think they
forked off and made their own release based on an older version of Open MPI.
...or maybe I'm remembering that
The thing is that there's just one interface: eth0.
Computer 1 thinks that it has 212... but it actually has a 210 when accessed
from outside. There's no other interface to choose from, just the one that
thinks it's a 212, the eth0.
Or maybe I'm just not understanding correctly.
---
On Wed,
Check out this FAQ entry:
http://www.open-mpi.org/faq/?category=tcp#tcp-selection
Note that there are btl_tcp_if_include / btl_tcp_if_exclude: these control
MPI-level communications. There's also oob_tcp_if_include / oob_tcp_if_exclude
(that take the same kinds of values as btl_tcp_if_incl
"OMPI always tries to use the lowest numbered address first - just a natural
ordering."
That doesn't seem to be the reason. We changed the private IPs to 212... (a
higher number than the public 210... IPs) and still MPI tries to go to 212
afterwards.
We're reading the oob_tcp and btl_tcp paramete
Does a "hello world" MPI app (with no MPI_SEND/MPI_RECV) in it work without
those params, but an MPI app with MPI_SEND/MPI_RECV hang?
If so, that's a little disappointing -- OMPI's MPI layer should be able to tell
the difference between the different networks and should be able to figure out
ro
OMPI always tries to use the lowest numbered address first - just a natural
ordering. You need to tell it to use just the public ones for this topology.
Use the oob_tcp and btl_tcp parameters to do this. See "ompi_info --param oob
tcp" and "ompi_info --param btl tcp" for the exact syntax.
Sent
We are constructing a set of computers with Open MPI and there's a small
problem with mixing public and private IPs.
We aren't sure about what's causing the problem or how to solve it.
The files are shared thanks to NFS and we have a couple computers with
private IPs and public IPs that we want t
10 matches
Mail list logo
