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-5960 Lustre <p>The lnetctl utility added the ability get get new information such as peer credits. What is still lacking is gathering details about peers and connections. This work adds this functionality</p> LU-5960

Add ability to get peer and connection information from lnetctl

Improvement Minor Open Unresolved James A Simmons James A Simmons lnet Wed, 26 Nov 2014 15:58:05 +0000 Thu, 10 Nov 2022 16:39:33 +0000 Lustre 2.8.0 0 5 <p>Patch at <a href="http://review.whamcloud.com/#/c/8027" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/8027</a>. This is not the final patch but something for feed back. Currently the peer information works well but connection data is currently not working. Need to add man pages and docs for this.</p> <p>Amir</p> <p>Could you please review this initial patch</p> <p>Thanks</p> <p>Peter</p> <p>The patch is now in a form that is useful. I like to have feedback from people about the format of lnetctl peers show and conns show commands. Of course code review is welcomed.</p> <p><a href="http://review.whamcloud.com/#/c/8027" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/8027</a></p> <p>Updated this work for 2.9. I have increased the scope of this patch with the goal of lnetctl having the functionality missing from lctl. As a bonus I added new features to those class functions such as filtering the results based on NID, PID or LNet type. So you could say list<br/> peers for o2ib3 only or another example is listing peers which use PID 5463 instead of the standard lustre PID of 12345.</p> <p>Updated the patch again. This time I added a new feature which is if a hostname exist for a IP the lnetctl tools can display the hostname instead of the IP. Should we make that optional? Also currently it displays hostname.domainname@nettype. Would admins prefer a hostname@netype as the default?</p> <p>James, I think if we do that we should make this feature symmetrical. The intention is to use the YAML output from show commands to be fed directly into YAML configuration. So all YAML config APIs should be able to take a hostname.domainname@nettype and convert that into &lt;ip&gt;@nettype before sending to the Kernel.</p> <p>I also think we should stick with the shortest non-ambiguous form. Can two nodes be on different domains and have the same hostname? If so (which I think is a possible setting) then we should stick with hostname.domainname@nettype.</p> <p>Please note that this is being done under the sysfs project: <a href="https://jira.whamcloud.com/browse/LU-9667" title="LNet Kernel/Userspace Interface" class="issue-link" data-issue-key="LU-9667">LU-9667</a></p> Related LU-9667 LU-7734 LU-9119 LU-10003 LU-5881 LU-7245 Development End date Wed, 28 Oct 2015 15:58:05 +0000 Project Rank 1|hzx1lj: Rank (Obsolete) 16644 Start date Wed, 26 Nov 2014 15:58:05 +0000