-<?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="managinglnet">
+<?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="managinglnet">
<title xml:id="managinglnet.title">Managing Lustre Networking (LNet)</title>
<para>This chapter describes some tools for managing Lustre networking (LNet) and includes the
following sections:</para>
</section>
</section>
<section xml:id="dbdoclet.50438203_82542">
- <title><indexterm><primary>LNet</primary><secondary>multi-rail configuration</secondary></indexterm>Multi-Rail Configurations with LNet</title>
- <para>To aggregate bandwidth across both rails of a dual-rail IB cluster (o2iblnd) <footnote>
- <para>Multi-rail configurations are only supported by o2iblnd; other IB LNDs do not support multiple interfaces.</para>
+ <title><indexterm><primary>LNet</primary><secondary>hardware multi-rail
+ configuration</secondary></indexterm>Hardware Based Multi-Rail
+ Configurations with LNet</title>
+ <para>To aggregate bandwidth across both rails of a dual-rail IB cluster
+ (o2iblnd) <footnote>
+ <para>Hardware multi-rail configurations are only supported by o2iblnd;
+ other IB LNDs do not support multiple interfaces.</para>
</footnote> using LNet, consider these points:</para>
<itemizedlist>
<listitem>
- <para>LNet can work with multiple rails, however, it does not load balance across them. The actual rail used for any communication is determined by the peer NID.</para>
+ <para>LNet can work with multiple rails, however, it does not load
+ balance across them. The actual rail used for any communication is
+ determined by the peer NID.</para>
</listitem>
<listitem>
- <para>Multi-rail LNet configurations do not provide an additional level of network fault
- tolerance. The configurations described below are for bandwidth aggregation only. </para>
+ <para>Hardware multi-rail LNet configurations do not provide an
+ additional level of network fault tolerance. The configurations
+ described below are for bandwidth aggregation only.</para>
</listitem>
<listitem>
- <para>A Lustre node always uses the same local NID to communicate with a given peer NID. The criteria used to determine the local NID are:</para>
+ <para>A Lustre node always uses the same local NID to communicate with a
+ given peer NID. The criteria used to determine the local NID are:</para>
<itemizedlist>
- <listitem>
- <para condition='l25'>Lowest route priority number (lower number, higher priority).</para>
- </listitem>
+ <listitem>
+ <para condition='l25'>Lowest route priority number (lower number,
+ higher priority).</para>
+ </listitem>
<listitem>
<para>Fewest hops (to minimize routing), and</para>
</listitem>
<listitem>
- <para>Appears first in the "<literal>networks</literal>" or "<literal>ip2nets</literal>" LNet configuration strings</para>
+ <para>Appears first in the "<literal>networks</literal>"
+ or "<literal>ip2nets</literal>" LNet configuration strings
+ </para>
</listitem>
</itemizedlist>
</listitem>
"even" servers with <literal>o2ib2</literal> on <literal>rail1</literal>.</para>
</section>
</section>
- <section xml:id="managinglnet.configuringroutes" condition='l24'>
- <title><indexterm><primary>LNet</primary></indexterm>Dynamically Configuring LNet Routes</title>
- <para>Two scripts are provided: <literal>lustre/scripts/lustre_routes_config</literal> and <literal>lustre/scripts/lustre_routes_conversion</literal>.</para>
- <para><literal>lustre_routes_config</literal> sets or cleans up LNet routes from the specified config file. <literal>/etc/sysconfig/lustre_routes.conf</literal> file can be used to automatically configure routes on LNet startup. </para>
- <para><literal>lustre_routes_conversion</literal> converts a legacy routes configuration file to the new syntax, which is parsed by <literal>lustre_routes_config</literal>.</para>
+ <section xml:id="managinglnet.configuringroutes">
+ <title><indexterm><primary>LNet</primary></indexterm>Dynamically Configuring
+ LNet Routes</title>
+ <para>Two scripts are provided:
+ <literal>lustre/scripts/lustre_routes_config</literal> and
+ <literal>lustre/scripts/lustre_routes_conversion</literal>.</para>
+ <para><literal>lustre_routes_config</literal> sets or cleans up LNet routes
+ from the specified config file. The
+ <literal>/etc/sysconfig/lnet_routes.conf</literal> file can be used to
+ automatically configure routes on LNet startup. </para>
+ <para><literal>lustre_routes_conversion</literal> converts a legacy routes
+ configuration file to the new syntax, which is parsed by
+ <literal>lustre_routes_config</literal>.</para>
<section remap="h3">
- <title><indexterm><primary>LNet</primary></indexterm><literal>lustre_routes_config</literal></title>
+ <title><indexterm><primary>LNet</primary></indexterm>
+ <literal>lustre_routes_config</literal></title>
<para><literal>lustre_routes_config</literal> usage is as follows</para>
<screen><literal>lustre_routes_config [--setup|--cleanup|--dry-run|--verbose] <replaceable>config_file</replaceable></literal>
--setup: configure routes listed in config_file
--cleanup: unconfigure routes listed in config_file
--dry-run: echo commands to be run, but do not execute them
--verbose: echo commands before they are executed </screen>
- <para> The format of the file which is passed into the script is as follows: </para>
+ <para> The format of the file which is passed into the script is as
+ follows: </para>
<para><literal><replaceable>network</replaceable>: { gateway: <replaceable>gateway</replaceable>@<replaceable>exit_network</replaceable> [hop: <replaceable>hop</replaceable>] [priority: <replaceable>priority</replaceable>] }</literal></para>
- <para> An LNet router is identified when its local NID appears within the list of routes. However, this can not be achieved by the use of this script, since the script only adds extra routes after the router is identified. To ensure that a router is identified correctly, make sure to add its local NID in the routes parameter in the modprobe lustre configuration file. See <xref linkend='dbdoclet.50438293_15350'/>.</para>
+ <para> An LNet router is identified when its local NID appears within the
+ list of routes. However, this can not be achieved by the use of this
+ script, since the script only adds extra routes after the router is
+ identified. To ensure that a router is identified correctly, make sure to
+ add its local NID in the routes parameter in the modprobe lustre
+ configuration file. See <xref linkend='dbdoclet.50438293_15350'/>.</para>
</section>
<section remap="h3">
<title><indexterm><primary>LNet</primary></indexterm><literal>lustre_routes_conversion</literal></title>
</section>
</section>
</chapter>
+<!--vim:expandtab:shiftwidth=2:tabstop=8:-->
git://git.whamcloud.com / doc / manual.git / blobdiff