On Dec 18, 2011, at 4:43 PM, Jaison Paul wrote:
> We have reported this before. We are still not able to do it, fully.
>
> However partially successful, now. We have used a machine with static IP
> address
> and modified the router settings by opening all ssh ports. Master runs on this
> machine and the slaves on EC2.
>
> Now we can run the "Hello world" over internet using ssh. It starts MPI
> executables in EC2 (we can see on 'top') and print back "hello" to our
> home/master machine.
>
> But send/recv doesnt work. send/recv hang between master(home
> PC)<->slave(EC2),
> both ways.
>
> What are the port settings for send/recv? Do we need to modify anything?
Have you looked at all the other EC2 discussions on the user list? Several
people have provided instructions on how to deal with the EC2 security
settings. Unfortunately, this is all a firewall/security issue.
It sounds like the out-of-band connections required by the RTE are getting
through. However, the MPI connections are created separately. You can force the
selection by setting the mca parameters to fit the EC2 and local firewall
settings:
MCA btl: parameter "btl_tcp_if_include" (current value:
, data source: default value)
Comma-delimited list of devices or CIDR notation of
networks to use for MPI communication (e.g.,
"eth0,eth1" or "192.168.0.0/16,10.1.4.0/24").
Mutually exclusive with btl_tcp_if_exclude.
MCA btl: parameter "btl_tcp_port_min_v4" (current value:
<1024>, data source: default value)
The minimum port where the TCP BTL will try to bind
(default 1024)
MCA btl: parameter "btl_tcp_port_range_v4" (current value:
<64511>, data source: default value)
The number of ports where the TCP BTL will try to
bind (default 64511). This parameter together with
the port min, define a range of ports where Open MPI
will open sockets.
>
> Any help is very much appreciated.
>
> Jaison
> Australian National Uni
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
