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@c7test etc]# lctl list_nids

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

[root@c7test etc]# lctl list_nids

192.168.1.5@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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to