- <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 <xref linkend="settingupbonding"/>.</para>
+ <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>