Details
-
Bug
-
Resolution: Fixed
-
Critical
-
Lustre 2.7.0
-
None
-
lustre-b2_7 build #29
-
3
-
17752
Description
After running /etc/rc.d/init.d/lnet start, it doesn't configure lnet exactly as defined in /etc/sysconf/lnet.conf. Router is missing, net are not the exact same.
This is a minor issue, Amir has suggested 1 line change can fix this problem .
the lnet.conf looks like
[root@eagle-54vm3 modprobe.d]# more /etc/sysconfig/lnet.conf
net:
- net: lo
nid: 0@lo
status: up
tunables:
peer_timeout: 0
peer_credits: 0
peer_buffer_credits: 0
credits: 0
- net: tcp1
nid: 192.168.201.180@tcp1
status: up
interfaces:
0: eth1
tunables:
peer_timeout: 181
peer_credits: 8
peer_buffer_credits: 0
credits: 256
route:
- net: tcp
gateway: 192.168.201.101@tcp1
hop: 1
priority: 0
state: up
[root@eagle-54vm3 modprobe.d]#
after running lnet start check the system
[root@eagle-54vm3 modprobe.d]# lnetctl net show -v
net:
- net: lo
nid: 0@lo
status: up
tunables:
peer_timeout: 0
peer_credits: 0
peer_buffer_credits: 0
credits: 0
- net: tcp
nid: 10.100.4.198@tcp
status: up
tunables:
peer_timeout: 180
peer_credits: 8
peer_buffer_credits: 0
credits: 256
- net: tcp1
nid: 192.168.201.180@tcp1
status: up
interfaces:
0: eth1
tunables:
peer_timeout: 181
peer_credits: 8
peer_buffer_credits: 0
credits: 256
[root@eagle-54vm3 modprobe.d]# lnetctl route show -v
[root@eagle-54vm3 modprobe.d]#
