public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
* configure MPXIO for ISCSI devices
@ 2024-06-19 13:06 Carsten Grzemba
  2024-06-19 16:18 ` [discuss] " Udo Grabowski (IMK)
  0 siblings, 1 reply; 5+ messages in thread
From: Carsten Grzemba @ 2024-06-19 13:06 UTC (permalink / raw)
  To: illumos-discuss

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

I have various devices connected via ISCSI to Omnios: disks, tapes and media changer.
I want to use MXIO for the disk devices but not for the tape and media changer device. I know that I can configure MPXIO for FC devices at port level in that kind:

name="fp" parent="/pci@0,0/pci8086,2940@1c/pci1028,1f17@0" port=0 mpxio-disable="no";

there looks the physical path like
/devices/pci@0,0/pci8086,2940@1c/pci1028,1f17@0/sd@0,0:c

But for ISCSI devices the path looks like 

/devices/iscsi/disk@0000iqn.2006-08.com.huawei%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A1020003%3A172.xx.yy.zz000E,1:c

How can I configure the MPXIO enable/disable per device for ISCSI devices?

[-- Attachment #2: Type: text/html, Size: 937 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [discuss] configure MPXIO for ISCSI devices
  2024-06-19 13:06 configure MPXIO for ISCSI devices Carsten Grzemba
@ 2024-06-19 16:18 ` Udo Grabowski (IMK)
  2024-06-20 10:21   ` Carsten Grzemba
  2024-06-20 14:01   ` Carsten Grzemba
  0 siblings, 2 replies; 5+ messages in thread
From: Udo Grabowski (IMK) @ 2024-06-19 16:18 UTC (permalink / raw)
  To: discuss

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

On 19/06/2024 15:06, Carsten Grzemba via illumos-discuss wrote:
> I have various devices connected via ISCSI to Omnios: disks, tapes and media
> changer.
> I want to use MXIO for the disk devices but not for the tape and media changer
> device. I know that I can configure MPXIO for FC devices at port level in that kind:
>
> name="fp" parent="/pci@0,0/pci8086,2940@1c/pci1028,1f17@0" port=0
> mpxio-disable="no";
>
> there looks the physical path like
> /devices/pci@0,0/pci8086,2940@1c/pci1028,1f17@0/sd@0,0:c
>
> But for ISCSI devices the path looks like
>
> /devices/iscsi/disk@0000iqn.2006-08.com.huawei
> <mailto:disk@0000iqn.2006-08.com.huawei>%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A1020003%3A172.xx.yy.zz000E,1:c
>
> How can I configure the MPXIO enable/disable per device for ISCSI devices?
>

You may work along the lines shown here:
<https://docs.oracle.com/cd/E23824_01/html/821-1459/fncpc.html>
On Iscsi, you configure multiple pathes via iscsiadm, and then
mpathadm should show them, and mpxio takes care of them.
You can selectively configure your pathes to exclude Tapes and
media changers.
In principle, this works on illunos, too, I've done this a decade
ago while fiddling with iscsi boot (which essentially DOESN'T work!),
I could configure multiple pathes, but abandoned that because it
didn't work for the purpose (booting...).
-- 
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology          https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [discuss] configure MPXIO for ISCSI devices
  2024-06-19 16:18 ` [discuss] " Udo Grabowski (IMK)
@ 2024-06-20 10:21   ` Carsten Grzemba
  2024-06-20 12:10     ` Udo Grabowski (IMK)
  2024-06-20 14:01   ` Carsten Grzemba
  1 sibling, 1 reply; 5+ messages in thread
From: Carsten Grzemba @ 2024-06-20 10:21 UTC (permalink / raw)
  To: illumos-discuss

[-- Attachment #1: Type: text/plain, Size: 484 bytes --]

> You can selectively configure your pathes to exclude Tapes and media changers.
How is the syntax for selectively configure paths?
My plan is to disable mpxio for iscsi global and enable mpxio only for the disk. There the paths are like shown above:

/devices/iscsi/disk@0000iqn.2006-08.com.huawei%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A1020003%3A172.xx.yy.ZZ000E,1:c

/devices/iscsi/disk@0000iqn.2006-08.com.huawei%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A20003%3A172.xx.yy.zz0004,0:c

[-- Attachment #2: Type: text/html, Size: 706 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [discuss] configure MPXIO for ISCSI devices
  2024-06-20 10:21   ` Carsten Grzemba
@ 2024-06-20 12:10     ` Udo Grabowski (IMK)
  0 siblings, 0 replies; 5+ messages in thread
From: Udo Grabowski (IMK) @ 2024-06-20 12:10 UTC (permalink / raw)
  To: discuss

[-- Attachment #1: Type: text/plain, Size: 4400 bytes --]

On 20/06/2024 12:21, Carsten Grzemba via illumos-discuss wrote:
>> You can selectively configure your pathes to exclude Tapes and media changers.
> How is the syntax for selectively configure paths?
> My plan is to disable mpxio for iscsi global and enable mpxio only for the disk. There the paths are like shown above:
>
> /devices/iscsi/disk@0000iqn.2006-08.com.huawei
> <mailto:disk@0000iqn.2006-08.com.huawei>%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A1020003%3A172.xx.yy.ZZ000E,1:c
>
> /devices/iscsi/disk@0000iqn.2006-08.com.huawei
> <mailto:disk@0000iqn.2006-08.com.huawei>%3Aoceanstor%3A2100a08cf8f6f36b%3A%3A20003%3A172.xx.yy.zz0004,0:c

I guess that you either don't configure those pathes at all (where
do they come from ? isns server ? ) or selectively remove them like
described in the man page (s.b.).

mpxio for iscsi is managed via the /kernel/drv/iscsi.conf file,
there's also an iscsit.conf file, but I don't know how that should
work in this context. mpxio for iscsi seems to be a global parameter.

remove Subcommand
      The syntax for the remove subcommand is:

        # iscsiadm remove direct_object

      The remove subcommand supports the following direct_objects:

      discovery-address discovery-address, ...

          Removes a target  device  from  the  list  of  discovery
          addresses.  A  discovery address (as in the syntax shown
          below) is an  IP  address-port  combination  used  in  a
          SendTargets  discovery  session.  Using  this  discovery
          approach, a target device can inform an initiator of the
          target address and target name of each target exposed by
          that device. If any  target  exposed  by  the  discovery
          address  is  currently mounted or there is active I/O on
          the device,  an  error  of  "logical  unit  in  use"  is
          returned and the operation fails. If the associated dev-
          ices are not in use, they are removed.

          discovery-address must be formatted as:

            <IP address>[:<port>]

          There are no options associated with this direct object.

      isns-server isns-server, ...

          Removes an iSNS server from  the  list  of  iSNS  server
          addresses. An iSNS server address (specified in the syn-
          tax shown below) is an IP address-port combination  used
          in  an  iSNS discovery session. By using iSNS discovery,
          an iSNS server can provide an initiator with information
          about  a portal and the name of each target that belongs
          to the same discovery domain as that of  the  initiator.
          If  any  target discovered by means of iSNS is currently
          mounted or there is active I/O on the device,  an  error
          of  "logical  unit in use" is returned and the operation
          fails. If the associated devices are not  in  use,  they
          are removed.

          isns-server must be formatted as:

            IP_address[:port]

          There are no options associated with this direct object.

      static-config static_target, ...

          Removes a target from the list of statically  discovered
          targets.  If  the  target  being  removed  is  currently
          mounted or there is active I/O on the device,  an  error
          of  "logical  unit in use" is returned and the operation
          fails. If a device is not in use, it will be removed.

          static_target must be formatted as:

            <target-name>,<target-address>[:port-number][,tpgt]

          There are no options associated with this direct object.

      target-param target-name

          Removes target specified by target-name. The target name
          is formatted as:

            <target-name>

          There are no options associated with this direct object.
          For  iSCSI  booting  when  the  Solaris I/O multipathing
          feature (formerly known as Sun StorEdge Traffic  Manager
          [STMS]  or MPxIO) is enabled, you cannot remove the tar-
          get.


-- 
Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
https://www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology          https://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [discuss] configure MPXIO for ISCSI devices
  2024-06-19 16:18 ` [discuss] " Udo Grabowski (IMK)
  2024-06-20 10:21   ` Carsten Grzemba
@ 2024-06-20 14:01   ` Carsten Grzemba
  1 sibling, 0 replies; 5+ messages in thread
From: Carsten Grzemba @ 2024-06-20 14:01 UTC (permalink / raw)
  To: illumos-discuss

[-- Attachment #1: Type: text/plain, Size: 118 bytes --]

Ah, thanks! 
For ISCSI is not possible to enable or disable MPXIO per port basis, like for fibre channel in fp.conf .

[-- Attachment #2: Type: text/html, Size: 183 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-06-20 14:01 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-19 13:06 configure MPXIO for ISCSI devices Carsten Grzemba
2024-06-19 16:18 ` [discuss] " Udo Grabowski (IMK)
2024-06-20 10:21   ` Carsten Grzemba
2024-06-20 12:10     ` Udo Grabowski (IMK)
2024-06-20 14:01   ` Carsten Grzemba

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).