ceive
> counts for each interface on your client and server to ensure that
> traffic is being spread across them.
>
> Chris Horn
>
> From:lustre-discuss on
> behalf of Gwen Dawes via lustre-discuss
>
> Date: Wednesday, January 17, 2024 at 5:48 AM
> To: lustre-di
>
> Chris Horn
>
> From:lustre-discuss on
> behalf of Gwen Dawes via lustre-discuss
>
> Date: Wednesday, January 17, 2024 at 5:48 AM
> To: lustre-discuss@lists.lustre.org
> Subject: Re: [lustre-discuss] LNet Multi-Rail config - with BODY!
> Hi Andreas,
>
> Th
Date: Wednesday, January 17, 2024 at 5:48 AM
To: lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] LNet Multi-Rail config - with BODY!
Hi Andreas,
Thanks for the pointer. I have a second server set up running 2.15.3 as
well specifically to check this, and can set it up
Hi Andreas,
Thanks for the pointer. I have a second server set up running 2.15.3 as
well specifically to check this, and can set it up with lnet_selftest,
same as the client. After taking a bit to convince the fabric manager
to accept the moved IPs, I get the exact same results between the two.
Hello Gwen,
I'm not a networking expert, but it seems entirely possible that the MR
discovery in 2.12.9
isn't doing as well as what is in 2.15.3 (or 2.15.4 for that matter). It would
make more sense
to have both nodes running the same (newer) version before digging too deeply
into this.
We
