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).
Creating an Initiator

Creating an Initiator

This operation enables you to create an initiator for a storage device.

Context

  • If initiators have been configured for the 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, you can set CHAP authentication parameters based on the security authentication plan.
NOTE:
  • 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 documents.

Procedure

  1. Choose Provisioning > Host > Initiator.
  2. Click Create.

    The Create Initiator dialog box is displayed.

  3. In Type, select an initiator type.

    NOTE:

    The initiator types include:

    • iSCSI
    • FC
    • IB

  4. Set the properties of the initiator based on the initiator type.

    Table 4-16 describes parameters related to FC or IB initiators.

    Table 4-16 FC or IB initiator parameters

    Parameter

    Description

    Setting

    WWPN

    Unique identifier of an initiator.

    [Value range]

    A WWPN is a hexadecimal value that contains 16 characters. It can contain the letters A to F (uppercase and lowercase) and digits 0 to 9. It cannot be all 0, all F, or all f.

    [Example]

    2000000743abcdff

    Alias

    Alias of an 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]

    FC1_ALIAS

    Uses third-party multipath software

    • 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 the host, you do not need to enable this parameter.

    [Example]

    Uses third-party multipath software

    Switchover Mode

    Path switchover mode.

    The storage 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 of HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software.

    NOTE:

    Asymmetric logical unit access (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 redirect subsequent I/Os to the other 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 HBA), or Windows Server 2008 (QLogic HBA).
    • 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

    Table 4-17 describes iSCSI initiator parameters.

    Table 4-17 iSCSI initiator parameters

    Parameter

    Description

    Setting

    IQN

    iSCSI Qualified Name (IQN) of an iSCSI initiator.

    NOTE:

    The initiator IQN must be the same as that on 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.
    • Can contain only letters, digits, periods (.), underscores (_), and hyphens (-).

    [Example]

    -

    Uses third-party multipath software

    • This parameter is displayed only after the initiator has been successfully 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 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 of HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software.

    NOTE:

    Asymmetric logical unit access (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 redirect subsequent I/Os to the other 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 HBA), or Windows Server 2008 (QLogic HBA).
    • 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 the 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 and Password for the storage system.

    [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 options 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 can contain 4 to 223 characters.
    • The name can contain only letters, digits, and the following special characters:

      !"#$&%'()*+,-./:;<=>?@[\]^_`{|}~

    • The first character must be a letter or digit.

    [Example]

    admin

    Password

    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 user name spelt backwards.

    [Example]

    Admin@123456789

    Confirm password

    Password for CHAP authentication.

    [Value range]

    The value of Confirm password must be consistent with that of Password.

    [Example]

    -

  5. Click OK.

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

  6. Click OK.
Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100049139

Views: 30964

Downloads: 226

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