HEX
Server: Apache/2.4.63 (Unix)
System: Linux TOMS-220NAS 4.4.302+ #86009 SMP Wed Nov 26 18:19:17 CST 2025 x86_64
User: flavio87 (1026)
PHP: 8.3.27
Disabled: NONE
Upload Files
File: //usr/local/packages/@appstore/ScsiTarget/ui/help/rus/target.html
<!DOCTYPE html>
<html class="img-no-display">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" >
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

<title>SAN Manager</title>


<link href="../../../../help/help.css" type="text/css" rel="stylesheet"  />
<link href="../../../../help/scrollbar/flexcroll.css" type="text/css" rel="stylesheet"  />
<script type="text/javascript" src="../../../../help/scrollbar/flexcroll.js"></script>
<script type="text/javascript" src="../../../../help/scrollbar/initFlexcroll.js"></script>
</head>
<body><h2><a name="leaf_target"></a>iSCSI</h2>
<p>Depending on the model, Synology NAS supports creating multiple targets to which LUNs can be mapped.</p>
<p><span class="note_head">Note: </span>The number of targets supported varies depending on Synology NAS models.</p>
<h4>To create a target:</h4>
<ol>
 <li>Click the <b>Create</b> button.</li>
 <li>Enter the target's information, including <b>Name</b>, <b>IQN</b>, and whether to enable <b>CHAP authentication</b>.</li>
 <li>Click <b>Next</b>.</li>
 <li>Set up LUN mapping. Select <b>Create a new LUN</b> or <b>Map existing LUNs</b>.</li>
 <li>Click <b>Next</b>.</li>
 <li>Click <b>Back</b> to modify or <b>Apply</b> to confirm settings.</li>
</ol>
<div class="section">
<h4>Terminologies</h4>
<ul>
<li><b>IQN</b>: IQN (iSCSI Qualified Name) is a set of unique name for a target. It
should not conflict with target IQNs on other servers. IQN must be less than 128 characters and can include letters (case insensitive), numbers, colons, dashes, and dots. The suggested naming format is iqn.[date].[domain]:[device identifier], for example: <i>iqn.2000-04.com.synology:storage.diskarray.1</i>.</li>
<li><b>Mutual CHAP authentication</b>: In <b>Mutual CHAP</b>, both the client and server will authenticate each other. Any CHAP password used for client authentication must not be configured for authentication of any server, and any CHAP password used for server authentication must not be configured for authentication of any client.</li>
<p><span class="note_head">Note:</span>The Discovery process on iSCSI initiator may fail if the CHAP authentication on your NAS is enabled. Please complete Discovery first, and then enable CHAP authentication before connecting to a target. Alternatively, you can connect to a target with the IP and IQN.</p>
</ul></div>
<h4>To remove a target:</h4>
<p>You can remove a target and any mapped LUNs. When removing a LUN, all data on the LUN will be deleted.</p>
 <ol>
 <li>Select the target you want to remove.</li>
 <li>Click <b>Remove</b>.</li>
 <li>If you want to remove mapped LUNs, select <b>Delete mapped LUNs as well</b> and select the ones you want to remove.</li>
 <li>Click <b>OK</b>.</li>
 </ol>
<h4>To edit a target:</h4>
 <ol>
 <li>Select the target you want to edit.</li>
 <li>Select <b>Edit</b> from the <b>Action</b> drop-down menu.</li>
 <li>Edit the settings to your preference. Click <b>OK</b> to save the changes.</li>
 </ol>
<div class="section">
<h4>Terminologies</h4>
<ul>
<li><b>CRC Checksum</b>: Enable CRC Checksum to check for errors that occurred during data transmission.</li>
<li><b>Multiple Sessions</b>: Allow multiple sessions from more than one initiator to connect to the same target at the same time. To protect your files from corruption or unexpected data loss, it is strongly suggested that you use a shared file system or cluster system such as VMware Virtual Machine File System (VMFS) and Oracle Cluster File System (OCFS).</li>
<li><b>Network Binding</b>: You can choose specific network interfaces to access the iSCSI target.</li>
</ul></div>
<h4>To enable or disable a target:</h4>
<ol>
<li>Select the target you want to enable or disable.</li>
<li>Select <b>Enable</b> or <b>Disable</b> from the <b>Action</b> drop-down menu.</li>
</ol></body>
</html>