Modifying Initiator Properties

Procedure

1. Log in to DeviceManager.
2. Choose Provisioning > Host > Initiator.
3. Select the initiator whose properties you want to modify and click Properties.

   The Initiator Properties dialog box is displayed.

   GUIs may vary with product versions and models. The actual GUIs prevail.

4. Modify the properties of the initiator.

   Table 7-16 describes the parameters for an iSCSI initiator when CHAP authentication is not enabled.

   Table 7-17 describes the parameters for an iSCSI initiator when CHAP authentication is enabled.

   Table 7-18 describes the parameters for non-iSCSI initiators.

   Table 7-16 iSCSI initiator parameters (CHAP authentication not enabled)

   Parameter	Description	Setting
   Alias	An alternate name of the initiator.	[Value range] An alias: Can be left blank or contain up to 31 characters. Contains only letters, digits, periods (.), underscores (_), and hyphens (-). [Example] Initiator01
   Use third-party multipath software	This parameter is only available after the initiator is added for the host successfully. 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 this parameter, 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. NOTE: The CHAP authentication parameters are valid only for iSCSI initiators.	[Example] -

   Table 7-17 iSCSI initiator parameters (CHAP authentication enabled)

   Parameter	Description	Setting
   Alias	An alternate name of the initiator.	[Value range] An alias: Can be left blank or contain up to 31 characters. Contains only letters, digits, periods (.), underscores (_), and hyphens (-). [Example] Initiator01
   Use third-party multipath software	This parameter is only available after the initiator is added for the host successfully. 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 the host, you do not need to enable Use third-party multipath software.	[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. NOTE: The CHAP authentication parameters are valid only for iSCSI initiators.	[Example] -
   Normal Authentication	Normal authentication is a process during which the target and initiator transmit data between each other after connections are set up. Authentication includes: No authentication Unidirectional authentication The target authenticates the initiator. Bidirectional authentication The target and initiator authenticate each other.	[Default Value] Unidirectional authentication
   Discovery Authentication	Discovery authentication is a process during which the target and initiator set up connections. Authentication includes: No authentication Unidirectional authentication The target authenticates initiator. Bidirectional authentication The target and initiator authenticate each other.	[Default Value] No authentication
   Old Password	Old password for CHAP authentication NOTE: Click Modify next to Password to modify the CHAP authentication password.	[Example] -
   New Password	New 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] -
   Confirm Password	Password for CHAP authentication.	[Value range] The value of Confirm Password must be consistent with that of New Password. [Example] -

   Table 7-18 Non-iSCSI initiator parameters

   Parameter	Description	Setting
   Alias	An alternate name of the initiator.	[Value range] An alias: Can be left blank or contain up to 31 characters. Contains only letters, digits, periods (.), underscores (_), and hyphens (-). [Example] Initiator01
   Use third-party multipath software	This parameter is only available after the initiator is added for the host successfully. 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 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 the host, you do not need to enable Use third-party multipath software.	[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

5. Confirm the modification of the initiator's properties.
   1. Click OK.

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

   2. Click OK.