No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Basic Storage Service Configuration Guide for Block

OceanStor Dorado V3 Series V300R002

This document is applicable to OceanStor Dorado3000 V3, Dorado5000 V3, Dorado6000 V3, and Dorado18000 V3. It describes the basic storage services and explains how to configure and manage them.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Modifying an Initiator

Modifying an Initiator

This operation enables you to modify the properties of an initiator.

Prerequisites

You can configure the Uses third-party multipath software parameters only after an initiator has been associated with a host.

Procedure

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

    The Initiator Properties dialog box is displayed.

  3. Modify the properties of the initiator.

    Table 5-21 describes the related parameters for an iSCSI initiator when CHAP authentication is not enabled.

    Table 5-22 describes the related parameters for an iSCSI initiator when CHAP authentication is enabled.

    Table 5-23 describes the related parameters for non-iSCSI initiators.
    Table 5-21 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.
    • Can contain only letters, digits, periods (.), underscores (_), and hyphens (-).

    [Example]

    Initiator01

    Uses third-party multipath software

    • This parameter is displayed only after the initiator has been added to a host.
    • Select this parameter to use multipathing software not developed by Huawei. 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 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]

    Uses third-party multipath software

    Switchover Mode

    Path switchover mode.

    The system supports the following modes:

    • early-version ALUA: This mode is selected when:
      • The storage system is upgraded from V300R001C00 or V300R001C01 to V300R002C00 or later.
      • Before the upgrade, the storage system has enabled ALUA.
    • 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 HBA), or Windows Server 2008 (QLogic HBA).
    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]

    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.

    [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 Normal Authentication and Discovery Authentication.

    • If Enable CHAP authentication is selected, you must set CHAP Name and Password for the storage system. In addition, you must set the 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 and Password for the storage system.
    NOTE:

    The CHAP authentication parameters are valid only for iSCSI initiators.

    [Example]

    -

    Table 5-22 iSCSI initiator parameters (CHAP authentication enabled)

    Parameter

    Description

    Setting

    Alias

    An alternate name of the initiator.

    [Value range]

    The alias:

    • Can be left blank or contain up to 31 characters.
    • Can ontain only letters, digits, periods (.), underscores (_), and hyphens (-).

    [Example]

    Initiator01

    Uses third-party multipath software

    • This parameter is displayed only after the initiator has been added to a host.
    • Select this parameter to use multipathing software not developed by Huawei. 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 the host before you enable or disable this parameter, restart the host after configuring this parameter.
    • If UltraPath is installed on the host, you do not need to enable this parameter.

    [Example]

    Uses third-party multipath software

    Switchover Mode

    Path switchover mode.

    The system supports the following modes:

    • early-version ALUA: This mode is selected when:
      • The storage system is upgraded from V300R001C00 or V300R001C01 to V300R002C00 or later.
      • Before the upgrade, the storage system has ALUA enabled.
    • 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 HBA), or Windows Server 2008 (QLogic HBA).
    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]

    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.

    [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 a non-HyperMetro scenario, retain the default value Optimal Path.

    [Example]

    Optimal Path

    Enable CHAP authentication

    CHAP authentication includes Normal Authentication and Discovery 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 and 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 options 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

    Discovery authentication is a process during which the target and initiator set up connections. Authentication options include:

    • No authentication
    • Unidirectional authentication

      The target authenticates the 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 can contain 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 5-23 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.
    • Can contain only letters, digits, periods (.), underscores (_), and hyphens (-).

    [Example]

    Initiator01

    Uses third-party multipath software

    • This parameter is displayed only after the initiator has been added to a host.
    • Select this parameter to use multipathing software not developed by Huawei. 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 the host before you enable or disable this parameter, restart the host after configuring this parameter.
    • If UltraPath is installed on the host, you do not need to enable this parameter.

    [Example]

    Uses third-party multipath software

    Switchover Mode

    Path switchover mode.

    The system supports the following modes:

    • early-version ALUA: This mode is selected when:
      • The storage system must be upgraded from V300R001C00 or V300R001C01 to V300R002C00 or later.
      • Before the upgrade, the storage system has ALUA enabled.
    • 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 HBA), or Windows Server 2008 (QLogic HBA).
    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]

    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.

    [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

  4. Confirm the modification of the initiator's properties.

    1. Click OK.
      • If Uses third-party multipath software is modified:
        1. A security alert dialog box is displayed.
        2. Confirm the information in the dialog box and select I have read and understand the consequences associated with performing this operation.
        3. Click OK.

          The Success dialog box is displayed indicating that the operation is successful.

      • If Uses third-party multipath software is not modified:

        The Success dialog box is displayed indicating that the operation is successful.

    2. Click OK.

Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100049139

Views: 28194

Downloads: 213

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next