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-10003 Lustre <p>trying to add second interface getting an error</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> nbpt-serv1 ~ # ip -4 addr 1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN qlen 1 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 6: ib0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc mq state UP qlen 1024 inet 192.168.41.10/24 brd 192.168.41.255 scope global ib0 valid_lft forever preferred_lft forever 7: ib1: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc mq state UP qlen 1024 inet 10.151.20.103/18 brd 10.151.63.255 scope global ib1 valid_lft forever preferred_lft forever 8: ib2: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc mq state UP qlen 1024 inet 192.168.44.10/24 brd 192.168.44.255 scope global ib2 valid_lft forever preferred_lft forever 9: ib3: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc mq state UP qlen 1024 inet 10.151.63.233/18 brd 10.151.63.255 scope global ib3 valid_lft forever preferred_lft forever 10: bond0: &lt;BROADCAST,MULTICAST,MASTER,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UP qlen 1000 inet 172.17.0.156/16 brd 172.17.255.255 scope global bond0 valid_lft forever preferred_lft forever nbpt-serv1 ~ # lnetctl net show net: - net type: lo local NI(s): - nid: 0@lo status: up - net type: o2ib local NI(s): - nid: 10.151.20.103@o2ib status: up interfaces: 0: ib1 nbpt-serv1 ~ # lnetctl net add --net o2ib --<span class="code-keyword">if</span> ib3 add: - net: errno: -22 descr: <span class="code-quote">"cannot add network: Invalid argument"</span> nbpt-serv1 ~ # lnetctl net del --net o2ib --<span class="code-keyword">if</span> ib1 del: - net: errno: -22 descr: <span class="code-quote">"cannot del network: Invalid argument"</span> </pre> </div></div> <p> </p> <p> </p> <p> </p> LU-10003

lnetctl error "cannot add network: invalid argument"

Bug Major Reopened Unresolved James A Simmons Mahmoud Hanafi Tue, 19 Sep 2017 00:32:47 +0000 Fri, 26 Jan 2024 19:52:05 +0000 Lustre 2.10.0 2 12 <p>looks like it is fails here</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> rc = l_ioctl(LNET_DEV_ID, IOC_LIBCFS_ADD_LOCAL_NI, data); (gdb) s l_ioctl (dev_id=dev_id@entry=0, opc=opc@entry=3233310047, buf=buf@entry=0x618190) at util/l_ioctl.c:106 $1 = {lic_cfg_hdr = {ioc_len = 2728, ioc_version = 65547}, lic_nid = 1407375061237737, lic_ni_intf = { <span class="code-quote">"ib3"</span>, <span class="code-quote">'\000'</span> &lt;repeats 124 times&gt;, <span class="code-quote">'\000'</span> &lt;repeats 127 times&gt; &lt;repeats 15 times&gt;}, lic_legacy_ip2nets = <span class="code-quote">'\000'</span> &lt;repeats 127 times&gt;, lic_cpts = {0 &lt;repeats 128 times&gt;}, lic_ncpts = 0, lic_status = 0, lic_tcp_bonding = 0, lic_idx = 0, lic_dev_cpt = 0, pad = <span class="code-quote">"\000\000\000"</span>, lic_bulk = 0x618b98 <span class="code-quote">"q\004\002"</span>} </pre> </div></div> <p>Amir</p> <p>Could you please advise?</p> <p>Thanks</p> <p>Peter</p> <p>if you try and add the same interface twice, it'll fail the second time. </p> <p>But it should be able to add a different interface. Can you please enable debug logs and attach them here:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lctl set_param debug=+net lctl set_param debug=+neterror lnetctl net add --net o2ib --<span class="code-keyword">if</span> ib3 lctl dk &gt; log </pre> </div></div> <p>Also just to verify can you please paste the output from:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lnetctl -h </pre> </div></div> <p>here is the output</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">elrtr10 ~ # lctl clear;lctl set_param debug=+net;lctl set_param debug=+neterror;lnetctl net add --net o2ib --<span class="code-keyword">if</span> ib0;lctl dk &gt; log debug=+net debug=+neterror add: - net: errno: -22 descr: <span class="code-quote">"cannot add network: Invalid argument"</span> elrtr10 ~ # cat log 00000400:00000080:38.0F:1506037088.299967:0:3941:0:(module.c:121:libcfs_ioctl()) libcfs ioctl cmd 3233310047 Debug log: 1 lines, 1 kept, 0 dropped, 0 bad. elrtr10 ~ # ip -o -4 add show 1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 6: ib0 inet 10.151.26.140/18 brd 10.151.63.255 scope global ib0\ valid_lft forever preferred_lft forever 7: ib1 inet 10.151.26.60/18 brd 10.151.63.255 scope global ib1\ valid_lft forever preferred_lft forever 8: ib2 inet 10.149.26.140/18 brd 10.149.63.255 scope global ib2\ valid_lft forever preferred_lft forever 9: ib3 inet 10.149.26.60/18 brd 10.149.63.255 scope global ib3\ valid_lft forever preferred_lft forever 10: bond0 inet 172.17.0.160/16 brd 172.17.255.255 scope global bond0\ valid_lft forever preferred_lft forever elrtr10 ~ # lnetctl -h Try interactive use without arguments or use one of: <span class="code-quote">"lnet"</span> <span class="code-quote">"route"</span> <span class="code-quote">"net"</span> <span class="code-quote">"routing"</span> <span class="code-quote">"set"</span> <span class="code-quote">"<span class="code-keyword">import</span>"</span> <span class="code-quote">"export"</span> <span class="code-quote">"stats"</span> <span class="code-quote">"numa"</span> <span class="code-quote">"peer"</span> <span class="code-quote">"help"</span> <span class="code-quote">"exit"</span> <span class="code-quote">"quit"</span> <span class="code-quote">"--list-commands"</span> as argument. </pre> </div></div> <p>can you try this:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lnetctl lnet configure lnetctl net add --net o2ib --<span class="code-keyword">if</span> ib0 </pre> </div></div> <p>If you're bringing up lnet using</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lctl net up </pre> </div></div> <p>then you'll need to run </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">lnetctl lnet configure </pre> </div></div> <p>before you're able to use the rest of the lnetctl commands.</p> <p>In the future, it'll be a good idea to use lnetctl utility for everything:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">modprobe lnet lnetctl lnet configure lnetctl net add --net o2ib --<span class="code-keyword">if</span> ib0,ib1 # or whatever interfaces you'd like to add # other lnetctl commands </pre> </div></div> <p>We load the lustre module and that starts everything. Here is our /etc/modprobe.d/lustre.conf</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">options ko2iblnd require_privileged_port=0 use_privileged_port=0 options ko2iblnd timeout=150 retry_count=7 map_on_demand=32 peer_credits=63 concurrent_sends=63 options ko2iblnd ntx=32768 credits=32768 fmr_pool_size=8193 #lnet options lnet networks=<span class="code-quote">"o2ib(ib0,ib1),o2ib313(ib2,ib3)"</span> forwarding=enabled #options lnet networks=<span class="code-quote">"o2ib(ib1),o2ib313(ib3)"</span> forwarding=enabled options lnet avoid_asym_router_failure=1 check_routers_before_use=1 small_router_buffers=65536 large_router_buffers=8192 options ptlrpc at_max=600 at_min=150 </pre> </div></div> <p>yes, so in that case you'll need to call "lnetctl lnet configure" otherwise you won't be able to add networks or use other lnetctl commands.</p> <p>There is a way to actually do what you're doing using the module parameters but dynamically using lnetctl. The added benefit of doing it dynamically is that you're able to assign tunables per network instead of globally. For example if you want to have map-on-demand different for different networks (this will become useful if you're using OPA and MLX for example, and you want to tune them differently on the router).</p> <p>You can put all the yaml configuration in /etc/lnet.conf and then start lnet as a service which will import that file. </p> <p>The issue was not running<br/> lnetctl lnet configure</p> <p>The documentation should be more clear to indicate this.</p> <p>i'll push a patch to the manual to clarify that.</p> <p><a href="https://review.whamcloud.com/29323" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/29323</a> </p> <p>So in reality lnetctl is not long optional. I has to be installed on a node and run at startup time. In reality lctl net no long works by itself.</p> <p>If you don't want to use MR and you configure everything from module parameters, then you don't need to use lnetctl.</p> <p>For MR and future LNet features, lnetctl will be the utility to use. no more updates will be made to lctl.</p> <p>I'm looking at modifying the makefiles to always make lnetctl and install it properly.</p> <p>Awesome. I was looking at doing the same thing. Especially since the lustre tools are also looking to use libyaml (<a href="https://jira.whamcloud.com/browse/LU-9324" title="sanity-pfl test 10 needs to reset the file system default layout" class="issue-link" data-issue-key="LU-9324"><del>LU-9324</del></a>) as well. Can you base your work on top of <a href="https://review.whamcloud.com/#/c/28752" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/28752</a>. Also a review would be nice <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/biggrin.png" height="16" width="16" align="absmiddle" alt="" border="0"/> As you can see with that patch I killed off libptlctl.a and integrated the yaml stuff into liblnetconfig so liblustreapi.so can use it for <a href="https://jira.whamcloud.com/browse/LU-9324" title="sanity-pfl test 10 needs to reset the file system default layout" class="issue-link" data-issue-key="LU-9324"><del>LU-9324</del></a>.</p> <p>The reason I would also looking at this is that I use the maloo test suite but setup lnet using lnetctl. The test suite doesn't really like that. So I was looking to make the test suite work flawlessly with lnetctl.</p> <p>Is any further work needed on this ticket or can the ticket be closed now that the manual has been updated?</p> <p>Andreas talked about pushing patches that tell the user that lctl net is obsolete. Perhaps this is the perfect ticket to push those patches under?</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/30755" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/30755</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: deprecate lctl net commands<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 37c7bb1c23bed67f07bebbe9234bbcb44647f739</p> <p>Patch pushed to make lctl net functions deprecate now that the work to make lnetctl a hard requirement has landed for lustre 2.11</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/30755/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/30755/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: deprecate lctl net commands<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 1e6bd608a89ddaa3c731102f3721b26a47c28741</p> <p>Landed for 2.11</p> <p>Minh Diep (minh.diep@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/30968" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/30968</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: deprecate lctl net commands<br/> Project: fs/lustre-release<br/> Branch: b2_10<br/> Current Patch Set: 1<br/> Commit: b7a878f82eadc21bc91fe52b873538b80f854742</p> <p>The deprecation messages are not very clear. For example, now when I run <tt>sanity.sh</tt> it reports (among other things):</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>This command has been deprecated. Plesae use 'lnetctl net show'. </pre> </div></div> <p>... but it isn't clear what <tt>This command</tt> is, so I don't even know what command to start looking for in the test scripts. It should print the command name, like:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>lctl: 'list_nids' is deprecated. Please use 'lnetctl net show'. </pre> </div></div> <p>Please fix typo <tt>Plesae</tt> in error message as well.</p> <p>Also, use of the deprecated commands like "<tt>lctl list_nids</tt>" by the test scripts should be replaced by "<tt>lnetctl net show</tt>", and equivalent for "<tt>lctl network</tt>" and "<tt>lctl ping</tt>". It looks like <tt>lnetctl</tt> has existed since version <tt>v2_6_54_0-13-g0f753ea</tt> so this should be safe to land for master (we test 2.11 interop against 2.7, but no longer against 2.5).</p> <p>Andreas, beside fixing the deprecated message are you suggesting we also change lctl usage to lnetctl usage in the test scripts as part of this ticket?</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/31030" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31030</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: clarify lctl deprecation message<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 410c34ffb78be293804b39d2bd75129b67a4a309</p> <p>Amir Shehata (amir.shehata@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/31031" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31031</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> tests: replace lctl with lnetctl for lnet<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: bf6785279267934826457b3051e5ea8ca8734634</p> <p>chatted with <a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=jhammond" class="user-hover" rel="jhammond">jhammond</a> regarding the deprecation and he thinks that deprecating list_nids is going to cause trouble for the customer. We wanted to get some feedback on whether we should remove list_nids from the set of commands being deprecated.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/31030/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31030/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: clarify lctl deprecation message<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 73867ddf0c34d5e702ee4dcda850cf974bdb33da</p> <p>I think the deprecation warnings should be removed entirely.</p> <p>In order for that to happen lctl would have to work again. The changes to the LNet layer for multirail support broke the lctl net functionality. Also the current lnetctl tools don't work with pre-2.10 version as a side note.</p> <p>John L. Hammond (john.hammond@intel.com) uploaded a new patch: <a href="https://review.whamcloud.com/31534" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31534</a><br/> Subject: <del><a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a></del> lnet: remove lctl deprecation messages<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 5009ae1fdc2110a4251a57b58bbbb82663f2edab</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="https://review.whamcloud.com/31534/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/31534/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: remove lctl deprecation messages<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 423bdae48e1a0ed602f524ba41a2c83c67f4716a</p> <p>this can be closed</p> <p>I think that this ticket had been kept open because  <a href="https://review.whamcloud.com/#/c/31031/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/31031/</a> has not landed yet. Is this still needed? If so, let's reopen the ticket and rebase the patch to get it landed, if not let's abandon the patch</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/48814" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/48814</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: use Netlink to support old and new NI APIs.<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: ca490c04254a8b345a5ef4ea6037dd082edd8344</p> <p>Using this ticket to unify the MR and preMR APIs. We can kill off the old ioctls and keep the lctl LNet functionality since it will never go away</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/48814/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/48814/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: use Netlink to support old and new NI APIs.<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 8f8f6e2f36e56e53e38447583a08b7794f156c47</p> <p>More patches to go.</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/49068" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/49068</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: to properly handle errors reported use ssize_t<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: e0f25c6fec1c5fdfcc9005407f7c06f5529a879f</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/49068/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/49068/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: to properly handle errors reported use ssize_t<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 3737b28a9d014a0d0cf6a072f874990e771e06a3</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/49360" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/49360</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: use Netlink to support LNet ping commands<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: c9e8f052bcf896a07e440f383a104b5006dcaf71</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/49360/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/49360/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: use Netlink to support LNet ping commands<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: d137e9823ca1e97fccee59913d5a7bf1891b825a</p> <p>More work left.</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/50440" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/50440</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> utils: migrate old route API to Netlink / YAML API<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 10e1e556bc07546d79e0c41e319dce60c58bb304</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/50440/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/50440/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: migrate old route API to Netlink / YAML API<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 8b51c333716adade3c89b10fedbe2ca1851e027c</p> <p>"James Simmons &lt;jsimmons@infradead.org&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53556" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53556</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: implement Netlink version of lnet distance API.<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 7f98f120831eee86b5657966774061d3321abf3c</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53556/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53556/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: implement Netlink version of lnet distance API.<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: b62c385e180fbdf85533e334fa63d6b9c6bb2452</p> <p>"Chris Horn &lt;chris.horn@hpe.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/53835" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/53835</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-10003" title="lnetctl error &quot;cannot add network: invalid argument&quot;" class="issue-link" data-issue-key="LU-10003">LU-10003</a> lnet: Update lctl ping to work with large NIDs<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: dc0098e601cb613a87946548a2ffa5a8f4d4e2c0</p> Related LUDOC-392 LU-10391 LU-5960 LU-9680 LU-16307 LU-10556 LU-16462 LU-10790 Development Rank 1|hzzke7: Rank (Obsolete) 9223372036854775807 Severity