From 33888b67a8db94389bdb735d7797fc7b163a3b6b Mon Sep 17 00:00:00 2001 From: Amir Shehata Date: Mon, 3 Jun 2013 15:59:04 -0700 Subject: [PATCH] LUDOC-147 lnet: Describe routes config in Manual Describe how to dynamically configure LNET routes using the two new scripts which were added: luster_routes_config and lustre_routes_conversion. Sections 15.5 was added in the Lustre Manual. LU-2950 tracks the change which landed to provide the above functionality. Signed-off-by: Amir Shehata Change-Id: I3974286bce9d726abd12a5deb568740bca4544aa Reviewed-on: http://review.whamcloud.com/6538 Tested-by: Hudson Reviewed-by: Richard Henwood Reviewed-by: Doug Oucharek Reviewed-by: Linda Bebernes --- ManagingLNET.xml | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) diff --git a/ManagingLNET.xml b/ManagingLNET.xml index c231361..a6f3516 100644 --- a/ManagingLNET.xml +++ b/ManagingLNET.xml @@ -15,6 +15,9 @@ + + +
<indexterm><primary>LNET</primary><secondary>management</secondary></indexterm> @@ -207,4 +210,43 @@ ents"</screen> <para>This configuration includes two additional proxy o2ib networks to work around Lustre's simplistic NID selection algorithm. It connects "even" clients to "even" servers with <literal>o2ib0</literal> on <literal>rail0</literal>, and "odd" servers with <literal>o2ib3</literal> on <literal>rail1</literal>. Similarly, it connects "odd" clients to "odd" servers with <literal>o2ib1</literal> on <literal>rail0</literal>, and "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 + Two scripts are provided: lustre/scripts/lustre_routes_config and lustre/scripts/lustre_routes_conversion. + lustre_routes_config sets or cleans up LNET routes from the specified config file. /etc/sysconfig/lustre_routes.conf file can be used to automatically configure routes on LNET startup. + lustre_routes_conversion converts a legacy routes configuration file to the new syntax, which is parsed by lustre_routes_config. +
+ <indexterm><primary>LNET</primary></indexterm><literal>lustre_routes_config</literal> + lustre_routes_config usage is as follows + lustre_routes_config [--setup|--cleanup|--dry-run|--verbose] config_file + --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 + The format of the file which is passed into the script is as follows: + network: { gateway: gateway@exit_network [hop: hop] [priority: priority] } + 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 . +
+
+ <indexterm><primary>LNET</primary></indexterm><literal>lustre_routes_conversion</literal> + lustre_routes_conversion usage is as follows: + lustre_routes_conversion legacy_file new_file + lustre_routes_conversion takes as a first parameter a file with routes configured as follows: + network [hop] gateway@exit network[:priority]; + The script then converts each routes entry in the provided file to: + network: { gateway: gateway@exit network [hop: hop] [priority: priority] } + and appends each converted entry to the output file passed in as the second parameter to the script. +
+
+ <indexterm><primary>LNET</primary></indexterm><literal>Route Configuration Examples</literal> + Below is an example of a legacy LNET route configuration. A legacy configuration file can have multiple entries. + tcp1 10.1.1.2@tcp0:1; +tcp2 10.1.1.3@tcp0:2; +tcp3 10.1.1.4@tcp0; + Below is an example of the converted LNET route configuration. The following would be the result of the lustre_routes_conversion script, when run on the above legacy entries. + tcp1: { gateway: 10.1.1.2@tcp0 priority: 1 } +tcp2: { gateway: 10.1.1.2@tcp0 priority: 2 } +tcp1: { gateway: 10.1.1.4@tcp0 } +
+
-- 1.8.3.1