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-11460 Lustre <p>Node A</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> [root@trevis-402 ~]# lnetctl net show net:     - net type: lo       local NI(s):         - nid: 0@lo           status: up     - net type: tcp       local NI(s):         - nid: 10.9.10.2@tcp           status: up           interfaces:               0: eth0 [root@trevis-402 ~]# lnetctl peer show peer:     - primary nid: 10.9.11.3@tcp       Multi-Rail: True       peer ni:         - nid: 10.9.11.3@tcp           state: NA         - nid: 10.9.10.3@tcp           state: NA     - primary nid: 10.9.10.2@tcp       Multi-Rail: True       peer ni:         - nid: 10.9.10.2@tcp           state: NA</pre> </div></div> <p> </p> <p>Node B</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> [root@trevis-403 ~]# lnetctl net show net:     - net type: lo       local NI(s):         - nid: 0@lo           status: up     - net type: tcp       local NI(s):         - nid: 10.9.10.3@tcp           status: up           interfaces:               0: eth0         - nid: 10.9.11.3@tcp           status: up           interfaces:               0: eth1 </pre> </div></div> <p> </p> <p>Now delete the 'eth1' interface on Node B, so configuration looks like this -</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> [root@trevis-403 ~]# lnetctl net show net:     - net type: lo       local NI(s):         - nid: 0@lo           status: up     - net type: tcp       local NI(s):         - nid: 10.9.10.3@tcp           status: up           interfaces:               0: eth0 </pre> </div></div> <p> </p> <p>After this step, if we try to ping from Node A to Node B,</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> [root@trevis-402 ~]# lnetctl ping 10.9.11.3@tcp manage:     - ping:           errno: -1           descr: failed to ping 10.9.11.3@tcp: Input/output error                   [root@trevis-402 ~]# lnetctl ping 10.9.11.3@tcp ping:     - primary nid: 10.9.11.3@tcp       Multi-Rail: True       peer ni:         - nid: 10.9.10.3@tcp [root@trevis-402 ~]# lnetctl ping 10.9.11.3@tcp manage:     - ping:           errno: -1           descr: failed to ping 10.9.11.3@tcp: Input/output error                   [root@trevis-402 ~]# lnetctl ping 10.9.11.3@tcp ping:     - primary nid: 10.9.11.3@tcp       Multi-Rail: True       peer ni:         - nid: 10.9.10.3@tcp </pre> </div></div> LU-11460

lnetctl ping giving unexpected output

Bug Major Closed Not a Bug Amir Shehata Sonia Sharma Tue, 2 Oct 2018 22:31:56 +0000 Thu, 4 Oct 2018 22:21:05 +0000 Thu, 4 Oct 2018 22:21:05 +0000 Lustre 2.11.0 0 2 <p>I think the issue is in</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> lnet_peer_del_nid() 485 »·······/* 486 »······· * This function only allows deletion of the primary NID <span class="code-keyword">if</span> it 487 »······· * is the only NID. 488 »······· */ 489 »·······<span class="code-keyword">if</span> (nid == lp-&gt;lp_primary_nid &amp;&amp; lp-&gt;lp_nnis != 1) { 490 »·······»·······rc = -EBUSY; 491 »·······»·······<span class="code-keyword">goto</span> out; 492 »·······} </pre> </div></div> <p>With discovery, updated peer information is sent via PUSH message but if the interface that is brought down is the primary_nid then the peer information cannot be updated. This is because the primary_nid cannot be deleted/updated as the upper layers rely on the intially configured primary_nid</p> Development Rank 1|i003g7: Rank (Obsolete) 9223372036854775807 Severity