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/LUDOC-494 Lustre Documentation <p>In a discussion on <a href="https://review.whamcloud.com/#/c/43127/," class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/43127/,</a> in response to:</p> <blockquote><p>Note that bit of code is requiring that hop count be set for some routes, when they did not need to be set before (in lustre 2.12)</p></blockquote> <p>Chris said:</p> <p>"Yes, good point. I think there was always an implicit requirement that hop count be set for multi-hop routes if the avoid_asym_route_failure feature was enabled, but we should make that explicit."</p> <p>However this isn't reflected in the manual or lnetctl(8). (yet)</p> <p> </p> LUDOC-494

Clarify when setting lnet route hops is required for Lustre 2.12 and Lustre 2.14

Bug Minor Open Unresolved Serguei Smirnov Olaf Faaland Thu, 29 Jul 2021 18:53:30 +0000 Tue, 8 Aug 2023 22:00:16 +0000 0 5 <p>Related to <a href="https://jira.whamcloud.com/browse/LU-14555" class="external-link" rel="nofollow">https://jira.whamcloud.com/browse/LU-14555</a></p> <p>Serguei</p> <p>Could you please advise on what changes should be made to the manual here?</p> <p>Thanks</p> <p>Peter</p> <p>Hi,</p> <p>I reviewed the current related documentation, listed below are the recommended changes:</p> <p>The lnetctl section of the Lustre manual and lnetctl man page should be updated to mention that the hop count defaults to 1 if not specified when adding a route with lnetctl.</p> <p>Also, the manual should be updated to clarify that "avoid_asym_route_failure" module parameter applies only to single-hop routers. </p> <p>Also, the following passage from 34.3.7. LNet Peer Health should be modified: </p> <p><cite>"A router is considered down if any of its NIDs are down. For example, router X has three NIDs: <tt>Xnid1</tt>, <tt>Xnid2</tt>, and <tt>Xnid3</tt>. A client is connected to the router via <tt>Xnid1</tt>. The client has router checker enabled. The router checker periodically sends a ping to the router via <tt>Xnid1</tt>. The router responds to the ping with the status of each of its NIDs. In this case, it responds with <tt>Xnid1=up</tt>, <tt>Xnid2=up</tt>, <tt>Xnid3=down</tt>. If <tt>avoid_asym_router_failure==1</tt>, the router is considered down if any of its NIDs are down, so router X is considered down and will not be used for routing messages. If <tt>avoid_asym_router_failure==0</tt></cite><cite>, router X will continue to be used for routing messages."</cite>  </p> <p>The above sounds incorrect to me now, because the router shouldn't be considered down unless it cannot reach remote net.</p> <p>Thanks,</p> <p>Serguei.</p> <p> </p> <p>Hi Serguei,</p> <p>We'll be happy to review the patches.</p> <p>Thanks</p> <p>"Serguei Smirnov &lt;ssmirnov@whamcloud.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/44916" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/44916</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LUDOC-494" title="Clarify when setting lnet route hops is required for Lustre 2.12 and Lustre 2.14" class="issue-link" data-issue-key="LUDOC-494">LUDOC-494</a> lnet: clarify use of route hopcount<br/> Project: doc/manual<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 48588c2fcdc74e48caca530f7e38f3036143ea95</p> <p>"Andreas Dilger &lt;adilger@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/c/doc/manual/+/44916/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/c/doc/manual/+/44916/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LUDOC-494" title="Clarify when setting lnet route hops is required for Lustre 2.12 and Lustre 2.14" class="issue-link" data-issue-key="LUDOC-494">LUDOC-494</a> lnet: clarify use of route hopcount<br/> Project: doc/manual<br/> Branch: master<br/> Current Patch Set: <br/> Commit: f7da09ba79b2522ca51d001c59ab1212d051309c</p> Related Development Rank 1|i020iv: Rank (Obsolete) 9223372036854775807 Severity