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

OceanStor 2600 V3 Storage System V300R005 HyperMetro Feature Guide 06

"This document describes the implementation principles and application scenarios of theHyperMetro feature. Also, it explains how to configure and manage HyperMetro."
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).
Configure a Multipathing Policy for Host

Configure a Multipathing Policy for Host

This section describes how to configure the Multipathing software.

Context

Multipathing software must be installed for the HyperMetro solution. You can use either Huawei UltraPath or third-party multipathing software.

  • In terms of multipathing, UltraPath is recommended for HyperMetro. UltraPath can identify host locations so that hosts can access the nearest storage array, reducing cross-site accesses and latency while improving access efficiency and storage performance.
  • If the customer needs to use third-party multipathing software on the application server, the function of Uses third-party multipath software for initiators must be enabled on Huawei storage.

Configuring an UltraPath Policy for Host

This section describes how to configure the UltraPath software. For HyperMetro, the UltraPath software is configured to improve the I/O processing efficiency and reduce the access latency.

Context

In UltraPath, the local storage array is granted with the prior read and write permission. The local storage array is preferentially used to process host services. If the local storage array malfunctions, the remote storage array will be used. In this way, service response efficiency is improved and access latency is reduced.

UltraPath must be configured on all application servers.

When configuring UltraPath, ensure that Uses third-party multipath software is disabled as it is not needed.

NOTE:

For details about how to disable Uses third-party multipath software, see section Configuring an OS Native Multipathing Policy.

Procedure
  1. Set the HyperMetro working mode.

    The commands for setting the HyperMetro working mode vary with OSs on application servers.

    • For Linux, Windows, AIX, and Solaris OSs,
      1. Log in to the application server.
      2. Log in to the CLI of OceanStor UltraPath.
        • In Linux OSs, run upadmin to log in to the CLI of OceanStor UltraPath.
        • In Windows, AIX, and Solaris OSs, run upadm to log in to the CLI of OceanStor UltraPath.
      3. Run set hypermetro workingmode={ priority | balance } primary_array_id=ID [vlun_id={ ID | ID1,ID2... | ID1-ID2 } ]. Table 2-31 describes the key parameters in the command.
    Table 2-31 Parameter description

    Keyword and Parameter

    Description

    Default Value

    workingmode={ priority | balance }

    Used to specify the HyperMetro working mode.

    • priority: preferred storage array mode
    • balance: load balancing mode

    priority

    priority is recommended. balance is applicable to scenarios where the two active-active data centers are in the same building.

    primary_array_id=ID

    ID of the preferred storage array. The ID is allocated by UltraPath. The storage array in the data center in which the application hosts reside is selected.

    Run the command to obtain the ID of the storage array:

    • Linux: upadmin show array
    • Windows/AIX/Solaris: upadm show array
    NOTE:
    • When workingmode is set to priority, the value of the parameter indicates the storage array to which I/Os are preferentially delivered.
    • When workingmode is set to balance, the value of the parameter indicates the storage array where the first slice section resides.

    None

    NOTE:

    Mapping relationship between application hosts and storage arrays:

    • If the preferred storage array is configured for all application hosts in data center A, select storage array A.
    • If the preferred storage array is configured for all application hosts in data center B, select storage array B.

    vlun_id={ ID | ID1,ID2... | ID1-ID2 }

    ID of a virtual HyperMetro LUN. The ID is allocated by UltraPath.

    Run show vlun type=hypermetro to obtain the ID of a virtual HyperMetro LUN.

    None

    Instruction for Use

    This command is used to set the HyperMetro working mode of storage arrays and virtual LUNs. For example:

    • To set the HyperMetro working mode of an array to priority and specify the ID of the preferred storage array to 0, run set hypermetro workingmode=priority primary_array_id=0.
    • To set the HyperMetro working mode of virtual LUN 0 to balance and specify array 0 as the storage array where the first slice section resides, run set hypermetro workingmode=balance primary_array_id=0 vlun_id=0.

      The HyperMetro working mode of a virtual LUN has a higher priority than that set for all storage systems. To obtain better performance, you are advised to set the HyperMetro working mode for arrays only.

    • For vSphere OSs,
      1. Log in to the application server.
      2. Run esxcli upadm to log in to the CLI of OceanStor UltraPath.
      3. Run set hypermetro workingmode -m mode -p primary_array_id [-l vlun_id]. Table 2-32 describes the key parameters in the command.
    Table 2-32 Parameter description

    Keyword and Parameter

    Description

    Default Value

    -m mode

    Used to specify the HyperMetro working mode.

    • priority: preferred storage array mode
    • balance: load balancing mode

    priority

    priority is recommended. balance is applicable to scenarios where the two active-active data centers are in the same building.

    -p primary_array_id

    ID of the preferred storage array. The ID is allocated by UltraPath. The storage array in the data center in which the application hosts reside is selected.

    Run esxcli upadm show diskarray to obtain the ID of the storage array.

    NOTE:
    • When -m is set to priority, the value of the parameter indicates the storage array to which I/Os are preferentially delivered.
    • When -m is set to balance, the value of the parameter indicates the storage array where the first slice section resides.

    None

    NOTE:

    Mapping relationship between application hosts and storage arrays:

    • If the preferred storage array is configured for all application hosts in data center A, select storage array A.
    • If the preferred storage array is configured for all application hosts in data center B, select storage array B.

    [-l vlun_id]

    ID of a virtual HyperMetro LUN. The ID is allocated by UltraPath.

    Run show vlun type=hypermetro to obtain the ID of a virtual HyperMetro LUN.

    None

    Instruction for Use

    This command is used to set the HyperMetro working mode of storage arrays and virtual LUNs. For example:

    • To set the HyperMetro working mode of an array to priority and specify the ID of the preferred storage array to 0, run set hypermetro -m priority -p 0.
    • To set the HyperMetro working mode of virtual LUN 0 to balance and specify array 0 as the storage array where the first slice section resides, run set hypermetro -m balance -p 0 -l 0.

      The HyperMetro working mode of a virtual LUN has a higher priority than that set for all storage systems. To obtain better performance, you are advised to set the HyperMetro working mode for arrays only.

  2. Check whether the configuration succeeds.

    To check whether the configuration succeeds, run the command based on the operating system type:

    • Linux: upadmin show upconfig
    • Windows/AIX/Solaris: upadm show upconfig
    • vSphere: esxcli upadm show upconfig
    NOTE:

    In Linux, add the upadmin prefix to a command to log in to the CLI of OceanStor UltraPath. In Windows/AIX/Solaris, add the upadm prefix to a command to log in to the CLI of OceanStor UltraPath. In vSphere, add the esxcli upadm prefix to a command to log in to the CLI of OceanStor UltraPath.

    If the following command output is displayed, the configuration is successful. Otherwise, execute configuration again. Figure 2-21 shows the command output in vSphere as an example.

    HyperMetro WorkingMode : read write within primary array
    Figure 2-21 Querying UltraPath configurations

  3. Optional: (for vSphere) Enable the APD to PDL function of ESXi hosts.

    NOTE:
    • The APD to PDL function is disabled by default.
    • You do not need to enable APD to PDL in any of the following situations:
      • ESXi hosts and storage systems are connected by an iSCSI network.
      • ESXi hosts and storage systems are connected by a Fibre Channel network, and the ESXi hosts are not deployed in a cluster.
      • ESXi hosts and storage systems are connected by a Fibre Channel network, the ESXi hosts are deployed in a cluster, and the storage systems are any version of OceanStor V3 V300R005.
    • In other situations, you must enable APD to PDL as follows:
    1. Run the esxcli upadm set apdtopdl -m on command.
    2. Run the esxcli show upconfig command to view the configuration result. If APD to PDL Mode is on, the APD to PDL function of ESXi hosts is enabled.
      vSphere Security documentation for more information 
      ~ # esxcli upadm show upconfig 
      =============================================================== 
      UltraPath Configuration 
      =============================================================== 
      Basic Configuration 
          Working Mode : load balancing within controller 
          LoadBanlance Mode : min-queue-depth 
          Loadbanlance io threshold : 1 
          LUN Trespass : on 
       
      Advanced Configuration 
          Io Retry Times : 10 
          Io Retry Delay : 0 
          Faulty path check interval : 10 
          Idle path check interval : 60 
          Failback Delay Time : 600 
          Max io retry timeout : 1800 
       
      Path reliability configuration 
          Timeout degraded statistical time : 600    
          Timeout degraded threshold : 1 
          Timeout degraded path recovery time : 1800 
          Intermittent IO error degraded statistical time : 300 
          Min. I/Os for intermittent IO error degraded statistical : 5000 
          Intermittent IO error derraded threshold : 20 
          Intermittent IO error derraded path recovery time : 1800 
          Intermittent fault degraded statistical time : 1800 
          Intermittent fault degraded threshold : 3 
          Intermittent fault degraded path recovery time : 3600 
          High latency degraded statistical time : 300 
          High latency degraded threshold : 1000 
          High latency degraded path recovery time : 3600 
       
      APDtoPDL configuration 
          APD to PDL Mode : on 
          APD to PDL Timeout : 10 
       

  4. Optional: (for Windows) Set the timeout period for an iSCSI initiator.

    NOTE:
    • If you are using a Hyper-V cluster for HyperMetro's upper-layer environment and employing a 10GE SAN, you must set the timeout period to 5 seconds for the iSCSI initiator of every host in the cluster.
    • If the upper-layer environment of HyperMetro is not a Hyper-V cluster or does not use a 10GE SAN, skip this step.
    NOTE:

    Perform the following steps on each Hyper-V host.

    1. Run the iscsiConfig set timeout 5 command.
    2. Run the iscsiConfig set linkdowntime 5 command.
    3. Restart the host.

Configuring an OS Native Multipathing Policy

This section explains how to configure OS native multipathing software.

Context

This configuration must be performed on all initiators with HyperMetro enabled.

HyperMetro is compatible with OS native multipathing software such as HP-UNIX NMP and PV-Links, OpenVMS DM-MultiPath, and Oracle DM-MultiPath.

To use OS native multipathing software, you must enable Uses third-party multipath software for every initiator that will be used for HyperMetro.

Procedure
  1. Log in to DeviceManager.
  2. Choose Provisioning > Host.
  3. In the lower left corner, select the initiator used for HyperMetro, click Modify.

    The Modify Initiator dialog box is displayed.

  4. Modify the properties of the initiator. Figure 2-22 lists related parameters.

    NOTE:

    You need to restart the host after modifying the host initiator information for the configuration to take effect.

    Figure 2-22 Modify Initiator

    For third-party multipathing policies of different operating systems, see the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software to set the parameters in Figure 2-22.

  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.

  6. Configuring third-party multipathing software policies of the hosts.

    This document only describes the configuration required for connecting Huawei storage to third-party multipathing software. For details about third-party multipathing software configuration for host, refer to the HyperMetro Configuration Guide for Huawei SAN Storage Using OS Native Multipathing Software.

Translation
Download
Updated: 2018-09-03

Document ID: EDOC1000106183

Views: 29214

Downloads: 273

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