https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-10930 Lustre <blockquote><p>options lnet forwarding="enabled"</p></blockquote> <p>Setting forwarding="enabled" in lnet modprobe conf file does not enable routing.  That is, after starting lnet with the configuration below, "lnetctl routing show" returns nothing.  Also, a compute node (also 2.11) with a route whose gateway is configured as below, shows the route is down.</p> <p>The specific configuration tested was:</p> <blockquote><p><span class="error">&#91;root@ulna4:~&#93;</span># cat /etc/modprobe.d/lnet.conf<br/> options lnet forwarding="enabled"</p></blockquote> <p>and</p> <blockquote><p><span class="error">&#91;root@ulna4:~&#93;</span># cat /etc/lnet.conf<br/> ip2nets:</p> <ul class="alternate" type="square"> <li>net-spec: o2ib100<br/> interfaces:<br/> 0: san0<br/> ip-range:<br/> 0: 172.19.1.*</li> <li>net-spec: o2ib33<br/> interfaces:<br/> 0: hsi0<br/> ip-range:<br/> 0: 192.168.128.*<br/> route:<br/> &lt;routes redacted&gt;</li> </ul> </blockquote> <p> </p> Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)<br/> Linux 4.14.0-43.el7a.aarch64 LU-10930

lnet module parameter "forwarding" does not enable routing

Bug Minor Open Unresolved Sonia Sharma Olaf Faaland llnl Thu, 19 Apr 2018 15:49:37 +0000 Thu, 19 Apr 2018 19:58:18 +0000 Lustre 2.11.0 0 5 <p>I haven't tested a combination of lnetctl import/YAML configuration and lnet module options configuration like this, in 2.10 yet.</p> <p>Sonia</p> <p>Can you please advise?</p> <p>Thanks</p> <p>Peter</p> <p>There is a couple of ways you can start up LNet. The legacy way is lctl net up. And the new way is lnetctl lnet configure.</p> <p>When you run lnetctl lnet configure. It doesn't configure the system using any of the module parameters which lnetctl handles. This was by design to prevent conflict between module parameters and lnet.conf YAML file.</p> <p>If you would like to load the module parameters you can run: lnetctl lnet configure --all.</p> <p>I see though that you are using lnet.conf to startup the system, so I wouldn't recommend loading the module parameters which are also configured from lnetctl.</p> <p>The idea is to rely on only one source of configuration.</p> <p>&gt; The idea is to rely on only one source of configuration.</p> <p>That makes sense, but then I think at least two changes are necessary:</p> <ol> <li>Lustre should report it when module options are provided but are ignored.</li> <li>The policy you describe should be  loud and proud in the man pages.</li> </ol> <p>Also, <b>lnetctl routing show</b> and <b>lnetctl export</b> need to report that routing is disabled.  As you see below, neither do, although they report when it is enabled.</p> <blockquote><p><span class="error">&#91;faaland1@ulna66 ~&#93;</span> $sudo lnetctl routing show<br/> <span class="error">&#91;faaland1@ulna66 ~&#93;</span> $sudo lnetctl export | grep -C3 routing<br/> <span class="error">&#91;faaland1@ulna66 ~&#93;</span> $</p></blockquote> <p> </p> <p> </p> <p>I verified that with 2.11, if "forwarding" and "networks" are set as module parameters, that <b>lnetctl configure --all</b> does enable routing as well as creating networks and associated NIDs.</p> <p>Also, thanks for the clarification.</p> Development Rank 1|hzzw3j: Rank (Obsolete) 9223372036854775807 Severity