[lustre-discuss] Lustre Client pinned to use specific NIC on host

[Tim Schnedler]

One way to do this is to make a lustre conf file in etc/ modprobe.d

On Fri, Oct 3, 2025 at 12:48 PM Sonia Sharma via lustre-discuss <
lustre-discuss at lists.lustre.org> wrote:

> Hello Dear Lustre Community
>
> I was wondering if there is some setting/way to make a Lustre Client use
> only a specific NIC to route its LNet messages from even when multiple NICs
> on that host are configured with the same LNet network.
>
> For example, let’s say I have a host with this below LNet configuration,
> then is there a way that I can have the Lustre client to use only “
> *10.30.201.26 at tcp*” for all its communication
>
> *[node1]# lnetctl net show*
> *net:*
> *    - net type: lo*
> *      local NI(s):*
> *        - nid: 0 at lo*
> *          status: up*
> *    - net type: tcp*
> *      local NI(s):*
> *        - nid: 10.30.201.26 at tcp*
> *          status: up*
> *          interfaces:*
> *              0: enp1s0*
> *        - nid: 10.30.201.10 at tcp*
> *          status: up*
> *          interfaces:*
> *              0: enp1s0:10269*
> *        - nid: 10.30.202.241 at tcp*
> *          status: up*
> *          interfaces:*
> *              0: enp1s0:10257*
>
> Best regards
> Sonia
>
> Confidential – Oracle Internal
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20251003/b4f766f0/attachment-0001.htm>