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).
Veritas/Symantec DMP
Storage System Configuration
If DMP is used, retain the default settings of the initiator and configure Host Access Mode and Preferred Path for HyperMetro as required. Table 6-4 lists the detailed settings.
Table 6-4 Configurations of storage systems earlier than 6.1.3 for interconnection with Solaris application servers
DMP |
HyperMetro Working Mode |
Storage System |
OS Setting |
Host Access Mode |
Preferred Path for HyperMetro |
Description |
|---|---|---|---|---|---|---|
DMP 7.1 or later |
Load balancing mode |
Local storage |
Solaris |
Asymmetric |
Yes |
The host uses all paths of a disk with equal priority. |
Remote storage |
Solaris |
Asymmetric |
Yes |
|||
Local preferred mode |
Local storage |
Solaris |
Asymmetric |
Yes |
The host considers the paths from the local storage system as preferred paths, and those from the remote storage system as non-preferred paths. |
|
Remote storage |
Solaris |
Asymmetric |
No |
Table 6-5 Configurations of storage systems 6.1.3 or later for interconnection with Solaris application servers
DMP |
HyperMetro Working Mode |
Storage System |
OS Setting |
Host Access Mode |
Preferred Path for HyperMetro |
Description |
|---|---|---|---|---|---|---|
DMP 7.1 or later |
Load balancing mode |
Local storage |
Solaris |
Load balancing |
N/A |
The host uses all paths of a disk with equal priority. |
Remote storage |
Solaris |
Load balancing |
N/A |
|||
Local preferred mode |
Local storage |
Solaris |
Asymmetric |
Yes |
The host considers the paths from the local storage system as preferred paths, and those from the remote storage system as non-preferred paths. |
|
Remote storage |
Solaris |
Asymmetric |
No |
- Use Huawei Storage Interoperability Navigator to query the combinations supported by DMP.
- DMP earlier than 7.1 does not support HyperMetro.
- In asymmetric mode, HyperMetro does not support VCS clusters.
- If a LUN has been mapped to a host, you must restart the host for the configuration to take effect after you modify Host Access Mode or Preferred Path for HyperMetro. If the host is running services, stop the services and export the disk group before restarting the host. If you configure the initiator for the first time, restart is not needed.
- If you do not use the recommended configurations, DMP may fail to identify and process paths properly.
- If DMP 7.x is used and Host Access Mode is set to Asymmetric, the maximum number of online FC and Ethernet ports supported by a single storage system or two HyperMetro storage systems is limited because the default RTPG buffer length of Veritas VxVM (DMP) is 255. If the number of online ports is greater than the allowed value, paths may not be properly identified. For details, contact Huawei engineers.
Configuring the Load Balancing Mode
The method for configuring the load balancing mode when DMP is used is the same as that when the OS native multipathing software is used. For details, see Configuring the Load Balancing Mode on Storage Systems Earlier Than 6.1.3 in Storage System Configuration.
Configuring the Local Preferred Mode
The method for configuring the local preferred mode when DMP is used is the same as that when the OS native multipathing software is used. For details, see Configuring the Local Preferred Mode in Storage System Configuration.
Host Configuration
Pre-installation Check
DMP cannot coexist with the operating system's native multipathing software MPxIO. Before installing DMP, run the stmsboot -L command to check whether MPxIO (STMS) is disabled.
-bash-4.1# stmsboot -L stmsboot: MPXIO disabled
- If MPxIO is not disabled, open the /kernel/drv/fp.conf configuration file and change mpxio-disable to yes. Then run the stmsboot -d command to disable STMS. When running stmsboot, choose reboot for the settings to take effect.
- SAN Boot is not supported in load balancing mode.
Installing ASL
DMP is generally integrated in the Veritas Storage Foundation/InfoScale software package and is used together with the Veritas Volume Manager (VxVM) and Veritas File System (VxFS).
In this document, installing Veritas InfoScale 7.3.1 in Solaris 11.3 for SPARC is used as an example. For details about how to install Veritas InfoScale 7.3.1, see Veritas InfoScale Installation Guide.
After installing Veritas InfoScale, install Array Support Library (ASL), which provides array-specific support for DMP. ASL is a shared library that can be dynamically loaded. When discovering devices, ASL implements hardware-specific logic to discover device properties.
You are advised to install the latest version of ASL. You can obtain the ASL installation package for Huawei storage from https://sort.veritas.com/asl. ASL can be installed online or offline. Install ASL by following instructions in the Readme file on the official download page. The default path selection policy is MinimumQ.
- Veritas AVID does not support Huawei storage.
- After installing Veritas software, you need to modify fp_offline_ticker and fcp_offline_delay for fp and fcp drivers. The two parameters affect the I/O suspension time when a link fault occurs. You are advised to set both fp_offline_ticker and fcp_offline_delay to 10 based on the value ranges provided by Oracle. You can also set the two parameters based on service configurations. For details, see How Can I Set the fp and fcp Drivers' Time Parameters That Determine How Long a Host Will Wait Before Offlining Disks Upon a Link Failure?
- ZFS file systems are not supported.
- DMP provides the MinimumQ and Round-Robin path selection algorithms, which can be modified based on customer service configurations. You can run the vxdmpadm setattr ENCLR_NAME iopolicy=xxx command to modify the path selection algorithm. xxx indicates the path selection algorithm, which can be MinimumQ or Round-Robin.
Verification
Verifying the Load Balancing Mode
- Run the vxddladm listsupport all | grep huawei command to verify the ASL installation. In the following example, the multipathing software has correctly identified XSG1.
-bash-4.1# vxddladm listsupport all | grep huawei libvxhuawei.so HUAWEI, HUASY S5100, S5300, S5500, S5600, S6800E, S8000, S8000-I, VIS6000, S5500T, S5600T, S5800T, S6800T, S2600T, V1500, V1800, S2100, S2200T, S2300, S2300E, S2600, S3900-M100, S3900-M200, S3900-M300, S5900-M100, S5900-M200, S6900-M100, Dorado2100, Dorado2100 G2, Dorado5100, HVS85T, HVS88T, XSG1 -bash-4.1#
- Run the cfgadm -al and vxdisk scandisks commands at the OS and DMP layers respectively to scan for LUNs. Then run the vxddladm list devices command to check whether the disk corresponding to each sub-path is claimed by Veritas. In the following example, one LUN is mapped and has 16 sub-paths. libvxhuawei.so has identified 16 devices.
-bash-4.1# vxddladm list devices DEVICE TARGET-ID STATE DDL-STATUS (ASL) =============================================================== c2t3d0s2 - Online CLAIMED (Disk) c9t28011603042D0306d1s2 c9_p8_t0 Online CLAIMED (libvxhuawei.so) c9t28001603042D0306d1s2 c9_p7_t0 Online CLAIMED (libvxhuawei.so) c9t28F11603042D0306d1s2 c9_p6_t0 Online CLAIMED (libvxhuawei.so) c9t28F01603042D0306d1s2 c9_p5_t0 Online CLAIMED (libvxhuawei.so) c9t2211238256791322d1s2 c9_p4_t0 Online CLAIMED (libvxhuawei.so) c9t2210238256791322d1s2 c9_p3_t0 Online CLAIMED (libvxhuawei.so) c9t2001238256791322d1s2 c9_p2_t0 Online CLAIMED (libvxhuawei.so) c9t2000238256791322d1s2 c9_p1_t0 Online CLAIMED (libvxhuawei.so) c8t28011603042D0306d1s2 c8_p8_t0 Online CLAIMED (libvxhuawei.so) c8t28001603042D0306d1s2 c8_p7_t0 Online CLAIMED (libvxhuawei.so) c8t28F11603042D0306d1s2 c8_p6_t0 Online CLAIMED (libvxhuawei.so) c8t28F01603042D0306d1s2 c8_p5_t0 Online CLAIMED (libvxhuawei.so) c8t2211238256791322d1s2 c8_p4_t0 Online CLAIMED (libvxhuawei.so) c8t2210238256791322d1s2 c8_p3_t0 Online CLAIMED (libvxhuawei.so) c8t2001238256791322d1s2 c8_p2_t0 Online CLAIMED (libvxhuawei.so) c8t2000238256791322d1s2 c8_p1_t0 Online CLAIMED (libvxhuawei.so) -bash-4.1#
- Run the vxdisk list command to check whether HyperMetro LUNs on the host have been aggregated. The aggregated device can be identified as huawei-xxx. In the following example, DMP identifies an aggregated LUN as huawei-xsg11_#.
-bash-4.1# vxdisk list DEVICE TYPE DISK GROUP STATUS huawei-xsg11_0 auto:cdsdisk - - online thinrclm s113_disk_0 auto:ZFS - - ZFS
- Run the vxdisk list device command and check whether the number of paths and path status are correct (consistent with the actual configuration). The following is an example when the storage version is earlier than 6.1.3. There are 16 paths (cXtXdXsX) to the aggregated LUN, and all paths are enabled.
-bash-4.1# vxdisk list huawei-xsg11_0 Device: huawei-xsg11_0 devicetag: huawei-xsg11_0 type: auto hostid: disk: name= id=1577290545.6.S113 group: name= id= info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig autoimport thinrclm pubpaths: block=/dev/vx/dmp/huawei-xsg11_0s2 char=/dev/vx/rdmp/huawei-xsg11_0s2 guid: {cdf68062-2731-11ea-bd1f-00144fec1884} udid: HUAWEI%5FXSG1%5F21001603042d0306%5F61603041002D030604F9505C0000000F site: - version: 3.1 iosize: min=512 (bytes) max=2048 (blocks) public: slice=2 offset=65792 len=209619712 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1577290545 seqno=0.2 ssb: actual_seqno=0.0 headers: 0 240 configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 disabled config priv 000256-048207[047952]: copy=01 offset=000192 disabled log priv 048208-055503[007296]: copy=01 offset=000000 disabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 16 c8t2000238256791322d1s2 state=enabled type=active/optimized(p) c8t2211238256791322d1s2 state=enabled type=active/optimized(p) c8t2001238256791322d1s2 state=enabled type=active/optimized(p) c8t2210238256791322d1s2 state=enabled type=active/optimized(p) c8t28001603042D0306d1s2 state=enabled type=active/optimized(p) c8t28011603042D0306d1s2 state=enabled type=active/optimized(p) c8t28F01603042D0306d1s2 state=enabled type=active/optimized(p) c8t28F11603042D0306d1s2 state=enabled type=active/optimized(p) c9t2210238256791322d1s2 state=enabled type=active/optimized(p) c9t2211238256791322d1s2 state=enabled type=active/optimized(p) c9t28F01603042D0306d1s2 state=enabled type=active/optimized(p) c9t28001603042D0306d1s2 state=enabled type=active/optimized(p) c9t2000238256791322d1s2 state=enabled type=active/optimized(p) c9t28F11603042D0306d1s2 state=enabled type=active/optimized(p) c9t28011603042D0306d1s2 state=enabled type=active/optimized(p) c9t2001238256791322d1s2 state=enabled type=active/optimized(p) -bash-4.1#The following is an example when the storage version is 6.1.3 or later. There are 16 paths (cXtXdXsX) to the aggregated LUN, and all paths are enabled.bash-3.2# vxdisk list huawei-xsg11_3 Device: huawei-xsg11_3 devicetag: huawei-xsg11_3 type: auto hostid: disk: name= id=1652444225.5.sol10u11b group: name= id= info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig autoimport thinrclm pubpaths: block=/dev/vx/dmp/huawei-xsg11_3s2 char=/dev/vx/rdmp/huawei-xsg11_3s2 guid: {9a580090-d2b6-11ec-a86b-0010e0584fb2} udid: HUAWEI%5FXSG1%5F2100cc64a68314d3%5F6CC64A61008314D3099097B1000001DD site: - version: 3.1 iosize: min=512 (bytes) max=2048 (blocks) public: slice=2 offset=65792 len=209616640 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1652444270 seqno=0.2 ssb: actual_seqno=0.0 headers: 0 240 configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 disabled config priv 000256-048207[047952]: copy=01 offset=000192 disabled log priv 048208-055503[007296]: copy=01 offset=000000 disabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 16 c6t2018CC64A68314D3d4s2 state=enabled c6t28F20A2B304438A8d4s2 state=enabled c6t2019CC64A68314D3d4s2 state=enabled c6t28130A2B304438A8d4s2 state=enabled c6t28120A2B304438A8d4s2 state=enabled c6t2008CC64A68314D3d4s2 state=enabled c6t28F30A2B304438A8d4s2 state=enabled c6t2009CC64A68314D3d4s2 state=enabled c7t28120A2B304438A8d4s2 state=enabled c7t28130A2B304438A8d4s2 state=enabled c7t2008CC64A68314D3d4s2 state=enabled c7t28F30A2B304438A8d4s2 state=enabled c7t2018CC64A68314D3d4s2 state=enabled c7t28F20A2B304438A8d4s2 state=enabled c7t2019CC64A68314D3d4s2 state=enabled c7t2009CC64A68314D3d4s2 state=enabled
Verifying the Local Preferred Mode
- Run the vxddladm listsupport all | grep huawei command to verify the ASL installation. In the following example, the multipathing software has correctly identified XSG1.
-bash-4.1# vxddladm listsupport all | grep huawei libvxhuawei.so HUAWEI, HUASY S5100, S5300, S5500, S5600, S6800E, S8000, S8000-I, VIS6000, S5500T, S5600T, S5800T, S6800T, S2600T, V1500, V1800, S2100, S2200T, S2300, S2300E, S2600, S3900-M100, S3900-M200, S3900-M300, S5900-M100, S5900-M200, S6900-M100, Dorado2100, Dorado2100 G2, Dorado5100, HVS85T, HVS88T, XSG1 -bash-4.1#
- Run the cfgadm -al and vxdisk scandisks commands at the OS and DMP layers respectively to scan for LUNs. Then run the vxddladm list devices command to check whether the disk corresponding to each sub-path is claimed by Veritas. In the following example, one LUN is mapped and has 16 sub-paths. libvxhuawei.so has identified 16 devices.
-bash-4.1# vxddladm list devices DEVICE TARGET-ID STATE DDL-STATUS (ASL) =============================================================== c2t3d0s2 - Online CLAIMED (Disk) c9t28011603042D0306d1s2 c9_p8_t0 Online CLAIMED (libvxhuawei.so) c9t28001603042D0306d1s2 c9_p7_t0 Online CLAIMED (libvxhuawei.so) c9t28F11603042D0306d1s2 c9_p6_t0 Online CLAIMED (libvxhuawei.so) c9t28F01603042D0306d1s2 c9_p5_t0 Online CLAIMED (libvxhuawei.so) c9t2211238256791322d1s2 c9_p4_t0 Online CLAIMED (libvxhuawei.so) c9t2210238256791322d1s2 c9_p3_t0 Online CLAIMED (libvxhuawei.so) c9t2001238256791322d1s2 c9_p2_t0 Online CLAIMED (libvxhuawei.so) c9t2000238256791322d1s2 c9_p1_t0 Online CLAIMED (libvxhuawei.so) c8t28011603042D0306d1s2 c8_p8_t0 Online CLAIMED (libvxhuawei.so) c8t28001603042D0306d1s2 c8_p7_t0 Online CLAIMED (libvxhuawei.so) c8t28F11603042D0306d1s2 c8_p6_t0 Online CLAIMED (libvxhuawei.so) c8t28F01603042D0306d1s2 c8_p5_t0 Online CLAIMED (libvxhuawei.so) c8t2211238256791322d1s2 c8_p4_t0 Online CLAIMED (libvxhuawei.so) c8t2210238256791322d1s2 c8_p3_t0 Online CLAIMED (libvxhuawei.so) c8t2001238256791322d1s2 c8_p2_t0 Online CLAIMED (libvxhuawei.so) c8t2000238256791322d1s2 c8_p1_t0 Online CLAIMED (libvxhuawei.so) -bash-4.1#
- Run the vxdisk list command to check whether HyperMetro LUNs on the host have been aggregated. The aggregated device can be identified as huawei-xxx. In the following example, DMP identifies an aggregated LUN as huawei-xsg11_#.
-bash-4.1# vxdisk list DEVICE TYPE DISK GROUP STATUS huawei-xsg11_0 auto:cdsdisk - - online thinrclm s113_disk_0 auto:ZFS - - ZFS
- Run the vxdisk list device command and check whether the number of paths and path status are correct (consistent with the actual configuration). The asymmetric mode involves preferred and non-preferred paths. You must check whether the status and number of both preferred and non-preferred paths are correct. In the following example, there are 16 paths to the aggregated LUN, and all paths are enabled. The type of eight preferred paths is active/optimized, and that of eight non-preferred paths is active/non-optimized.
-bash-4.1# vxdisk list huawei-xsg11_0 Device: huawei-xsg11_0 devicetag: huawei-xsg11_0 type: auto hostid: disk: name= id=1577290545.6.S113 group: name= id= info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2 flags: online ready private autoconfig autoimport thinrclm pubpaths: block=/dev/vx/dmp/huawei-xsg11_0s2 char=/dev/vx/rdmp/huawei-xsg11_0s2 guid: {cdf68062-2731-11ea-bd1f-00144fec1884} udid: HUAWEI%5FXSG1%5F21001603042d0306%5F61603041002D030604F9505C0000000F site: - version: 3.1 iosize: min=512 (bytes) max=2048 (blocks) public: slice=2 offset=65792 len=209619712 disk_offset=0 private: slice=2 offset=256 len=65536 disk_offset=0 update: time=1577290545 seqno=0.2 ssb: actual_seqno=0.0 headers: 0 240 configs: count=1 len=48144 logs: count=1 len=7296 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 disabled config priv 000256-048207[047952]: copy=01 offset=000192 disabled log priv 048208-055503[007296]: copy=01 offset=000000 disabled lockrgn priv 055504-055647[000144]: part=00 offset=000000 Multipathing information: numpaths: 16 c8t2000238256791322d1s2 state=enabled type=active/non-optimized c8t2211238256791322d1s2 state=enabled type=active/non-optimized c8t2001238256791322d1s2 state=enabled type=active/non-optimized c8t2210238256791322d1s2 state=enabled type=active/non-optimized c8t28001603042D0306d1s2 state=enabled type=active/optimized(p) c8t28011603042D0306d1s2 state=enabled type=active/optimized(p) c8t28F01603042D0306d1s2 state=enabled type=active/optimized(p) c8t28F11603042D0306d1s2 state=enabled type=active/optimized(p) c9t2210238256791322d1s2 state=enabled type=active/non-optimized c9t2211238256791322d1s2 state=enabled type=active/non-optimized c9t28F01603042D0306d1s2 state=enabled type=active/optimized(p) c9t28001603042D0306d1s2 state=enabled type=active/optimized(p) c9t2000238256791322d1s2 state=enabled type=active/non-optimized c9t28F11603042D0306d1s2 state=enabled type=active/optimized(p) c9t28011603042D0306d1s2 state=enabled type=active/optimized(p) c9t2001238256791322d1s2 state=enabled type=active/non-optimized - Run the vxdmpadm listenclosure all command. The command output shows that ENCLR_NAME of the HyperMetro storage systems is correctly aggregated and ARRAY_TYPE is correctly identified. In the following example, ARRAY_TYPE is ALUA, and the HyperMetro storage systems are correctly aggregated into huawei-xsg11.
-bash-4.1# vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT FIRMWARE =================================================================================================== disk Disk DISKS CONNECTED Disk 1 0603 huawei-xsg11 HUAWEI-XSG1 21001603042d0306 CONNECTED ALUA 1 6000