Lustre 1.6 Operations Manual

19.4 LNET Self-Test
LNET self-test helps site administrators confirm that Lustre Networking (LNET) has
been properly installed and configured, and that underlying network software and
hardware are performing according to expectations.
LNET self-test is a kernel module that runs over LNET and LNDs. It is designed to:
■
■
■
Test the connection ability of the Lustre network
Run regression tests of the Lustre network
Test performance of the Lustre network
19.4.1 Basic Concepts of LNET Self-Test
This section describes basic concepts of LNET self-test, utilities and a sample script.
19.4.1.1 Modules
To run LNET self-test, these modules must be loaded: libcfs, lnet, lnet_selftest and
one of the klnds (i.e, ksocklnd, ko2iblnd...). To load all necessary modules, run
modprobe lnet_selftest (recursively loads the modules on which LNET selftest
depends.
The LNET self-test cluster has two types of nodes:
■ Console node - A single node that controls and monitors the test cluster. It can be
any node in the test cluster.
■ Test nodes - The nodes that run tests. Test nodes are controlled by the user via the
console node; the user does not need to log into them directly.
The console and test nodes require all previously-listed modules to be loaded. (The
userspace test node does not require these modules.)
Note – Test nodes can be in either kernel or userspace. A console user can invite a
kernel test node to join the test session by running lst add_group NID, but the
user cannot actively add a userspace test node to the test-session. However, the
console user can passively accept a test node to the test session while the test node
runs lstclient to connect to the console.
Chapter 19 Lustre I/O Kit 19-17