FC target assigned to pool properties - Revision history

Pa-P: 1 revision

2021-12-03T13:27:40Z

1 revision

← Older revision	Revision as of 13:27, 3 December 2021
(No difference)

Ma-W at 10:24, 12 March 2020

2020-03-12T10:24:37Z

← Older revision		Revision as of 10:24, 12 March 2020
Line 1:		Line 1:
	The article describes how to assign FC target to pool properties when using HA cluster or single node configuration. In general, this function allows modifying target alias and assigning a remote target. In addition, if you would like to learn about FC target replacement, read this article: [http://wiki.scalelogicinc.com/nx2/FC_target_replacement http://wiki.scalelogicinc.com/nx2/FC_target_replacement]

	~~== High Availability cluster configuration ==~~

	Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In a cluster environment, when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. To properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.

	The cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. The initiator accesses LUNs by using an active path and a standby path is used for a target that doesn’t have access to LUNs. The active path is set for a target, when the pool is present on the same node where the target is. The standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, the ALUA configuration is not created by a cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs the configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after the cluster is started, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after the assignment of a remote target, please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite the modification of path statuses.

	~~<br/>In summary, to correctly set up targets for a cluster usage, do the following:~~

	*Select a remote target for each target assigned to FC groups.
	*Switch a selected remote target on a remote node to a target mode.

	~~== Single node configuration ==~~

	There is no possibility to pair the target with a remote node because ALUA is not used. In case when the pool is imported with an FC configuration from another machine, it is neccessary to assign FC targets to FC ports of the current server. This is due to the fact that the system is unable to determine on which ports it has to share resources.		There is no possibility to pair the target with a remote node because ALUA is not used. In case when the pool is imported with an FC configuration from another machine, it is neccessary to assign FC targets to FC ports of the current server. This is due to the fact that the system is unable to determine on which ports it has to share resources.

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

Ma-W at 10:22, 12 March 2020

2020-03-12T10:22:32Z

← Older revision		Revision as of 10:22, 12 March 2020
Line 1:		Line 1:
	~~This~~ function allows modifying target alias and ~~assign~~ a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In ~~cluster environment when a pool has to be moved to other node~~, ~~it is is required~~ to ~~know which~~ target ~~should be used there to serve FC groups resources~~. ~~In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups~~.		The article describes how to assign FC target to pool properties when using HA cluster or single node configuration. In general, this function allows modifying target alias and assigning a remote target. In addition, if you would like to learn about FC target replacement, read this article: [http://wiki.scalelogicinc.com/nx2/FC_target_replacement http://wiki.scalelogicinc.com/nx2/FC_target_replacement]

	<br/>Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster ~~moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA~~ configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.		== High Availability cluster configuration ==

			Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In a cluster environment, when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. To properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.

	In summary, to correctly set up targets for cluster ~~use it is required to~~:		The cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. The initiator accesses LUNs by using an active path and a standby path is used for a target that doesn’t have access to LUNs. The active path is set for a target, when the pool is present on the same node where the target is. The standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, the ALUA configuration is not created by a cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs the configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after the cluster is started, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after the assignment of a remote target, please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite the modification of path statuses.

			<br/>In summary, to correctly set up targets for a cluster usage, do the following:

	*Select a remote target for each target assigned to FC groups.		*Select a remote target for each target assigned to FC groups.
	*Switch a selected remote target on remote node to target mode.		*Switch a selected remote target on a remote node to a target mode.

			== Single node configuration ==

			There is no possibility to pair the target with a remote node because ALUA is not used. In case when the pool is imported with an FC configuration from another machine, it is neccessary to assign FC targets to FC ports of the current server. This is due to the fact that the system is unable to determine on which ports it has to share resources.

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

Ma-W: 1 revision

2019-03-28T13:46:41Z

1 revision

← Older revision	Revision as of 13:46, 28 March 2019
(No difference)

Ma-W at 14:43, 27 March 2019

2019-03-27T14:43:31Z

← Older revision		Revision as of 14:43, 27 March 2019
Line 1:		Line 1:
	~~<span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">~~This function allows modifying target alias and assign a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In cluster environment when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.~~</span>~~<br/~~><br/><span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;"~~>Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.~~</span><br/><br/><span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;">~~In summary, to correctly set up targets for cluster use it is required to:~~</span>~~		This function allows modifying target alias and assign a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In cluster environment when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.
	~~<ul style="margin-top:0pt;margin-bottom:0pt;">~~
	~~<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">~~Select a remote target for each target assigned to FC groups.~~</span></li>~~		<br/>Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.
	~~<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">~~Switch a selected remote target on remote node to target mode.~~</span></li>~~
	~~</ul>~~
			In summary, to correctly set up targets for cluster use it is required to:

			*Select a remote target for each target assigned to FC groups.
			*Switch a selected remote target on remote node to target mode.

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

migrate>Mi-S at 12:13, 15 June 2018

2018-06-15T12:13:36Z

← Older revision		Revision as of 12:13, 15 June 2018
Line 1:		Line 1:
	<span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">This function allows modifying target alias and assign a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In cluster environment when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.</span>		<span style="font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">This function allows modifying target alias and assign a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In cluster environment when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.</span><br/><br/><span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;">Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.</span><br/><br/><span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;">In summary, to correctly set up targets for cluster use it is required to:</span>

	<span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;">Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.</span>

	<span style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; font-size: 11pt; white-space: pre-wrap;">In summary, to correctly set up targets for cluster use it is required to:</span>
	<ul style="margin-top:0pt;margin-bottom:0pt;">		<ul style="margin-top:0pt;margin-bottom:0pt;">
	<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Select a remote target for each target assigned to FC groups.</span></li>		<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Select a remote target for each target assigned to FC groups.</span></li>
	<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Switch a selected remote target on remote node to target mode.~~<br/>[[Category:Help topics]]~~</span></li>		<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Switch a selected remote target on remote node to target mode.</span></li>
	</ul>		</ul>

			[[Category:Help topics]]

migrate>Mi-S at 11:19, 15 June 2018

2018-06-15T11:19:25Z

← Older revision		Revision as of 11:19, 15 June 2018
Line 6:		Line 6:
	<ul style="margin-top:0pt;margin-bottom:0pt;">		<ul style="margin-top:0pt;margin-bottom:0pt;">
	<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Select a remote target for each target assigned to FC groups.</span></li>		<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Select a remote target for each target assigned to FC groups.</span></li>
	<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Switch a selected remote target on remote node to target mode.</span></li>		<li><span style="font-size: 11pt; background-color: transparent; vertical-align: baseline; white-space: pre-wrap;">Switch a selected remote target on remote node to target mode.<br/>[[Category:Help topics]]</span></li>
	</ul>		</ul>

migrate>Mi-S: Created page with "This function allows mo..."

2018-06-15T10:22:39Z

Created page with "This function allows mo..."

New page

This function allows modifying target alias and assign a remote target. Configuration of the remote target is crucial for a correct FC cluster configuration. FC targets are local to a particular machine because in general those are the physical ports from adapters attached to a given server. In cluster environment when a pool has to be moved to other node, it is is required to know which target should be used there to serve FC groups resources. In order to properly configure FC for a cluster use, it is required to assign a remote target to each of local targets present in FC groups.

Cluster uses Asymmetric Logical Unit Access (ALUA) to configure the paired targets. LUNs are visible on both configured targets by the initiator that has access to those LUNs by paths. Depending on the path status, the initiator knowns which path should be used to access LUNs. Initiator accesses LUNs by using an active path and standby path is used for a target that doesn’t have access to LUNs. Active path is set for a target, when the pool is present on the same node where the target is. Standby path is used for a target, when a pool is present on the other node. When a cluster moves the pool from one node to another,  path statuses are modified accordingly. If the remote target is not configured, ALUA configuration is not created by cluster on the remote node. In that case, after moving the pool, all resources served by that target won’t be accessible. Once the remote target is assigned, the cluster performs configuration of ALUA and a given target can be safely used by both cluster nodes. It is possible to assign the remote target before or after cluster start, but it is necessary to make sure that it is configured before the move of pool is performed (either manually or by failover). Moreover, after assignment of remote target please make sure that it is in the target mode on the remote node. If the remote target will be in an initiator mode, it won’t be possible to access target LUNs after a pool move, despite modification of path statuses.

In summary, to correctly set up targets for cluster use it is required to:
<ul style="margin-top:0pt;margin-bottom:0pt;">
<li>Select a remote target for each target assigned to FC groups.</li>
<li>Switch a selected remote target on remote node to target mode.</li>
</ul>