[lustre-discuss] lnetctl --ip2net configures first interface

Jesse Stroik jesse.stroik at ssec.wisc.edu
Wed Mar 21 09:45:56 PDT 2018


For newer lustre client systems, I've begun using lustre 2.10.x. Dynamic 
lnet configuration is very helpful and it saves a lot of trouble in our 
environment. However, I've noticed that when using ip2net, lnetctl will 
assign the first interface available when that doesn't seem to be its 
intended behavior.

Example:

=======
[root at c7test etc]# lctl list_nids 
 

[root at c7test etc]# lnetctl net add --ip2net "tcp0 128.104.109.*" 
 

[root at c7test etc]# lctl list_nids 
 

192.168.1.5 at tcp
=======

The system in question has three interfaces, two of which are assigned 
IP addresses. ens224 is 192.168.1.5/24 and ens256 is 128.104.109.161/22.

Best,
Jesse Stroik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3964 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20180321/1ca7e6fc/attachment.bin>


More information about the lustre-discuss mailing list