I’m having an issue with MLNX_OFED_LINUX-4.6-1.0-.1.1-rhel7.6-x86_64.iso - seems to remove rdma core and the associated devel tools. The “–all” option with the installer didn’t include them. Running the installer a second time with “–dpdk --upstream-libs” seemed to include them.
Also there appears to be a conflict with the installer and “opa-address-resolution” and “pa-libopamgt”.
I started with a relatively clean install of RHEL 7.6 with the groupinstall for “Infiniband Support”.
Is installing with the “–dpdk --upstream-libs” option a second time the correct sequence of events to keep the development packages installed?
Shouldn’t the “–upstream-libs” option also be available for all the other options?
Hope you are doing well. We noticed that you have a valid Mellanox Support contract so we converted all three requests you made through the Mellanox Community into Support Cases.
Our Support engineers will be in touch with you shortly to assist you with the requests.
Just a note on the resolution that ended up working for me and my odd use-case:
See the mlnxofedinstall script. Comment the lines 644 to 648 out, then use “./mlnxofedinstall --upstream-libs”.
The comments (“#”) start with the line “if ($use_upstream_libs and $install_option ne ‘dpdk’) {“ and continue through that block.
That ended up installing opensmd, openibd, and all of the rdma core / upstream libs back. I’m not trying to do DPDK development. I was just trying to code at the verbs level. I also had two ports running, one IB and one Eth on these VPI cards.
And I’ve been corrected by the nice folks at Mellanox… for reference use:
mlnxofedinstall –all –force –without-32bit
That gets the mellanox tools installed, both opensmd and openibd pieces, plus the headers/etc to compile at the verbs layer. It might not be the latest version of verbs… but going to “upstream libs” is on you.