From a789c390ffe1ef596065780b2beeb4b2ef63960e Mon Sep 17 00:00:00 2001 From: Joseph Gmitter Date: Fri, 27 Jan 2017 15:22:10 -0500 Subject: [PATCH] LUDOC-359 lnet: Update to correct Lnet routings config file Updated section 15.5 of the manual to use the correct name for the LNet routing config file. /etc/sysconfig/lnet_routes.conf is correct, where *lustre*_routes.conf had been incorrectly specified. I also updated this section to adhere to max line width. Signed-off-by: Joseph Gmitter Change-Id: I63541395241ab8f01548bb3431bc4b9dfeffcb7c Reviewed-on: https://review.whamcloud.com/25145 Tested-by: Jenkins Reviewed-by: Amir Shehata --- ManagingLNet.xml | 29 ++++++++++++++++++++++------- 1 file changed, 22 insertions(+), 7 deletions(-) diff --git a/ManagingLNet.xml b/ManagingLNet.xml index d0ba235..ea3fc20 100644 --- a/ManagingLNet.xml +++ b/ManagingLNet.xml @@ -234,21 +234,36 @@ ents"
- <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>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. The + /etc/sysconfig/lnet_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> + <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: + 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 . + 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> -- 1.8.3.1