This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
What George is saying is that OMPI has two different systems that use
sockets: the BTL (MPI communications) and the OOB (OMPI's internal
We've been talking about the TCP BTL parameters over the rest of this
For the TCP OOB, it looks like the parameter name is
"oob_tcp_static_ports". I think it takes a comma-delimited list of
ports. You can probably specify, say, 10000 for btl_tcp_port_min_v4
and 9000 for oob_tcp_static_ports. For example:
mpirun --mca oob_tcp_static_ports 9000 --mca oob_tcp_static_ports
10000 --mca btl tcp,self ring
If you don't want to put those two variables on every mpirun command,
you can set them in your environment, put them in your personal params
file, or in the master params file. Just make sure that those files
are either the same on all nodes or visible on all nodes. :-)
On Apr 3, 2009, at 4:33 AM, Jerome BENOIT wrote:
> Hello List !
> George Bosilca wrote:
> > The range of ports for the OOB TCP has been removed by commit
> > Apparently it was replaced by the static port functionality. Only
> > TCP BTL use the range mechanism.
> if applicable, what is the parameter name for the this static port ?