IBM Support

rmmTierInit() fails to allocate a port when running Low Latency Messaging over InfiniBand

Troubleshooting


Problem

Running Low Latency Messaging on Linux over native InfiniBand, rmmTierInit() fails to allocate a port.

Symptom

The following log event occurs during rmmTierInit():

13418 RMMT The RMM transmitter instance was not created because of a failure to allocate a port number.

Cause

The OFED implementation is not able to pin a large enough amount of memory.

Resolving The Problem


Increase the memlock limits in /etc/security/limits.conf file.

When using the native InfiniBand implementation, you must increase the memlock limit so that he OFED implementation can pin a large amount of memory.

In order to increase the soft and hard memlock limits, add the following lines to the file /etc/security/limits.conf file:

<username or *> hard memlock <size in kbytes>
<username or *> soft memlock <size in kbytes>

Examples:

To set unlimited space for all users, add the following lines to the file:

    * soft memlock unlimited
    * hard memlock unlimited

To set the limits for all users to 256MB, add the following lines to the file:
    * soft memlock 262144
    * hard memlock 262144

[{"Product":{"code":"SSQPD3","label":"WebSphere MQ Low Latency Messaging"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.2;2.3;2.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 June 2018

UID

swg21407845