From 5f768dd52d87efddbd7efa23d57c6da62281728b Mon Sep 17 00:00:00 2001 From: Steffen Maier Date: Tue, 14 Mar 2017 14:19:09 +0100 Subject: [PATCH] lsluns: point out IBM Storwize configuration requirements Signed-off-by: Steffen Maier Reviewed-by: Jens Remus Signed-off-by: Michael Holzheu --- zconf/lsluns | 4 ++++ zconf/lsluns.8 | 12 ++++++++++++ 2 files changed, 16 insertions(+) diff --git a/zconf/lsluns b/zconf/lsluns index 75c31eee..4d96ebdf 100755 --- a/zconf/lsluns +++ b/zconf/lsluns @@ -177,6 +177,10 @@ $PROGRAM_NAME [-c ] ... [-p ] ... [-h] [-v] Discovering LUNs only makes sense for NPIV-enabled FCP devices without zfcp automatic LUN scan. zfcp automatic LUN scan is available as of kernel version 2.6.37, if not disabled with zfcp.allow_lun_scan=0. + For storage products that do not support a REPORT LUNS + well-known logical unit (such as IBM Storwize products), + ensure that LUN 0 represents a valid peripheral device type. + See the man page for more information. $PROGRAM_NAME -a [-c ] ... [-p ] ... [-h] [-v] diff --git a/zconf/lsluns.8 b/zconf/lsluns.8 index da8d5b21..daee0e92 100644 --- a/zconf/lsluns.8 +++ b/zconf/lsluns.8 @@ -64,6 +64,18 @@ If not attached already, lsluns temporarily attaches LUN 0 Do not terminate lsluns with a signal. Signals interfere with the removal of temporarily attached LUNs. +.TP +Storage Products +Some storage products return a peripheral device type of 31==0x1f +with peripheral qualifier 0 in a SCSI standard INQUIRY command +for an unmapped FCP LUN 0. Examples are: IBM Storwize products, +including IBM V7000, IBM V840, IBM V9000, and IBM SAN Volume Controller. +For lsluns to work with such storage products, +you must have a host mapping on the storage, which maps some volume +to exported FCP LUN 0x0000000000000000 (Storwize host map property "SCSI ID" 0) +for each used FCP-device initiator WWPN. The volume can be +a minimum-sized thin-provisioned shared stand-in volume. + .SH OPTIONS .TP .BR \-a ", " \-\-active