Difference between revisions of "LNet Router Config Guide2"

From Lustre Wiki
Jump to navigation Jump to search
(Redirected page to LNet Router Config Guide)
(37 intermediate revisions by the same user not shown)
Line 1: Line 1:
This document provides procedures to configure and tune an LNet router. It will also cover detailed instructions set on setting up connectivity of an Infiniband network to Intel OPA nodes using LNet router.
#REDIRECT [[LNet Router Config Guide]]
== 1. LNet ==
LNet supports different network types like Ethernet, InfiniBand, Intel Omni-Path and other proprietary network technologies such as the Cray’s Gemini. It routes LNet messages between different LNet networks using LNet routing. LNet’s routing capabilities provide an efficient protocol to enable bridging between different types of networks.
LNet is part of the Linux kernel space and allows for full RDMA throughput and zero copy communications when supported by underlying network. Lustre can initiate a multi-OST read or write using a single Remote Procedure Call (RPC), which allows the client to access data using RDMA at near peak bandwidth rates.
With Multi-Rail (MR) feature implemented in Lustre 2.10.X, it allows for multiple interfaces of same type on a node to be grouped together under the same LNet (ex tcp0, o2ib0, etc.). These interfaces can then be used simultaneously to carry LNet traffic. MR also has the ability to utilize multiple interfaces configured on different networks. For example, OPA and MLX interfaces can be grouped under their respective LNet and then can be utilized with MR feature to carry LNet traffic simultaneously.
== LNet Configuration Example ==
An LNet router is a specialized Lustre client where Lustre file system is not mounted and only the LNet is running. A single LNet router can serve different file systems.
For the above example:
* Servers are on LAN1, a Mellanox based InfiniBand network –
* Clients are LAN2, an Intel OPA network –
* Routers on LAN1 and LAN2 at, and, respectively
The network configuration on the nodes can be done either by adding the module parameters in lustre.conf
<pre> /etc/modprobe.d/lustre.conf
</pre> or dynamically by using the lnetctl command utility.
Also, current configuration can be exported to a YAML format file and then the configuration can be set by importing that YAML file anytime needed.
=== 2.1 Network Configuration by adding module parameters in lustre.conf ===
options lnet networks="o2ib1(ib0)" routes="o2ib2 [email protected]"
options lnet networks="o2ib1(ib0),o2ib2(ib1)" "forwarding=enabled"
options lnet networks="o2ib2(ib0)" routes="o2ib1 [email protected]" </nowiki>
NOTE: Restarting LNet is necessary to apply the new configuration. To do this, it is needed to unconfigure the LNet network and reconfigure again. Make sure that the Lustre network and Lustre file system are stopped prior to unloading the modules.
// To unload and load LNet module
modprobe -r lnet
modprobe lnet
// To unconfigure and reconfigure LNet
lnetctl lnet unconfigure
lnetctl lnet configure </nowiki>
=== 2.2 Dynamic Network Configuration using lnetctl command ===
lnetctl net add --net o2ib1 --if ib0
lnetctl route add --net o2ib2 --gateway [email protected]
lnetctl peer add --nid [email protected]
lnetctl net add --net o2ib1 --if ib0
lnetctl net add --net o2ib2 --if ib1
lnetctl peer add --nid [email protected]
lnetctl peer add --nid [email protected]
lnetctl set routing 1
lnetctl net add --net o2ib2 --if ib0
lnetctl route add --net o2ib1 --gateway [email protected]
lnetctl peer add --nid [email protected] </nowiki>

Latest revision as of 20:07, 12 October 2017