Add iSCSI target - Revision history

migrate>Ra-N at 09:48, 22 November 2019

2019-11-22T09:48:28Z

← Older revision		Revision as of 09:48, 22 November 2019
Line 3:		Line 3:
	'''1. Target Name'''		'''1. Target Name'''
	<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div>'''Note:'''</div>		<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div>'''Note:'''</div>
	The server name will be used as a part of the default target name.		The server name will be used as a part of the default target name. Before using the target, you need to add at least one LUN to it.

	Before using the target you need to add at least one LUN to it.

	'''2. Zvols'''		'''2. Zvols'''

migrate>Ra-N at 09:47, 22 November 2019

2019-11-22T09:47:55Z

← Older revision		Revision as of 09:47, 22 November 2019
Line 2:		Line 2:

	'''1. Target Name'''		'''1. Target Name'''
	<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div>~~<br/></div>~~		<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div>'''Note:'''</div>
	'''Note:'''

	The server name will be used as a part of the default target name.		The server name will be used as a part of the default target name.

migrate>Ra-N at 09:47, 22 November 2019

2019-11-22T09:47:10Z

← Older revision		Revision as of 09:47, 22 November 2019
Line 16:		Line 16:
	*'''Size'''		*'''Size'''
	*'''SCSI ID ''' - You can change the SCSI ID. To change it, double-click on the value of SCSI ID for the target.		*'''SCSI ID ''' - You can change the SCSI ID. To change it, double-click on the value of SCSI ID for the target.
	*'''LUN '''- You can define the LUN number. To change it, double-click on the value of the LUN for the target.
			'''Note''': Some virtual environments register the SCSI ID in the Virtual Machine configuration file. Changing SCSI ID will require to remove VMs from the inventory and the next new register into the VM inventory. This is why the SCSI ID can be changed only in an emergency case in order to re-mount volume with new credentials.

			*'''LUN '''- You can define the LUN number. To change it, double-click on the value of the LUN for the target.<br/>'''Note''': Some initiators require LUN 0 for discovery, this is why it is strongly recommended to use default LUN numbers.
	*'''Access Mode - '''You can choose between the '''READ-WRITE (DEFAULT) '''and '''READ-ONLY. '''		*'''Access Mode - '''You can choose between the '''READ-WRITE (DEFAULT) '''and '''READ-ONLY. '''

migrate>Ra-N at 09:43, 22 November 2019

2019-11-22T09:43:43Z

← Older revision		Revision as of 09:43, 22 November 2019
Line 3:		Line 3:
	'''1. Target Name'''		'''1. Target Name'''
	<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div><br/></div>		<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div><br/></div>
	'''Note~~ ~~:'''		'''Note:'''

	The server name will be used as a part of the default target name.		The server name will be used as a part of the default target name.

migrate>Ra-N at 09:43, 22 November 2019

2019-11-22T09:43:23Z

← Older revision		Revision as of 09:43, 22 November 2019
Line 2:		Line 2:

	'''1. Target Name'''		'''1. Target Name'''
	<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre> iqn.2019-11.iscsi:node-220.target0</pre><div><br/></div>		<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre>iqn.2019-11.iscsi:node-220.target0</pre><div><br/></div>
	'''Note :'''		'''Note :'''

migrate>Ra-N at 09:43, 22 November 2019

2019-11-22T09:43:13Z

← Older revision		Revision as of 09:43, 22 November 2019
Line 2:		Line 2:

	'''1. Target Name'''		'''1. Target Name'''
	<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre> ~~<samp>~~ iqn.2019-11.iscsi:node-220.target0~~</samp>~~</pre><div><br/></div>		<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre> iqn.2019-11.iscsi:node-220.target0</pre><div><br/></div>
	'''Note :'''		'''Note :'''

migrate>Ra-N at 09:42, 22 November 2019

2019-11-22T09:42:49Z

← Older revision		Revision as of 09:42, 22 November 2019
Line 2:		Line 2:

	'''1. Target Name'''		'''1. Target Name'''
			<div>iSCSI uses a special and unique name to identify an iSCSI target. The iSCSI naming requirements can be found on IETF Web site (see RFC 3721 and RFC 3722). A target name may contain alphanumeric characters but lower case only. Every character entered will be converted to lower case. No spaces or underscores are permitted. Some initiators require strict IQN format in the following form:<br/></div><pre>iqn.yyyy-mm.naming-authority:unique name</pre><div>This is way it is strongly recommended to follow the standard. An example of a proper target name is presented below:</div><pre> <samp> iqn.2019-11.iscsi:node-220.target0</samp></pre><div><br/></div>
	~~Enter the desired~~ target ~~name, or generate default name~~. ~~Target~~ name may contain alphanumeric characters~~: . : - and is considered~~ case~~-insensitive~~. Every character entered will be converted to lower case. No spaces or underscores are permitted.

	'''Note :'''		'''Note :'''

Ma-W at 15:18, 13 February 2019

2019-02-13T15:18:11Z

← Older revision		Revision as of 15:18, 13 February 2019
Line 35:		Line 35:
	*'''Enable target IP access restrictions'''		*'''Enable target IP access restrictions'''

	~~''''''~~It is possible to assign network classes or specify individual IP addresses that are permitted or denied to access the target. Entries should be delimited by semicolons. Allow access field has higher priority than Deny access field. In order to completely block access, type address 0.0.0.0/0 in Deny field.		It is possible to assign network classes or specify individual IP addresses that are permitted or denied to access the target. Entries should be delimited by semicolons. Allow access field has higher priority than Deny access field. In order to completely block access, type address 0.0.0.0/0 in Deny field.

	'''4. Summary'''		'''4. Summary'''

Ma-W at 15:15, 13 February 2019

2019-02-13T15:15:33Z

← Older revision		Revision as of 15:15, 13 February 2019
Line 3:		Line 3:
	'''1. Target Name'''		'''1. Target Name'''

	Enter the desired target name, or generate default name.~~ <span style="color: rgb(0, 0, 0); font-family: undefined, sans-serif; font-size: 13px; line-height: 19.200000762939453px">~~Target name may contain alphanumeric characters: . : - and is considered case-insensitive. Every character entered will be converted to lower case. No spaces or underscores are permitted.~~</span>~~		Enter the desired target name, or generate default name. Target name may contain alphanumeric characters: . : - and is considered case-insensitive. Every character entered will be converted to lower case. No spaces or underscores are permitted.

	'''~~<span style="color: rgb(0, 0, 0); font-family: undefined, sans-serif; font-size: 13px; line-height: 19.200000762939453px">~~Note :~~</span>~~'''		'''Note :'''

	~~<span style="color: rgb(0, 0, 0); font-family: undefined, sans-serif; font-size: 13px; line-height: 19.200000762939453px">~~The server name will be used as a part of the default target name.~~</span>~~		The server name will be used as a part of the default target name.

	~~<span style="color: rgb(0, 0, 0); font-family: undefined, sans-serif; font-size: 13px; line-height: 19.200000762939453px">~~Before using the target you need to add at least one LUN to it.~~</span>~~		Before using the target you need to add at least one LUN to it.

	'''2. Zvols'''		'''2. Zvols'''
Line 21:		Line 21:
	*'''Access Mode - '''You can choose between the '''READ-WRITE (DEFAULT) '''and '''READ-ONLY. '''		*'''Access Mode - '''You can choose between the '''READ-WRITE (DEFAULT) '''and '''READ-ONLY. '''

	~~<span style="color: rgb(0, 0, 0)">~~If set to '''read-only, ''' zvol will be created in read-only mode with the following restrictions:~~</span>~~		If set to '''read-only, ''' zvol will be created in read-only mode with the following restrictions:
	~~<ul style="margin-left: 40px;">~~
	~~<li><span style="color: rgb(0, 0, 0)">~~Properties cannot be changed~~</span><span style="color: rgb(0, 0, 0)">~~.~~</span></li>~~		*Properties cannot be changed.
	~~</ul>~~

	If no zvols are displayed, you can create a new zvol by clicking '''Add New Zvol. '''You will be moved to the '''Create new Zvol '''Wizard.		If no zvols are displayed, you can create a new zvol by clicking '''Add New Zvol. '''You will be moved to the '''Create new Zvol '''Wizard.
Line 36:		Line 35:
	*'''Enable target IP access restrictions'''		*'''Enable target IP access restrictions'''

	''''''~~<span style="color: rgb(102, 102, 102); font-family: arial; font-size: 11px; line-height: 13px">~~It is possible to assign network classes or specify individual IP addresses that are permitted or denied to access the target. Entries should be delimited by semicolons. Allow access field has higher priority than Deny access field. In order to completely block access, type address 0.0.0.0/0 in Deny field.~~</span>~~		''''''It is possible to assign network classes or specify individual IP addresses that are permitted or denied to access the target. Entries should be delimited by semicolons. Allow access field has higher priority than Deny access field. In order to completely block access, type address 0.0.0.0/0 in Deny field.

	'''4. Summary'''		'''4. Summary'''
Line 44:		Line 43:


	'''''~~<span>~~Video tutorial related to this article~~</span>~~'''''		'''''Video tutorial related to this article'''''

	{{#ev:youtube\|4cT22REyVuM}}		{{#ev:youtube\|4cT22REyVuM}}

	[[Category:Help topics]]		[[Category:Help topics]]

migrate>To-K: To-K moved page Add target to Add iSCSI target

2018-09-12T10:26:41Z

To-K moved page Add target to Add iSCSI target

← Older revision	Revision as of 10:26, 12 September 2018
(No difference)