Lustre 1.6 Operations Manual

5.2 Configuring Your Lustre Network
This section describes how to configure your Lustre network.
Note – We recommend that you use dotted-quad IP addressing rather than host
names. We have found this aids in reading debug logs, and helps greatly when
debugging configurations with multiple interfaces.
5.2.1 Module Parameters
LNET network hardware and routing are configured via module parameters of the
LNET and LND-specific modules. Parameters should be specified in the
/etc/modprobe.conf or /etc/modules.conf file, for example:
options lnet networks=tcp0,elan0
This specifies that this node should use all available TCP and Elan interfaces.
All LNET routers that bridge two networks are equivalent. Their configuration is not
primary or secondary. All available routers balance their overall load. Router fault
tolerance only works from Linux nodes. For this, LNET routing must correspond
exactly with the Linux nodes' map of alive routers. There is no hard limit on the
number of LNET routers.
Note – When multiple interfaces are available during the network setup, Lustre
choose the 'best' route. Once the network connection is established, Lustre expects
the network to stay connected. In a Lustre network, connections do not fail over to
the other interface, even if multiple interfaces are available on the same node.
■
■
Under Linux 2.6, the LNET configuration parameters can be viewed under
/sys/module/; generic and acceptor parameters under lnet and LND-specific
parameters under the corresponding LND name.
Under Linux 2.4, sysfs is not available, but the LND-specific parameters are
accessible via equivalent paths under /proc.
5-4 Lustre 1.7 Operations Manual • September 2008