Lustre 1.6 Operations Manual

Important: All old (pre v.1.4.6) Lustre configuration lines should be removed from
the module configuration files and replaced with the following. Make sure that
CONFIG_KMOD is set in your linux.config so LNET can load the following modules
it needs. The basic module files are:
modprobe.conf (for Linux 2.6)
alias lustre llite
options lnet networks=tcp0,elan0
modules.conf (for Linux 2.4)
alias lustre llite
options lnet networks=tcp0,elan0
For the following parameters, default option settings are shown in parenthesis.
Changes to parameters marked with a W affect running systems. (Unmarked
parameters can only be set when LNET loads for the first time.) Changes to
parameters marked with Wc only have effect when connections are established
(existing connections are not affected by these changes.)
31.2 Module Options
■
■
■
■
■
With routed or other multi-network configurations, use ip2nets rather than
networks, so all nodes can use the same configuration.
For a routed network, use the same “routes” configuration everywhere. Nodes
specified as routers automatically enable forwarding and any routes that are not
relevant to a particular node are ignored. Keep a common configuration to
guarantee that all nodes have consistent routing tables.
A separate modprobe.conf.lnet included from modprobe.conf makes distributing
the configuration much easier.
If you set config_on_load=1, LNET starts at modprobe time rather than
waiting for Lustre to start. This ensures routers start working at module load
time.
# lctl
# lctl> net down
Remember lctl ping – it is a handy way to check your LNET configuration.
31-2 Lustre 1.6 Operations Manual • September 2008