23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

32.5.12 lst<br />

The lst utility starts LNET self-test.<br />

Synopsis<br />

lst<br />

Description<br />

LNET self-test helps site administrators confirm that <strong>Lustre</strong> Networking (LNET) has<br />

been correctly installed and configured. The self-test also confirms that LNET, the<br />

network software and the underlying hardware are performing as expected.<br />

Each LNET self-test runs in the context of a session. A node can be associated with<br />

only one session at a time, to ensure that the session has exclusive use of the nodes<br />

on which it is running. A single node creates, controls and monitors a single session.<br />

This node is referred to as the self-test console.<br />

Any node may act as the self-test console. Nodes are named and allocated to a selftest<br />

session in groups. This allows all nodes in a group to be referenced by a single<br />

name.<br />

Test configurations are built by describing and running test batches. A test batch is a<br />

named collection of tests, with each test composed of a number of individual pointto-point<br />

tests running in parallel. These individual point-to-point tests are<br />

instantiated according to the test type, source group, target group and distribution<br />

specified when the test is added to the test batch.<br />

Modules<br />

To run LNET self-test, load following modules: libcfs, lnet, lnet_selftest and any one<br />

of the klnds (ksocklnd, ko2iblnd...). To load all necessary modules, run modprobe<br />

lnet_selftest, which recursively loads the modules on which lnet_selftest depends.<br />

There are two types of nodes for LNET self-test: console and test. Both node types<br />

require all previously-specified modules to be loaded. (The userspace test node does<br />

not require these modules).<br />

Test nodes can either be in kernel or in userspace. A console user can invite a kernel<br />

test node to join the test session by running lst add_group NID, but the user cannot<br />

actively add a userspace test node to the test-session. However, the console user can<br />

passively accept a test node to the test session while the test node runs lst client to<br />

connect to the console.<br />

Utilities<br />

Chapter 32 System Configuration Utilities (man8) 32-27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!