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-16836 Lustre <p>Adding NI if the corresponding interface is disconnected results in NI listed as "up" while it is expected to be "down". For example:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> 7: bond0: &lt;NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP&gt; mtu 1500 qdisc noqueue state DOWN group <span class="code-keyword">default</span> qlen 1000     link/ether 52:54:00:a3:1a:44 brd ff:ff:ff:ff:ff:ff     inet 192.168.122.239/24 brd 192.168.122.255 scope global noprefixroute dynamic bond0        valid_lft 3264sec preferred_lft 3264sec     inet6 fe80::5054:ff:fea3:1a44/64 scope link         valid_lft forever preferred_lft forever</pre> </div></div> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> # lnetctl net add --net tcp --<span class="code-keyword">if</span> bond0 # lnetctl net show net:     - net type: lo       local NI(s):         - nid: 0@lo           status: up     - net type: tcp       local NI(s):         - nid: 192.168.122.239@tcp           status: up           interfaces:               0: bond0</pre> </div></div> <p> </p> LU-16836

LNet: initial ni status is "up" if starting with link disconnected

Bug Minor Resolved Fixed Serguei Smirnov Serguei Smirnov ksocklnd lnet o2iblnd Thu, 18 May 2023 20:10:58 +0000 Sun, 29 Oct 2023 15:34:28 +0000 Wed, 28 Jun 2023 22:49:45 +0000 Lustre 2.16.0 0 4 <p>The issue here is that LNet may be able to initialize the LND, but doesn't get the link status update so it is not notified that the link is down. The new NI is then stuck with the "up" status until an event occurs which refreshes it, e.g plugging/unplugging the cable, etc.</p> <p>Here are the cases when this can happen:</p> <ul> <li>Cable is disconnected from the interface (socklnd, o2iblnd)</li> <li>All slave links of a bonded interface are down (the example from the ticket description). The links may be "administered" to be down, so the bond interface will be considered down, but still retain the IP and thus enable the LND to be initialized.</li> </ul> <p>Except with the slave bonded links as shown above, "ifdown" and "ip link set dev &lt;if&gt; down" commands don't appear to be useful for simulating this issue.</p> <p>"Serguei Smirnov &lt;ssmirnov@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/c/fs/lustre-release/+/51057" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/51057</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16836" title="LNet: initial ni status is &quot;up&quot; if starting with link disconnected" class="issue-link" data-issue-key="LU-16836"><del>LU-16836</del></a> lnet: ensure dev notification on lnd startup<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: fcb6d8de5eb5519d3eafd123719427c21ba0d6da</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/fs/lustre-release/+/51057/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/fs/lustre-release/+/51057/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-16836" title="LNet: initial ni status is &quot;up&quot; if starting with link disconnected" class="issue-link" data-issue-key="LU-16836"><del>LU-16836</del></a> lnet: ensure dev notification on lnd startup<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 09c6e2b872287c847d15620788f6cf50b3a9f30b</p> <p>Landed for 2.16</p> Related LU-17235 Development Rank 1|i03ltj: Rank (Obsolete) 9223372036854775807 Severity