From fae83cf58a7e0a4830d67979ac7f1d4fa2ee5ceb Mon Sep 17 00:00:00 2001 From: Amir Shehata Date: Wed, 4 Oct 2017 15:33:45 -0700 Subject: [PATCH] LUDOC-392 lnet: clarify lnetctl usage When using lnetctl to manage an LNet configured outside of lnetctl, lnetctl lnet configure must be called first before lnetctl can add or remove networks and interfaces. Signed-off-by: Amir Shehata Change-Id: Ie61dad46bb40353701e19a28dc96c15d80a7afb7 Reviewed-on: https://review.whamcloud.com/29323 Tested-by: Jenkins Reviewed-by: Sonia Sharma Reviewed-by: Joseph Gmitter --- ConfiguringLNet.xml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/ConfiguringLNet.xml b/ConfiguringLNet.xml index da67cbb..d4077af 100755 --- a/ConfiguringLNet.xml +++ b/ConfiguringLNet.xml @@ -45,9 +45,12 @@ required if you are using Infiniband or multiple Ethernet interfaces. The lnetctl utility can be used - to initialize LNet without bringing up any network interfaces. This - gives flexibility to the user to add interfaces after LNet has been - loaded. + to initialize LNet without bringing up any network interfaces. Network + interfaces can be added after configuring LNet via lnetctl. + lnetctl can also be used to manage an operational LNet. + However, if it wasn't initialized by lnetctl then + lnetctl lnet configure must be invoked before + lnetctl can be used to manage LNet. DLC also introduces a C-API to enable configuring LNet programatically. See -- 1.8.3.1