-<?xml version="1.0" encoding="UTF-8"?>
-<chapter version="5.0" xml:lang="en-US" xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" xml:id='understandinglustrenetworking'>
- <info>
- <title xml:id='understandinglustrenetworking.title'>Understanding Lustre Networking (LNET)</title>
- </info>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289855" xreflabel=""/>This chapter introduces Lustre Networking (LNET) and includes the following sections:</para>
- <itemizedlist><listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289859" xreflabel=""/><link xl:href="UnderstandingLustreNetworking.html#50438191_22878">Introducing LNET</link></para>
+<?xml version='1.0' encoding='UTF-8'?>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US" xml:id="understandinglustrenetworking">
+ <title xml:id="understandinglustrenetworking.title">Understanding Lustre Networking (LNet)</title>
+ <para>This chapter introduces Lustre networking (LNet). It includes the following sections:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <xref linkend="dbdoclet.50438191_22878"/>
+ </para>
</listitem>
-<listitem>
- <para> </para>
+ <listitem>
+ <para>
+ <xref linkend="dbdoclet.50438191_19625"/>
+ </para>
</listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289949" xreflabel=""/><link xl:href="UnderstandingLustreNetworking.html#50438191_19625">Key Features of LNET</link></para>
+ <listitem>
+ <para><xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="idp694976"/></para>
</listitem>
-<listitem>
- <para> </para>
+ <listitem>
+ <para>
+ <xref linkend="dbdoclet.50438191_20721"/>
+ </para>
</listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289863" xreflabel=""/><link xl:href="UnderstandingLustreNetworking.html#50438191_20721">Supported Network Types</link></para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-</itemizedlist>
- <section remap="h2">
- <title><anchor xml:id="dbdoclet.50438191_pgfId-1289865" xreflabel=""/></title>
- <section remap="h2">
- <title>2.1 <anchor xml:id="dbdoclet.50438191_22878" xreflabel=""/>Introducing LNET</title>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289866" xreflabel=""/>In a cluster with a Lustre file system, the system network connecting the servers and the clients is implemented using Lustre Networking (LNET), which provides the communication infrastructure required by the Lustre file system.</para>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289867" xreflabel=""/>LNET supports many commonly-used network types, such as InfiniBand and IP networks, and allows simultaneous availability across multiple network types with routing between them. Remote Direct Memory Access (RDMA) is permitted when supported by underlying networks using the appropriate Lustre network driver (LND). High availability and recovery features enable transparent recovery in conjunction with failover servers.</para>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289868" xreflabel=""/>An LND is a pluggable driver that provides support for a particular network type. LNDs are loaded into the driver stack, with one LND for each network type in use.</para>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1290033" xreflabel=""/>For information about configuring LNET, see <link xl:href="ConfiguringLNET.html#50438216_64580">Chapter 9</link>: <link xl:href="ConfiguringLNET.html#50438216_29256">Configuring Lustre Networking (LNET)</link>.</para>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1290034" xreflabel=""/>For information about administering LNET, see <link xl:href="III_LustreAdministration.html#50438269_15166">PART III - Administering Lustre</link>.</para>
- </section>
- <section remap="h2">
- <title>2.2 <anchor xml:id="dbdoclet.50438191_19625" xreflabel=""/>Key Features of LNET</title>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289918" xreflabel=""/>Key features of LNET include:</para>
- <itemizedlist><listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289871" xreflabel=""/><anchor xml:id="dbdoclet.50438191_57931" xreflabel=""/> RDMA, when supported by underlying networks such as InfiniBand or</para>
- <para> Myrinet MX</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289872" xreflabel=""/> Support for many commonly-used network types such as InfiniBand and TCP/IP</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289873" xreflabel=""/> High availability and recovery features enabling transparent recovery in conjunction with failover servers</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289874" xreflabel=""/> Simultaneous availability of multiple network types with routing between them.</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-</itemizedlist>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1290430" xreflabel=""/>LNET provides end-to-end throughput over Gigabit Ethernet (GigE) networks in excess of 100 MB/s, throughput up to 1.5 GB/s over InfiniBand double data rate (DDR) links, and throughput over 1 GB/s across 10GigE interfaces.</para>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1290434" xreflabel=""/>Lustre can use bonded networks, such as bonded Ethernet networks, when the underlying network technology supports bonding. For more information, see <link xl:href="SettingUpBonding.html#50438258_72593">Chapter 7</link>: <link xl:href="UnderstandingLustreNetworking.html#50438191_40026">Understanding Lustre Networking (LNET)</link>.</para>
- </section>
- <section remap="h2">
- <title>2.3 <anchor xml:id="dbdoclet.50438191_20721" xreflabel=""/>Supported Network Types</title>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289882" xreflabel=""/>LNET includes LNDs to support many network types including:</para>
- <itemizedlist><listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289883" xreflabel=""/> InfiniBand: OpenFabrics OFED (o2ib)</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289884" xreflabel=""/> TCP (any network carrying TCP traffic, including GigE, 10GigE, and IPoIB)</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289885" xreflabel=""/> Cray: Seastar</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289886" xreflabel=""/> Myrinet: MX</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289888" xreflabel=""/><anchor xml:id="dbdoclet.50438191_marker-1289887" xreflabel=""/> RapidArray: ra</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-<listitem>
- <para><anchor xml:id="dbdoclet.50438191_pgfId-1289890" xreflabel=""/><anchor xml:id="dbdoclet.50438191_marker-1289889" xreflabel=""/> Quadrics: Elan</para>
- </listitem>
-<listitem>
- <para> </para>
- </listitem>
-</itemizedlist>
- </section>
+ </itemizedlist>
+ <section xml:id="dbdoclet.50438191_22878">
+ <title><indexterm>
+ <primary>LNet</primary>
+ </indexterm><indexterm>
+ <primary>LNet</primary>
+ <secondary>understanding</secondary>
+ </indexterm> Introducing LNet</title>
+ <para>In a cluster using one or more Lustre file systems, the network communication
+ infrastructure required by the Lustre file system is implemented using the Lustre networking
+ (LNet) feature.</para>
+ <para>LNet supports many commonly-used network types, such as InfiniBand and IP networks, and
+ allows simultaneous availability across multiple network types with routing between them.
+ Remote direct memory access (RDMA) is permitted when supported by underlying networks using
+ the appropriate Lustre network driver (LND). High availability and recovery features enable
+ transparent recovery in conjunction with failover servers.</para>
+ <para>An LND is a pluggable driver that provides support for a particular network type, for
+ example <literal>ksocklnd</literal> is the driver which implements the TCP Socket LND that
+ supports TCP networks. LNDs are loaded into the driver stack, with one LND for each network
+ type in use.</para>
+ <para>For information about configuring LNet, see <xref linkend="configuringlnet"/>.</para>
+ <para>For information about administering LNet, see <xref linkend="adminlustrepart3"/>.</para>
+ </section>
+ <section xml:id="dbdoclet.50438191_19625">
+ <title><indexterm>
+ <primary>LNet</primary>
+ <secondary>features</secondary>
+ </indexterm>Key Features of LNet</title>
+ <para>Key features of LNet include:</para>
+ <itemizedlist>
+ <listitem>
+ <para>RDMA, when supported by underlying networks</para>
+ </listitem>
+ <listitem>
+ <para>Support for many commonly-used network types</para>
+ </listitem>
+ <listitem>
+ <para>High availability and recovery</para>
+ </listitem>
+ <listitem>
+ <para>Support of multiple network types simultaneously</para>
+ </listitem>
+ <listitem>
+ <para>Routing among disparate networks</para>
+ </listitem>
+ </itemizedlist>
+ <para>LNet permits end-to-end read/write throughput at or near peak bandwidth rates on a variety
+ of network interconnects.</para>
+ </section>
+ <section xml:id="idp694976">
+ <title><indexterm>
+ <primary>Lustre</primary>
+ <secondary>Networks</secondary>
+ </indexterm>Lustre Networks</title>
+ <para>A Lustre network is comprised of clients and servers running the Lustre software. It need
+ not be confined to one LNet subnet but can span several networks provided routing is possible
+ between the networks. In a similar manner, a single network can have multiple LNet subnets. </para>
+ <para>The Lustre networking stack is comprised of two layers, the LNet code module and the LND.
+ The LNet layer operates above the LND layer in a manner similar to the way the network layer
+ operates above the data link layer. LNet layer is connectionless, asynchronous and does not
+ verify that data has been transmitted while the LND layer is connection oriented and typically
+ does verify data transmission.</para>
+ <para>LNets are uniquely identified by a label comprised of a string corresponding to an LND and
+ a number, such as tcp0, o2ib0, or o2ib1, that uniquely identifies each LNet. Each node on an
+ LNet has at least one network identifier (NID). A NID is a combination of the address of the
+ network interface and the LNet label in the
+ form:<literal><replaceable>address</replaceable>@<replaceable>LNet_label</replaceable></literal>.</para>
+ <para>Examples: <screen>192.168.1.2@tcp0
+10.13.24.90@o2ib1</screen></para>
+ <para>In certain circumstances it might be desirable for Lustre file system traffic to pass
+ between multiple LNets. This is possible using LNet routing. It is important to realize that
+ LNet routing is not the same as network routing. For more details about LNet routing, see
+ <xref xmlns:xlink="http://www.w3.org/1999/xlink" linkend="configuringlnet"/></para>
+ </section>
+ <section xml:id="dbdoclet.50438191_20721">
+ <title><indexterm>
+ <primary>LNet</primary>
+ <secondary>supported networks</secondary>
+ </indexterm>Supported Network Types</title>
+ <para>The LNet code module includes LNDs to support many network types including:</para>
+ <itemizedlist>
+ <listitem>
+ <para> InfiniBand: OpenFabrics OFED (o2ib)</para>
+ </listitem>
+ <listitem>
+ <para> TCP (any network carrying TCP traffic, including GigE, 10GigE, and IPoIB)</para>
+ </listitem>
+ <listitem>
+ <para> RapidArray: ra</para>
+ </listitem>
+ <listitem>
+ <para> Quadrics: Elan</para>
+ </listitem>
+ </itemizedlist>
</section>
</chapter>
git://git.whamcloud.com / doc / manual.git / blobdiff