I’m not sure why lnetctl import wouldn’t correctly set discovery. Might be a
bug. You can try setting the kernel module parameter to disable discovery:
options lnet lnet_peer_discovery_disabled=1
This obviously requires LNet to be reloaded.
I would not recommend toggling discovery via the CLI
I supposed you removed the /etc/modprobe.d/lustre.conf completely.
I only have the lnet service enabled at startup, I do not start any
lustre3 service, but I am running lustre 2.12.0 sorry not 2.14
so something might be different.
Did you start over with a clean configuration ?
Did you
Thanks Rick. I removed my lnet modprobe options and adapted my lnet.conf file
to:
# cat /etc/lnet.conf
ip2nets:
- net-spec: o2ib1
interfaces:
0: ib0
global:
discovery: 0
#
Now "lnetctl export" doesn't have any reference to NIDs on the other networks,
so that's good. However,
I would use configuration on /etc/lnet.conf and I would not use anymore
the older style configuration in
/etc/modprobe.d/lustre.conf
for example in my /etc/lnet.conf configuration I have:
*ip2nets:
- net-spec: o2ib
interfaces:
0: ib0
- net-spec: tcp
interfaces:
0:
Hello,
I would like to know how to turn off auto discovery of peers on a client. This
seems like it should be straight forward but we can't get it to work. Please
fill me in on what I'm missing.
We recently upgraded our servers to 2.14. Our servers are multi-homed (1 tcp
network and 2
