Details
-
Bug
-
Resolution: Not a Bug
-
Minor
-
None
-
Lustre 2.5.0
-
None
-
server and client: lustre-master build #1627
-
3
-
9933
Description
According to the test plan attached on LU-2934, lnet route priority > 1 is not allowed, but there is no error message and it can be set > 1
[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
Attachments
Issue Links
- is related to
-
LU-2934 Add LNet Router Priority Parameter
-
- Resolved
-