It won't be a configure switch, but you can put the following in your default system mca param file:
btl_tcp_if_include=ipogif0 You'll find that file in <prefix>/etc - it is called openmpi-mca-params.conf. Users won't have to enter it after that since we pick that file up by default. On Oct 14, 2013, at 7:27 AM, Ray Sheppard <rshep...@iu.edu> wrote: > 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. > > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
