<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">That does the trick. I set:<div><br><div>export MPIR_CVAR_CH3_PORT_RANGE=10100:10200</div><div><br></div><div>set up all the firewalls, and waited for mpiexec to time out.</div><div>This way I can see which port it decided to open.</div><div><br></div><div>Now I see port 10100 is being used.</div><div><br></div><div>[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi<br>[proxy:0:1@<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>" to "198.125.163.210" (Connection timed out)<br>[proxy:0:1@<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>] main (pm/pmiserv/pmip.c:189): unable to connect to server 198.125.163.210 at port 10100 (check for firewalls!)<br><br></div><div><br></div><div>Next, I open only a range of ports on the openStack controller:</div><div><img id="e30341d1-0c24-4785-8019-e8834952cf85" height="45" width="693" apple-width="yes" apple-height="yes" src="cid:EF29140E-1552-4621-AEEA-06BB530933E0"></div><div><br></div><div><br></div><div>and my pi computation went through:</div><div><br></div>[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi<br>Process 3 of 4 is on <a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a><br>Process 2 of 4 is on <a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a><br>ProcessB 0 of 4 is on <a href="http://oswrk210.lns.mit.edu">oswrk210.lns.mit.edu</a><br>ProcessB 1 of 4 is on <a href="http://oswrk210.lns.mit.edu">oswrk210.lns.mit.edu</a><br>pi is approximately 3.1415926535902168, Error is 0.0000000000004237<br>wall clock time = 0.161488<br><br><div> </div><div>Thanks a lot - this lets me move forward.</div><div>You can close this ticket</div><div>Jan</div><div><br></div><div><br><div><div>On Apr 23, 2014, at 11:35 PM, "Balaji, Pavan" <<a href="mailto:balaji@anl.gov">balaji@anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Jan,<br><br>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.<br><br>FWIW, use the README.envvar for the environment variable names. They should contain the correct information. Aliases are only maintained for backward compatibility.<br><br> — Pavan<br><br>On Apr 23, 2014, at 10:06 PM, Jan Balewski <<a href="mailto:balewski@MIT.EDU">balewski@MIT.EDU</a>> wrote:<br><br><blockquote type="cite"><br>On Apr 23, 2014, at 5:32 PM, Kenneth Raffenetti <<a href="mailto:raffenet@mcs.anl.gov">raffenet@mcs.anl.gov</a>> wrote:<br><br><blockquote type="cite">You can control the port range that mpich will use. See this item in the FAQ<br><br><a href="http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do_I_control_which_ports_MPICH_uses.3F">http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_How_do_I_control_which_ports_MPICH_uses.3F</a><br></blockquote><br>Hi,<br>Thanks, but somehow setting of MPICH_PORT_RANGE variable on the master VM does not propagate.<br>mpiexec still tries to open the port 34781 which is out of the range set by <br>export MPICH_PORT_RANGE=10000:10100<br><br>I'm missing sth - not sure what?<br>Jan<br><br>--------<br>[cosy11@oswrk210 mpich-3.1]$ echo $MPICH_PORT_RANGE<br>10000:10100<br><br>[cosy11@oswrk210 mpich-3.1]$ mpiexec -f machinefile2 -n 4 ./examples/cpi<br>[proxy:0:1@<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>] HYDU_sock_connect (utils/sock/sock.c:172): unable to connect from "<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>" to "198.125.163.210" (Connection timed out)<br>[proxy:0:1@<a href="http://oswrk207.lns.mit.edu">oswrk207.lns.mit.edu</a>] main (pm/pmiserv/pmip.c:189): unable to connect to server 198.125.163.210 at port 34781 (check for firewalls!)<br><br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote></div><br></div></div></body></html>