How to setup multiple iSCSI targets which span from different node?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi.

I want to setup iSCSI targets which have different IP addresses.
More detail, I want to make a specific node which handles all
discovery requests from clients.
My scenario is as follow.

(1) The storage server has multiple storage nodes and each node has a
different IP address. Each storage node exports many iSCSI targets.
      <node1>: 10.0.0.11
           1st_target_in_node_1, (portal: 10.0.0.11:3333) <for client 1>
           2st_target_in_node_1, (portal: 10.0.0.11:3334) <for client 2>
           3st_target_in_node_1, (portal: 10.0.0.11:3335) <for client 3>
      <node2>: 10.0.0.12
           1st_target_in_node_2, (portal: 10.0.0.12:3333) <for client 1>
      <node3>: 10.0.0.13
           1st_target_in_node_3, (portal: 10.0.0.13:3333) <for client 2>
           2st_target_in_node_3, (portal: 10.0.0.13:3334) <for client 3>
      ...

(2) Multiple clients try to discovery available iSCSI targets by using
a single portal.
 10.0.0.10 is an alias IP address. Let's assume <node1>:10.0.0.11 has
this alias IP address.
  [Client1] iscsiadm -m discovery -t st -P 10.0.0.10
           1st_target_in_node_1, (portal: 10.0.0.11:3333) <for client 1>
           1st_target_in_node_2, (portal: 10.0.0.12:3333) <for client 1>
  [Client2] iscsiadm -m discovery -t st -P 10.0.0.10
           2st_target_in_node_1, (portal: 10.0.0.11:3334) <for client 2>
           1st_target_in_node_3, (portal: 10.0.0.13:3333) <for client 2>
  [Client2] iscsiadm -m discovery -t st -P 10.0.0.10
           3st_target_in_node_1, (portal: 10.0.0.11:3335) <for client 3>
           2st_target_in_node_3, (portal: 10.0.0.13:3334) <for client 3>


In this scenario, I try to use open source tools (tgtd, targetcli) to
setup iSCSI targets with different portals. But I cannot.
For example, when I use tgtd

root@host# tgtadm --lld iscsi --op new --mode portal --param portal=10.0.2.1
tgtadm: invalid request

It looks like tgtd and targetcli do not support remote IP addresses
(which are not in the local machine) for portals.


In summary, my questions are.
(1) Do tgtd and targetcli support remote IP addresses for portals? If
it supports, how can I do that?
(2) To achieve the goal, should I make a specific proxy server to
handle discovery requests from clients? (constructing own iSCSI target
mapping (iSCSI target <-> node IP address), parsing iSCSI requests,
determining the discovery commands, and replying back to the client)

Sincerely,
Joonsung Kim.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux