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-3836 Lustre <p>According to the test plan attached on <a href="https://jira.whamcloud.com/browse/LU-2934" title="Add LNet Router Priority Parameter" class="issue-link" data-issue-key="LU-2934"><del>LU-2934</del></a>, lnet route priority &gt; 1 is not allowed, but there is no error message and it can be set &gt; 1</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[root@wtm-77 ~]# modprobe lnet LNet: HW CPU cores: 32, npartitions: 4 alg: No test for crc32 (crc32-table) alg: No test for adler32 (adler32-zlib) alg: No test for crc32 (crc32-pclmul) padlock: VIA PadLock Hash Engine not detected. [root@wtm-77 ~]# lctl network up LNet: Added LNI 10.10.18.208@tcp [8/256/0/180] LNet: Accept all, port 7988 LNET configured [root@wtm-77 ~]# cat /proc/sys/lnet/routes Routing disabled net hops priority state router o2ib 1 2 up 10.10.18.199@tcp </pre> </div></div> server and client: lustre-master build #1627 LU-3836

There is no error message when setting priority > 1 for lnet routes

Bug Minor Closed Not a Bug WC Triage Sarah Liu Mon, 26 Aug 2013 22:56:18 +0000 Tue, 27 Aug 2013 16:18:23 +0000 Tue, 27 Aug 2013 16:18:23 +0000 Lustre 2.5.0 0 3 <p>Doug, please confirm but my understanding is that the design of the router priority changed after the comments in that bug to allow a range of priorities.</p> <p>Andreas: correct. The test plan will need to be updated for this ticket.</p> Related LU-2934 Development Rank 1|hzvzb3: Rank (Obsolete) 9933 Severity