Thanks Sebastien,
this put all clients into the correct LNet. And nodemap.exports looks as
expected.
(Had to add 'options lnet lnet_peer_discovery_disabled=1' for ‘-o
network=’ to work).
Regards
Thomas
On 6/19/24 08:31, Sebastien Buisson wrote:
Hi,
I am not sure the NIDs displayed under ‘
Hi,
I am not sure the NIDs displayed under ‘exports’ and in the logs are the actual
NIDs used to communicate with, maybe they are just identifiers to describe the
peers.
If you want to restrict a client to a given LNet network for a given mount
point, you can use the ‘-o network=’ mount option
OK, client 247 is the good one ;-)
It is rather an LNET issue.
All three clients have:
> options lnet networks="o2ib8(ib0),o2ib6(ib0)"
I can mount my nodemapped Lustre, with its MGS on 10.20.6.63@o2ib8, and
another Lustre on o2ib6.
However, the log of the MGS at 10.20.6.63@o2ib8 remarks
> M
Hi all,
what is the meaning of the "exports" property/parameter of a nodemap?
I have
mgs ]# lctl nodemap_info newclients
...
There are three clients:
mgs # lctl get_param nodemap.newclients.ranges
nodemap.newclients.ranges=
[
{ id: 13, start_nid: 10.20.3.246@o2ib8, end_nid: 10.20.3.246@o2ib8
