ibd0 and ce0 have to be on the same network for this to work. Or said
differently IP must be able to find a route between en0 and idb0. If
those are on different private networks (like 192.168.1.x and
192.168.2.x) this will not work.
Aurelien
Le 11 janv. 08 à 16:05, Rolf Vandevaart a écrit
Hello:
Have you actually tried this and got it to work? It did not work for me.
burl-ct-v440-0 50 =>mpirun -host burl-ct-v440-0,burl-ct-v440-1 -np 1
-mca btl self,sm,tcp -mca btl_tcp_if_include ce0 connectivity_c : -np 1
-mca btl self,sm,tcp -mca btl_tcp_if_include ce0 connectivity_c
Connec
Try something similar to this
mpirun -np 1 -mca btl self,tcp -mca btl_tcp_if_include en1 NetPIPE_3.6/
NPmpi : -np 1 -mca btl self,tcp -mca btl_tcp_if_include en0
NetPIPE_3.6/NPmpi
You should then be able to specify a different if_include mask for you
different processes.
Aurelien
Le 11
On Fri, Jan 11, 2008 at 11:36:23AM +, Lydia Heck wrote:
> I have a setup which contains one set of machines
> with one nge and one e1000g network and of machines
> with two e1000g networks configured. I am planning a
Are we talking about shared filesystems or can you place different
~/.openmp
I should have added that the two networks are not routable,
and that they are private class B.
On Fri, 11 Jan 2008, Lydia Heck wrote:
>
> I have a setup which contains one set of machines
> with one nge and one e1000g network and of machines
> with two e1000g networks configured. I am planning
I have a setup which contains one set of machines
with one nge and one e1000g network and of machines
with two e1000g networks configured. I am planning a
large run where all these computers will be occupied
with one job and the mpi communication should only go
over one specific network which is c
