[LU-7474] Using lnet init script and lnetctl brings up tcp interface

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.7.0
• Labels: patch
• Environment: RHEL 6.6; lustre-client-2.7.1-2.6.32_504.30.3.el6.x86_64_g43f9fd9.x86_64
• Severity: 3
• Assignee: Doug Oucharek (Inactive)
• Reporter: Jesse Hanley

Description

We're attempting to migrate to lnetctl for some of our setup rather than using the lnet modprobe.conf file.

We removed the ip2nets parameter from the conf, and generated our /etc/sysconfig/lnet.conf file. Using the following method works (from an unconfigured system):

• modprobe lnet
• lnetctl lnet configure
• lnetctl import < /etc/sysconfig/lnet.conf

The problem we're seeing is that the LNET init script calls lctl network up, which configures a default nid on the tcp interface (instead of the InfiniBand interface).

Is this indented behavior? Currently, we're planning to use the following in our LNET init script instead:

125,129c125
<       if [ -f $LUSTRE_LNET_CONFIG_UTILITY ] && [ -f "$LUSTRE_LNET_CONFIG_FILE" ]; then
<                 $LUSTRE_LNET_CONFIG_UTILITY lnet configure || exit 1
<         else
<                 lctl network up || exit 1
<         fi
---
>       lctl network up || exit 1

Thanks!
–
Jesse

Issue Links

• duplicates: LU-6340 DLC: /etc/rc.d/init.d/lnet doesn't configure lnet exactly as defined in lnet.conf