1 <?xml version='1.0' encoding='UTF-8'?>
2 <chapter xmlns="http://docbook.org/ns/docbook"
3 xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
4 xml:id="understandinglustrenetworking">
5 <title xml:id="understandinglustrenetworking.title">Understanding Lustre Networking (LNet)</title>
6 <para>This chapter introduces Lustre networking (LNet). It includes the following sections:</para>
10 <xref linkend="understanding_lnet"/>
15 <xref linkend="lnet_key_feature"/>
19 <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="idp694976"/></para>
23 <xref linkend="supported_networks"/>
27 <section xml:id="understanding_lnet">
29 <primary>LNet</primary>
30 </indexterm><indexterm>
31 <primary>LNet</primary>
32 <secondary>understanding</secondary>
33 </indexterm> Introducing LNet</title>
34 <para>In a cluster using one or more Lustre file systems, the network communication
35 infrastructure required by the Lustre file system is implemented using the Lustre networking
36 (LNet) feature.</para>
37 <para>LNet supports many commonly-used network types, such as InfiniBand and IP networks, and
38 allows simultaneous availability across multiple network types with routing between them.
39 Remote direct memory access (RDMA) is permitted when supported by underlying networks using
40 the appropriate Lustre network driver (LND). High availability and recovery features enable
41 transparent recovery in conjunction with failover servers.</para>
42 <para>An LND is a pluggable driver that provides support for a particular network type, for
43 example <literal>ksocklnd</literal> is the driver which implements the TCP Socket LND that
44 supports TCP networks. LNDs are loaded into the driver stack, with one LND for each network
46 <para>For information about configuring LNet, see <xref linkend="configuringlnet"/>.</para>
47 <para>For information about administering LNet, see <xref linkend="adminlustrepart3"/>.</para>
49 <section xml:id="lnet_key_feature">
51 <primary>LNet</primary>
52 <secondary>features</secondary>
53 </indexterm>Key Features of LNet</title>
54 <para>Key features of LNet include:</para>
57 <para>RDMA, when supported by underlying networks</para>
60 <para>Support for many commonly-used network types</para>
63 <para>High availability and recovery</para>
66 <para>Support of multiple network types simultaneously</para>
69 <para>Routing among disparate networks</para>
72 <para>LNet permits end-to-end read/write throughput at or near peak bandwidth rates on a variety
73 of network interconnects.</para>
75 <section xml:id="idp694976">
77 <primary>Lustre</primary>
78 <secondary>Networks</secondary>
79 </indexterm>Lustre Networks</title>
80 <para>A Lustre network is comprised of clients and servers running the Lustre software. It need
81 not be confined to one LNet subnet but can span several networks provided routing is possible
82 between the networks. In a similar manner, a single network can have multiple LNet subnets. </para>
83 <para>The Lustre networking stack is comprised of two layers, the LNet code module and the LND.
84 The LNet layer operates above the LND layer in a manner similar to the way the network layer
85 operates above the data link layer. LNet layer is connectionless, asynchronous and does not
86 verify that data has been transmitted while the LND layer is connection oriented and typically
87 does verify data transmission.</para>
88 <para>LNets are uniquely identified by a label comprised of a string corresponding to an LND and
89 a number, such as tcp0, o2ib0, or o2ib1, that uniquely identifies each LNet. Each node on an
90 LNet has at least one network identifier (NID). A NID is a combination of the address of the
91 network interface and the LNet label in the
92 form:<literal><replaceable>address</replaceable>@<replaceable>LNet_label</replaceable></literal>.</para>
93 <para>Examples: <screen>192.168.1.2@tcp0
94 10.13.24.90@o2ib1</screen></para>
95 <para>In certain circumstances it might be desirable for Lustre file system traffic to pass
96 between multiple LNets. This is possible using LNet routing. It is important to realize that
97 LNet routing is not the same as network routing. For more details about LNet routing, see
98 <xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="configuringlnet"/></para>
100 <section xml:id="supported_networks">
102 <primary>LNet</primary>
103 <secondary>supported networks</secondary>
104 </indexterm>Supported Network Types</title>
105 <para>The LNet code module includes LNDs to support many network types including:</para>
108 <para> InfiniBand: OpenFabrics OFED (o2ib)</para>
111 <para> TCP (any network carrying TCP traffic, including GigE, 10GigE, and IPoIB)</para>
114 <para> RapidArray: ra</para>
117 <para> Quadrics: Elan</para>
123 vim:expandtab:shiftwidth=2:tabstop=8: