Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: [OMPI users] btl_tcp_if_include setting
From: Ray Sheppard (rsheppar_at_[hidden])
Date: 2013-10-14 10:27:35


Hi,
   I am setting up version 1.7.2 for a Cray XE-6. The build nodes have
different interfaces than the compute nodes. I have been able to set it
up, but users need to embed the following into their mpirun command:
--mca btl_tcp_if_include ipogif0

Currently, The ompi_info shows as below. I have been trying to figure
out the correct configure switch to add to the build to remove the need
for a permanent mpirun switch, but seem to be not getting it right. Any
suggestions are welcomed. Thanks,
      Ray

  ompi_info --param btl all
                  MCA btl: parameter "btl_tcp_if_include" (current
value: "",
                           data source: default, level: 1 user/basic, type:
                           string)
                           Comma-delimited list of devices and/or CIDR
                           notation of networks to use for MPI communication
                           (e.g., "eth0,192.168.0.0/16"). Mutually
exclusive
                           with btl_tcp_if_exclude.
                  MCA btl: parameter "btl_tcp_if_exclude" (current value:
                           "127.0.0.1/8,sppp", data source: default,
level: 1
                           user/basic, type: string)
                           Comma-delimited list of devices and/or CIDR
                           notation of networks to NOT use for MPI
                           communication -- all devices not matching these
                           specifications will be used (e.g.,
                           "eth0,192.168.0.0/16"). If set to a non-default
                           value, it is mutually exclusive with
                           btl_tcp_if_include.