Lines Matching +full:storage +full:- +full:target

1 # iSCSI Target {#iscsi}
3 ## iSCSI Target Getting Started Guide {#iscsi_getting_started}
5 The Storage Performance Development Kit iSCSI target application is named `iscsi_tgt`.
26 ### Assigning CPU Cores to the iSCSI Target {#iscsi_config_lcore}
31 To ensure the SPDK iSCSI target has the best performance, place the NICs and the NVMe devices on the
32 same NUMA node and configure the target to run on CPU cores associated with that node. The following
33 command line option is used to configure the SPDK iSCSI target:
36 -m 0xF000000
39 This is a hexadecimal bit mask of the CPU cores where the iSCSI target will start polling threads.
42 ## Configuring iSCSI Target via RPC method {#iscsi_rpc}
44 The iSCSI target is configured via JSON-RPC calls. See @ref jsonrpc for details.
48 - iscsi_create_portal_group -- Add a portal group.
49 - iscsi_delete_portal_group -- Delete an existing portal group.
50 - iscsi_target_node_add_pg_ig_maps -- Add initiator group to portal group mappings to an existing i…
51 - iscsi_target_node_remove_pg_ig_maps -- Delete initiator group to portal group mappings from an ex…
52 - iscsi_get_portal_groups -- Show information about all available portal groups.
60 - iscsi_create_initiator_group -- Add an initiator group.
61 - iscsi_delete_initiator_group -- Delete an existing initiator group.
62 - iscsi_initiator_group_add_initiators -- Add initiators to an existing initiator group.
63 - iscsi_get_initiator_groups -- Show information about all available initiator groups.
69 ### Target nodes
71 - iscsi_create_target_node -- Add an iSCSI target node.
72 - iscsi_delete_target_node -- Delete an iSCSI target node.
73 - iscsi_target_node_add_lun -- Add a LUN to an existing iSCSI target node.
74 - iscsi_get_target_nodes -- Show information about all available iSCSI target nodes.
77 /path/to/spdk/scripts/rpc.py iscsi_create_target_node Target3 Target3_alias MyBdev:0 1:2 64 -d
82 The Linux initiator is open-iscsi.
84 Installing open-iscsi package
87 yum install -y iscsi-initiator-utils
92 apt-get install -y open-iscsi
105 killall -HUP iscsid
126 Assume target is at 10.0.0.1
129 iscsiadm -m discovery -t sendtargets -p 10.0.0.1
132 ### Connect to target
135 iscsiadm -m node --login
138 At this point the iSCSI target should show up as SCSI disks. Check dmesg to see what
141 ### Disconnect from target
144 iscsiadm -m node --logout
147 ### Deleting target node cache
150 iscsiadm -m node -o delete
153 This will cause the initiator to forget all previously discovered iSCSI target nodes.
158 iscsiadm -m session -P 3 | grep "Attached scsi disk" | awk '{print $4}'
185 ### Example: Configure simple iSCSI Target with one portal and two LUNs
187 Assuming we have one iSCSI Target server with portal at 10.0.0.1:3200, two LUNs (Malloc0 and Malloc…
192 #### Configure iSCSI Target
203 ./scripts/rpc.py bdev_malloc_create -b Malloc0 64 512
204 ./scripts/rpc.py bdev_malloc_create -b Malloc1 64 512
219 Finally construct one target using previously created bdevs as LUN0 (Malloc0) and LUN1 (Malloc1)
223 ./scripts/rpc.py iscsi_create_target_node disk1 "Data Disk1" "Malloc0:0 Malloc1:1" 1:2 64 -d
228 Discover target
231 $ iscsiadm -m discovery -t sendtargets -p 10.0.0.1
232 10.0.0.1:3260,1 iqn.2016-06.io.spdk:disk1
235 Connect to the target
238 iscsiadm -m node --login
241 At this point the iSCSI target should show up as SCSI disks.
248 [630112.124743] scsi 68:0:0:0: Direct-Access     INTEL    Malloc disk      0001 PQ: 0 ANSI: 5
249 [630112.125445] sd 68:0:0:0: [sdd] 131072 512-byte logical blocks: (67.1 MB/64.0 MiB)
254 [630112.126483] scsi 68:0:0:1: Direct-Access     INTEL    Malloc disk      0001 PQ: 0 ANSI: 5
256 [630112.127143] sd 68:0:0:1: [sde] 131072 512-byte logical blocks: (67.1 MB/64.0 MiB)
269 $ iscsiadm -m session -P 3 | grep "Attached scsi disk" | awk '{print $4}'
285 upper level stack (for iSCSI target, the upper level stack is scsi/lun) to
286 handle the hot-remove event.
290 When the LUN receive the hot-remove notification from block device layer,
300 The SPDK iSCSI target application supports iSCSI login redirection feature.
303 contains a set of portals. Users for the SPDK iSCSI target application configure
309 The SPDK iSCSI target application usually has a discovery portal. The discovery
311 of portals on which these target may be accessed, by a discovery session.
315 portal group may optionally have a redirect portal for non-discovery logins for
316 each associated target. This redirect portal must be from a private portal group.
318 Initiators configure portals in public portal groups as target portals. When an
319 initiator logs in to a target through a portal in an associated public portal group,
320 the target sends a temporary redirection response with a redirect portal. Then the
321 initiator logs in to the target again through the redirect portal.
324 `iscsi_create_portal_group` RPC, associate portal groups with a target using the
326 specify a up-to-date redirect portal in a public portal group for a target using
330 Typically users will use the login redirection feature in scale out iSCSI target
331 system, which runs multiple SPDK iSCSI target applications.