Options for Lustre kernel modulesB–4
• Two (non-bonded) Gigabit Ethernet interconnects, which the client node uses to access two different
HP SFS systems. One of the HP SFS systems is configured with a dual Gigabit Ethernet interconnect;
the second HP SFS system is configured with a single Gigabit Ethernet interconnect. The client node
accesses only HP SFS Version 2.2 servers that are not running in Portals compatibility mode:
options lnet network=tcp0(eth1,eth2),tcp1(eth1) portals_compatibility=none
Section B.2.1 provides instructions for testing the options lnet settings in the configuration files.
B.2.1 Testing the options lnet settings
You can use the lctl ping command to test the options lnet settings in the /etc/modprobe.conf
or the /etc/modules.conf files by attempting to connect to a server where a specific Lustre file system’s
services are running. However, note the following constraints:
• There must be no Lustre file system mounted on the node where you are performing the connectivity
test.
• In cases where a Quadrics interconnect is used, you cannot use the lctl ping command to test
connectivity.
To test connectivity to a specific Lustre file system, perform the following steps:
1. Make sure that the file system is started on the HP SFS server. Use the sfsmgr show filesystem
command on a server in the HP SFS system to view the state of the file systems.
2. Load the lnet module on the client node, as follows:
# modprobe lnet
3. Initialize all networks, by entering the following command:
# lctl net up
LNET configured
#
4. Determine the NID of an appropriate server for use in the connectivity test, as follows:
a. The server that the client node attempts to contact must be actively serving the file system’s
services; you can determine which servers are running a file system’s services by entering the
show filesystem filesystem_name command (on a server in the HP SFS system), as
shown in the following example. In this example, the south2, south3, or south4 servers
could be used in the connectivity test, because they are all running services in the data file
system:
sfs> show filesystem data
.
.
.
MDS Information:
Name LUN Array Controller Files Used Service State Running on
----- --- ----- ---------- -------- ---- ------------- ----------
mds6 6 1 scsi-1/1 469M 0% running south2
OST Information:
Name LUN Array Controller Size(GB) Used Service State Running on
----- --- ----- ---------- -------- ---- ------------- ----------
ost6 11 3 scsi-1/1 2048 14% running south3
ost7 11 4 scsi-2/1 2048 14% running south4
ost8 11 5 scsi-3/1 2048 14% running south3
ost9 11 6 scsi-4/1 2048 14% running south4
Kommentare zu diesen Handbüchern