UltraPath
This section describes the operations on storage systems and hosts when UltraPath is used.
Storage System Configuration
If UltraPath is used, retain the default initiator settings. Do not select Use third-party multipath software.
If the storage system version is V500R007C71 Kunpeng or later, upgrade Huawei UltraPath to 31.0.0 or later. Before configuring HyperMetro, enable automatic LUN SN synchronization on both storage systems. If this function is not enabled, one HyperMetro LUN may be identified as two disks by host applications. For details, see section "What Can I Do If the Host Identifies One HyperMetro LUN as Two Disks?" in the HyperMetro Feature Guide for Block.
Host Configuration
Install UltraPath by following instructions in the OceanStor UltraPath for Windows User Guide.
After you install UltraPath, set the trespass policy for LUNs as follows:
- For UltraPath earlier than 21.2.0, it is recommended that you run the set luntrespass command to disable the trespass policy.
UltraPath CLI #3 >set luntrespass=off array_id=0 The current configuration will overwrite the configuration of all VLUNs in this array. Are you sure you want to continue? [y,n]: y Succeeded in executing the command.
The command format is set luntrespass={ on | off } [ array_id=ID | vlun_id={ ID | ID1,ID2... | ID1-ID2 } ]. Table 6-7 describes the key parameters in the command.Table 6-7 Parameter descriptionParameter
Description
Default Value
{ on | off }
Trespass policy of LUNs
- on: Switchover of LUNs' working controller is enabled.
- off: Switchover of LUNs' working controller is disabled.
on
array_id=ID
ID of the storage array
You can run the show array command to query the ID of the storage array.
None
vlun_id={ ID | ID1,ID2... | ID1-ID2 }
ID of the virtual LUN
You can run the show vlun type=all command to query the IDs of all virtual LUNs.
None
- For UltraPath 21.2.0 and later, it is recommended that you retain the default settings (the trespass policy is disabled by default).
After configuring the trespass policy, set the HyperMetro working mode to local preferred on UltraPath. In this mode, the local storage array is preferred in processing host services. The remote storage array is used only when the local array is faulty. This improves the service response speed and reduces the access latency.
Table 6-8 lists the command for setting the HyperMetro working mode.
Operating System |
Command |
Example |
|---|---|---|
Windows |
set hypermetroworkingmode={priority|balance}primary_array_id=ID |
upadm set hypermetro workingmode=priority primary_array_id=0 |
Table 6-9 describes the parameters.
Parameter |
Description |
Default Value |
|---|---|---|
workingmode={ priority | balance } |
HyperMetro working mode.
NOTE:
If you set the HyperMetro working mode for a specific virtual LUN first and then the global HyperMetro working mode for the storage system, the working mode for the virtual LUN remains unchanged. |
priority priority is recommended. balance is applicable when 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 that is in the same data center as the application hosts is preferred. Run the command to obtain the storage array ID:
NOTE:
|
None NOTE:
Mapping relationship between application hosts and storage arrays:
|
If a path switchover takes a long period of time, you can modify the timeout time for a driver by following instructions in How Do I Modify the Timeout Time for the FC HBA Port Driver? or How Do I Modify the iSCSI Initiator's Driver Timeout Time?, thereby shortening I/O interruption.
Verification
Run the upadm show upconfig command. If the command output contains the following information, the configuration is successful.
HyperMetro WorkingMode : read write within primary array
Figure 6-14 provides an example.
