That does the trick. I set:

export MPIR_CVAR_CH3_PORT_RANGE=10100:10200

set up all the firewalls, and waited for mpiexec to time out.
This way I can see which port it decided to open.

Now I see port 10100 is being used.

[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi
[proxy:0:1@oswrk207.lns.mit.edu] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "oswrk207.lns.mit.edu" to "198.125.163.210" (Connection timed out)
[proxy:0:1@oswrk207.lns.mit.edu] main (pm/pmiserv/pmip.c:189): unable to connect to server 198.125.163.210 at port 10100 (check for firewalls!)


Next, I open only a range of ports on the openStack controller:


and my pi computation went through:

[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi
Process 3 of 4 is on oswrk207.lns.mit.edu
Process 2 of 4 is on oswrk207.lns.mit.edu
ProcessB 0 of 4 is on oswrk210.lns.mit.edu
ProcessB 1 of 4 is on oswrk210.lns.mit.edu
pi is approximately 3.1415926535902168, Error is 0.0000000000004237
wall clock time = 0.161488

 
Thanks a lot - this lets me move forward.
You can close this ticket
Jan


On Apr 23, 2014, at 11:35 PM, "Balaji, Pavan" <balaji@anl.gov> wrote:

Jan,

It looks like mpiexec is not respecting all the aliases for that environment variable.  Can you use MPIR_CVAR_CH3_PORT_RANGE to set the port range for now?  We’ll add MPICH_PORT_RANGE as an alias for it in the next release.

FWIW, use the README.envvar for the environment variable names.  They should contain the correct information.  Aliases are only maintained for backward compatibility.

 — Pavan

On Apr 23, 2014, at 10:06 PM, Jan Balewski <balewski@MIT.EDU> wrote:


On Apr 23, 2014, at 5:32 PM, Kenneth Raffenetti <raffenet@mcs.anl.gov> wrote:

You can control the port range that mpich will use. See this item in the FAQ

http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do_I_control_which_ports_MPICH_uses.3F

Hi,
Thanks, but somehow setting of MPICH_PORT_RANGE variable on the master VM does not propagate.
mpiexec still tries to open the  port 34781 which is out of the range set by
export MPICH_PORT_RANGE=10000:10100

I'm missing sth  - not sure what?
Jan

--------
[cosy11@oswrk210 mpich-3.1]$ echo $MPICH_PORT_RANGE
10000:10100

[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi
[proxy:0:1@oswrk207.lns.mit.edu] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "oswrk207.lns.mit.edu" to "198.125.163.210" (Connection timed out)
[proxy:0:1@oswrk207.lns.mit.edu] main (pm/pmiserv/pmip.c:189): unable to connect to server 198.125.163.210 at port 34781 (check for firewalls!)

_______________________________________________
discuss mailing list     discuss@mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list     discuss@mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss