John,
> > Otherwise, lustre chooses a NID by asking LNET what the network "distance"
> > to all the server's NIDs are, and picks the "best" one as follows...
> >
> > 1. Compare hop counts. The NID that is reached by traversing fewer routers
> > wins.
>
> Presumably that means lnet routers, not IP ones or anything else, correct?
Yes.
> > 2. Compare rank. Find the local network that you must send on to reach the
> > given NID and compare the order in which the these networks appear in the
> > "networks" or "ip2nets" module parameter. The local network listed first
> > wins.
>
> Ah. I guess I didn't realize that it had that much awareness of topology,
> but I suppose it needs to, doesn't it? I guess I should go read up on those
> module parms.
Please holler if it's not clear in the documentation.
> At startup time, is it as simple as making sure all the right modules are
> loaded, and that the NID name in the mount command gets correctly parsed?
You can debug connectivity before trying any lustre stuff...
1. Get LNET running on relevent nodes: modprobe lnet && lctl net up
2. lctl ping <NID>
> So for instance, if I've got some external hosts accessable over socklnd as
>
> # mount -t lustre my-server:/lustrefs /mnt/external-lustre
>
> and some internal nodes as well, can I just say something like
>
> # mount -t lustre SC!123:/lustrefs /mnt/internal-lustre
>
> as long as my custom lnd will turn "SC!123" into an internal NID?
I think "my-server" really means "[EMAIL PROTECTED]" because the network type
of a NID defaults to "tcp" and the network number defaults to "0".
If the new network type your LND implements is "sc", then you should be able to
say...
# mount -t lustre [EMAIL PROTECTED]:/lustrefs /mnt/internal-lustre
Note that all the string/NID conversion stuff is in
<lustre>/lnet/libcfs/nidstrings.c
Cheers,
Eric
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
