[LUDOC-364] Update description of "lctl get_param nis" in Lustre manual Created: 12/Feb/17  Updated: 03/Nov/20

Status: Open
Project: Lustre Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Malcolm Cowe (Inactive) Assignee: Lustre Manual Triage
Resolution: Unresolved Votes: 0
Labels: None

Rank (Obsolete): 9223372036854775807

 Description   

The output from the command lctl get_param nis in current versions of Lustre does not match the description in the Lustre manual. New fields have been added to the ouput that have not been documented.

The manual currently has the following example output with a tabel afterwards describing each column:

# lctl get_param nis
nid                    refs   peer    max   tx    min
0@lo                   3      0       0     0     0
192.168.10.34@tcp      4      8       256   256   252

By contrast, Lustre version 2.7 has the following output:

[root@ct7-mds2 ~]# lctl get_param nis
nis=nid                      status alive refs peer  rtr   max    tx   min
0@lo                         up     0    3    0    0     0     0     0
192.168.2.12@tcp             up    -1    4    8    0   256   256   251

The columns status, alive and rtr are not documented.

 



 Comments   
Comment by Nathan Rutman [ 03/Nov/20 ]

FWIW, there also seems to be an entry per CPT, but there is no column showing which CPT the line is for.

cdslmo103:~ # lctl get_param -n nis
nid                      status alive refs peer  rtr   max    tx   min
0@lo                       down     0    2    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
0@lo                       down     0    0    0    0     0     0     0
172.18.1.63@o2ib             up    -1    1    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    56
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    56
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    56
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    56
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    61
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    56
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
172.18.1.63@o2ib             up    -1    0    8    0    64    64    64
Generated at Sat Feb 10 03:42:20 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.