Creating an Initiator

Context

• In the scenario where initiators have been configured for a host:
  • If initiators can be automatically discovered on DeviceManager, skip operations in this section.
  • If initiators cannot be automatically discovered on DeviceManager, create initiators using the IQNs or WWPNs of the initiators configured for the host.
• If no initiator is configured for a host, configure initiators by following instructions in "Configuring Connectivity" in the Huawei SAN Storage Host Connectivity Guide for XXX and then add initiators on DeviceManager.
• On DeviceManager, set or modify parameters of initiators manually created or automatically discovered based on the multipathing software and host operating system version. For recommended parameter settings in different scenarios, see "Configuring Multipathing" in the Huawei SAN Storage Host Connectivity Guide for XXX. For iSCSI initiators, set CHAP authentication parameters based on the security authentication plan.
  • XXX represents a specific operating system, for example, Windows.
  • You can log in to Huawei's technical support website (https://support.huawei.com/enterprise/) and enter the product model + document name in the search box to search for, browse, and download a document.

Procedure

1. Log in to DeviceManager.
2. Choose Provisioning > Host > Initiator.
3. Click Create.

   The Create Initiator dialog box is displayed.

4. In Type, select an initiator type.
5. Set the properties of the initiator based on the initiator type.

   Table 5-15 describes related parameters about FC initiator.

   Table 5-15 FC initiator parameters

   Parameter	Description	Setting
   WWPN	World Wide Port Name (WWPN), unique identifier of an initiator.	[Value range] A WWPN is a hexadecimal value that contains 16 characters comprised of uppercase letters A to F, lowercase letters a to f, or digits 0 to 9, but cannot all be 0, F, or f. [Example] 2000000743abcdff
   Alias	Alias of an initiator.	[Value range] An alias: Can be left blank or contain up to 31 characters. Contains only letters, digits, periods (.), underscores (_), and hyphens (-). [Example] FC1_ALIAS
   Use third-party multipath software	Select Use third-party multipath software to use multipathing software not developed by the device provider. In the HyperMetro scenario, configure asymmetric logical unit access (ALUA) as described in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software. If LUNs have been mapped to a host before you enable or disable Use third-party multipath software, restart the host after configuring this parameter. If UltraPath is installed on a host, you do not need to select this option.	[Example] Use third-party multipath software
   Switchover Mode	Path switchover mode. The storage system supports the following modes: Common ALUA: This mode is selected when the OS of the host that connects to the storage system is SUSE, Red Hat 6.X, Windows Server 2012 (Emulex HBA), Windows Server 2008 (Emulex HBA), or HP-UX 11i V3. ALUA not used: This mode is selected when a host such as HP-UX 11i V2 does not support ALUA or the actual application scenario does not need ALUA. Special mode: This mode is selected when the OS of the host that connects to the storage system is VMware, AIX, Red Hat 7.X, Windows Server 2012 (QLogic HBAs), or Windows Server 2008 (QLogic HBAs). NOTICE: In HyperMetro scenarios, set this parameter with the guidance of Huawei technical support engineers and follow the requirements in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software. NOTE: ALUA is a multi-target port access model. If multiple paths exist, the ALUA model provides a way of presenting active/passive LUNs to a host, and offers a port status switching interface to switch over the working controller. For example, when a host multipathing program supporting ALUA detects a port status change on a controller that becomes faulty, the program will automatically switch subsequent I/Os to another controller.	[Example] Common ALUA
   Special mode type	This parameter must be configured if Switchover Mode is set to Special mode. The detailed requirements are as follows: Mode 0: The host and storage system must be connected using a Fibre Channel network. The OS of the host that connects to the storage system is Red Hat 7.X, Windows Server 2012 (QLogic HBAs), or Windows Server 2008 (QLogic HBAs). Mode 1: The OS of the host that connects to the storage system is AIX or VMware. In the HyperMetro scenario, HyperMetro is in load balancing mode. Mode 2: The OS of the host that connects to the storage system is AIX or VMware. In the HyperMetro scenario, HyperMetro is in local preferred mode. Mode 3: The OS of the host that connects to the storage system is Linux or Solaris. HyperMetro is in local preferred mode. NOTICE: In HyperMetro scenarios, set this parameter with the guidance of Huawei technical support engineers and follow the requirements in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software.	[Example] Mode 0
   Path Type	In the HyperMetro scenario, the storage system supports two path switchover modes: Optimal Path and Non-Optimal Path. When HyperMetro is in load balancing mode, set Path Type for the initiators of both the local and remote storage systems to Optimal Path. Enable ALUA on both the host and storage systems. If the host uses the round-robin multipathing policy, it delivers I/Os to both storage systems in round-robin mode. When HyperMetro is in local preferred mode, set Path Type for the initiator of the local storage system to Optimal Path, and that of the remote storage system to Non-Optimal Path. Enable ALUA on both the host and storage systems. The host delivers I/Os to the local storage system preferentially. In the non-HyperMetro scenario, retain the default value Optimal Path.	[Example] Optimal Path

   Table 5-16 describes iSCSI initiator parameters.

   Table 5-16 iSCSI initiator parameters

   Parameter	Description	Setting
   IQN	iSCSI Qualified Name (IQN) of an iSCSI initiator. NOTE: The initiator IQN must be the same as the one on the application server. The IQN of each initiator must be unique. Do not configure the initiators of multiple application servers with the same IQN.	[Value range] An IQN must contain 1 to 223 characters. [Example] iqn.1991-05.com.microsoft:host-name
   Alias	Alias of an iSCSI initiator.	[Value range] An alias: Can be left blank or contain up to 31 characters. Contains only letters, digits, periods (.), underscores (_), and hyphens (-). [Example] -
   Use third-party multipath software	Select Use third-party multipath software to use multipathing software not developed by the device provider. In the HyperMetro scenario, configure ALUA as described in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software. If LUNs have been mapped to a host before you enable or disable Use third-party multipath software, restart the host after configuring this parameter. If UltraPath is installed on a host, you do not need to enable this parameter.	[Example] Use third-party multipath software
   Switchover Mode	Path switchover mode. The system supports the following modes: Common ALUA: This mode is selected when the OS of the host that connects to the storage system is SUSE, Red Hat 6.X, Windows Server 2012 (Emulex HBA), Windows Server 2008 (Emulex HBA), or HP-UX 11i V3. ALUA not used: This mode is selected when a host such as HP-UX 11i V2 does not support ALUA or the actual application scenario does not need ALUA. Special mode: This mode is selected when the OS of the host that connects to the storage system is VMware, AIX, Red Hat 7.X, Windows Server 2012 (QLogic HBAs), or Windows Server 2008 (QLogic HBAs). NOTICE: In HyperMetro scenarios, set this parameter with the guidance of Huawei technical support engineers and follow the requirements in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software. NOTE: ALUA is a multi-target port access model. If multiple paths exist, the ALUA model provides a way of presenting active/passive LUNs to a host, and offers a port status switching interface to switch over the working controller. For example, when a host multipathing program supporting ALUA detects a port status change on a controller that becomes faulty, the program will automatically switch subsequent I/Os to another controller.	[Example] Common ALUA
   Special mode type	This parameter must be configured if Switchover Mode is set to Special mode. The detailed requirements are as follows: Mode 0: The host and storage system must be connected using a Fibre Channel network. The OS of the host that connects to the storage system is Red Hat 7.X, Windows Server 2012 (QLogic HBAs), or Windows Server 2008 (QLogic HBAs). Mode 1: The OS of the host that connects to the storage system is AIX or VMware. In the HyperMetro scenario, HyperMetro is in load balancing mode. Mode 2: The OS of the host that connects to the storage system is AIX or VMware. In the HyperMetro scenario, HyperMetro is in local preferred mode. Mode 3: The OS of the host that connects to the storage system is Linux or Solaris. HyperMetro is in local preferred mode. NOTICE: In HyperMetro scenarios, set this parameter with the guidance of Huawei technical support engineers and follow the requirements in the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software.	[Example] Mode 0
   Path Type	In the HyperMetro scenario, the storage system supports two path switchover modes: Optimal Path and Non-Optimal Path. When HyperMetro is in load balancing mode, set Path Type for the initiators of both the local and remote storage systems to Optimal Path. Enable ALUA on both the host and storage systems. If the host uses the round-robin multipathing policy, it delivers I/Os to both storage systems in round-robin mode. When HyperMetro is in local preferred mode, set Path Type for the initiator of the local storage system to Optimal Path, and that of the remote storage system to Non-Optimal Path. Enable ALUA on both the host and storage systems. The host delivers I/Os to the local storage system preferentially. In the non-HyperMetro scenario, retain the default value Optimal Path.	[Example] Optimal Path
   Enable CHAP authentication	CHAP authentication includes Discovery Authentication and Normal Authentication. If Enable CHAP authentication is selected, you must set CHAP name and Password for the storage system. In addition, you must set CHAP name and Password on the application server for it to access the storage system. If Enable CHAP authentication is not selected, you do not need to set CHAP name or Password for the storage system.	[Example] -
   Normal Authentication	Authentication mode in the process during which the target and initiator transmit data between each other after connections are set up. Authentication modes include: No authentication Unidirectional authentication The target authenticates the initiator. Bidirectional authentication The target and initiator authenticate each other.	[Default Value] Unidirectional authentication
   Discovery Authentication	Authentication mode in the process during which the target and initiator are setting up connections. Authentication modes include: No authentication Unidirectional authentication The target authenticates the initiator. Bidirectional authentication The target and initiator authenticate each other.	[Default Value] No authentication
   CHAP name	User name for CHAP authentication. NOTE: The name contains 4 to 223 characters. The name only contains letters, digits or special characters. Special characters are: !"#$&%'()*+,-./:;<=>?@[\]^_`{|}~ The first character must be a letter or digit.	[Example] admin
   Password	Password for CHAP authentication. The password contains 12 to 16 characters. The password must contain three of the following four types of characters: Uppercase letters Lowercase letters Digits Special characters (including space) !"#$&%'()*+,-./:;<=>?@[\]^_`{|}~ The password must not be the same as the user name or the reverse of the user name.	[Example] Admin@123456789
   Confirm Password	Password for CHAP authentication.	[Value range] The value of Confirm Password must be consistent with that of Password. [Example] -
   Match Type	To configure this parameter, click Advanced. IQN match policy to match online idle iSCSI initiators with the current initiator. After the matching is successful, the idle iSCSI initiators can automatically associate with the host of the current initiator. NOTE: This parameter applies to V500R007C60SPC200 and later versions.	[Value range] Default General match Keyword match

6. Click OK.

   The Success dialog box is displayed, indicating that the operation succeeded.

7. Click OK.