[OMPI users] --mca btl params

[Jeffrey A Cummings]

What are the allowable values for the –mca btl parameter on the mpirun command line?

– Jeff

Jeffrey A. Cummings
Engineering Specialist
Mission Analysis and Operations Department
Systems Analysis and Simulation Subdivision
Systems Engineering Division
Engineering and Technology Group
The Aerospace Corporation
571-304-7548
***@aero.org

From: users [mailto:users-***@lists.open-mpi.org] On Behalf Of Andy Riebs
Sent: Tuesday, October 09, 2018 2:34 PM
To: ***@lists.open-mpi.org
Subject: Re: [OMPI users] no openmpi over IB on new CentOS 7 system

Noam,

Start with the FAQ, etc., under "Getting Help/Support" in the left-column menu at https://www.open-mpi.org/

Andy
________________________________
From: Noam Bernstein <***@nrl.navy.mil><mailto:***@nrl.navy.mil>
Sent: Tuesday, October 09, 2018 2:26PM
To: Open Mpi Users <***@lists.open-mpi.org><mailto:***@lists.open-mpi.org>
Cc:
Subject: [OMPI users] no openmpi over IB on new CentOS 7 system
Hi - I’m trying to get OpenMPI working on a newly configured CentOS 7 system, and I’m not even sure what information would be useful to provide. I’m using the CentOS built in libibverbs and/or libfabric, and I configure openmpi with just
—with-verbs —with-ofi —prefix=$DEST
also tried —without-ofi, no change. Basically, I can run with “—mca btl self,vader”, but if I try “—mca btl,openib” I get an error from each process:
[compute-0-0][[24658,1],5][connect/btl_openib_connect_udcm.c:1245:udcm_rc_qp_to_rtr] error modifing QP to RTR errno says Invalid argument
If I don’t specify the btl it appears to try to set up openib with the same errors, then crashes on some free() related segfault, presumably when it tries to actually use vader.

The machine seems to be able to see its IB interface, as reported by things like ibstatus or ibv_devinfo. I’m not sure what else to look for. I also confirmed that “ulimit -l” reports unlimited.

Does anyone have any suggestions as to how to diagnose this issue?

thanks,
Noam




_______________________________________________

users mailing list

***@lists.open-mpi.org<mailto:***@lists.open-mpi.org>

https://lists.open-mpi.org/mailman/listinfo/users

[Noam Bernstein]

Post by Jeffrey A Cummings
What are the allowable values for the –mca btl parameter on the mpirun command line?

That's basically what the output of
ompi_info -a
says.

So it appears, for the moment at least, like things are magically better. In the process of organizing all the information that's requested on the web site, I caught some (I thought innocuous, but apparently not) mismatches in kernel-related rpms on the nodes. Once those were cleared up things started working. I don't really know why, but the point is moot. Thanks.

Noam

[Noam Bernstein]

Post by Noam Bernstein

Post by Jeffrey A Cummings
What are the allowable values for the –mca btl parameter on the mpirun command line?

That's basically what the output of
ompi_info -a
says.

Oops - managed to fail to paste in the actual result. I can get that tomorrow.

Noam

[Jeff Squyres (jsquyres) via users]

Post by Noam Bernstein
That's basically what the output of
ompi_info -a
says.

You actually probably want:

ompi_info | grep btl

That will show you the names and versions of the "btl" plugins that are available on your system. For example, this is what I have on my system from a development build (this is on the Open MPI development head; not in a release):

----
$ ompi_info | grep btl
MCA btl: ofi (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA btl: self (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA btl: vader (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA btl: openib (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA btl: usnic (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA btl: tcp (MCA v2.1.0, API v3.1.0, Component v4.1.0)
MCA fbtl: posix (MCA v2.1.0, API v2.0.0, Component v4.1.0)
----

You can get fancy and get parsable output, too:

----
$ ompi_info --parsable | grep :btl: | grep component
mca:btl:ofi:version:"component:4.1.0"
mca:btl:self:version:"component:4.1.0"
mca:btl:vader:version:"component:4.1.0"
mca:btl:openib:version:"component:4.1.0"
mca:btl:template:version:"component:4.1.0"
mca:btl:usnic:version:"component:4.1.0"
mca:btl:tcp:version:"component:4.1.0"
-----