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).
AIX
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 7-22 lists the detailed settings.
Table 7-22 Storage configurations for interconnection with AIX application servers
DMP |
HyperMetro Working Mode |
Storage System |
OS Setting |
Host Access Mode |
Preferred Path for HyperMetro |
Description |
|---|---|---|---|---|---|---|
DMP 6.0.x to DMP 7.0 |
Load balancing mode |
Local storage |
AIX |
Load balancing |
N/A |
The host uses all paths of a disk with equal priority. |
Remote storage |
AIX |
Load balancing |
N/A |
|||
DMP 7.1 or later |
Load balancing mode |
Local storage |
AIX |
Load balancing |
N/A |
|
Remote storage |
AIX |
Load balancing |
N/A |
|||
Local preferred mode |
Local storage |
AIX |
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 |
AIX |
Asymmetric |
No |
- Use Huawei Storage Interoperability Navigator to query the combinations supported by DMP.
- DMP earlier than 7.1 does not support the local preferred mode or asymmetric mode.
- 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.
- To change the LUN mapping on the storage system, including but not limited to changing the host LUN ID, changing the port online, and removing and adding a LUN, follow the instructions in "How Can I Change LUN Mappings When Non-Huawei Multipathing Software Is Used?" in the OceanStor Dorado Host Connectivity Guide for AIX to correctly change the LUN mapping. Otherwise, services may be interrupted.
- 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.
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.
Host Configuration
Pre-installation Check
Before installing the Veritas DMP multipathing software, ensure that the operating system's native multipathing software has not taken over Huawei storage. In the following example, there are 16 sub-paths between a LUN and a host. The host OS identifies 16 hdisks of the Other FC SCSI Disk Drive type, indicating that the OS native multipathing software has not taken over Huawei storage.
bash-3.2# lsdev -Cc disk hdisk0 Available 0D-00-00 SAS Disk Drive hdisk1 Defined 06-00-02 N/A hdisk2 Defined 06-00-02 N/A hdisk3 Available 0J-00-02 Other FC SCSI Disk Drive hdisk4 Available 0J-00-02 Other FC SCSI Disk Drive hdisk5 Available 0J-00-02 Other FC SCSI Disk Drive hdisk6 Available 0J-00-02 Other FC SCSI Disk Drive hdisk7 Available 0J-01-02 Other FC SCSI Disk Drive hdisk8 Available 0J-01-02 Other FC SCSI Disk Drive hdisk9 Available 0J-01-02 Other FC SCSI Disk Drive hdisk10 Available 0J-01-02 Other FC SCSI Disk Drive hdisk11 Available 0J-00-02 Other FC SCSI Disk Drive hdisk12 Available 0J-00-02 Other FC SCSI Disk Drive hdisk13 Available 0J-00-02 Other FC SCSI Disk Drive hdisk14 Available 0J-00-02 Other FC SCSI Disk Drive hdisk15 Available 0J-01-02 Other FC SCSI Disk Drive hdisk16 Available 0J-01-02 Other FC SCSI Disk Drive hdisk17 Available 0J-01-02 Other FC SCSI Disk Drive hdisk18 Available 0J-01-02 Other FC SCSI Disk Drive bash-3.2#
If any hdisk is of the Huawei MPIO FC Disk Drive type, you must stop services and uninstall ODM. For details on how to uninstall ODM, see the AIX ODM for MPIO User Guide.
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.4.1 in AIX 7.2 TL1 is used as an example. For details about how to install Veritas InfoScale 7.4.1, see Veritas Storage Foundation 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 the Veritas software, modify the dyntrk and fc_err_recov parameters of the AIX FC HBA. For details, see "How Can I Modify the dyntrk and fc_err_recov Parameters for FC HBAs?" in the OceanStor Dorado Host Connectivity Guide for AIX.
- 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-3.2# 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-3.2#
If XSG1 does not exist, upgrade the VRTSaslapm ASL online to a version that supports Huawei storage. You can obtain the ASL installation package for Huawei storage from https://sort.veritas.com/asl. Install ASL by following instructions in the Readme file on the official download page.
- Run the cfgmgr -v 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-3.2# vxddladm list devices DEVICE TARGET-ID STATE DDL-STATUS (ASL) =============================================================== hdisk17 - Online CLAIMED (libvxhuawei.so) hdisk6 - Online CLAIMED (libvxhuawei.so) hdisk12 - Online CLAIMED (libvxhuawei.so) hdisk18 - Online CLAIMED (libvxhuawei.so) hdisk7 - Online CLAIMED (libvxhuawei.so) hdisk13 - Online CLAIMED (libvxhuawei.so) hdisk8 - Online CLAIMED (libvxhuawei.so) hdisk14 - Online CLAIMED (libvxhuawei.so) hdisk3 - Online CLAIMED (libvxhuawei.so) hdisk9 - Online CLAIMED (libvxhuawei.so) hdisk15 - Online CLAIMED (libvxhuawei.so) hdisk4 - Online CLAIMED (libvxhuawei.so) hdisk10 - Online CLAIMED (libvxhuawei.so) hdisk16 - Online CLAIMED (libvxhuawei.so) hdisk5 - Online CLAIMED (libvxhuawei.so) hdisk11 - Online CLAIMED (libvxhuawei.so) hdisk0 - Online CLAIMED (Disk)
- 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-3.2# vxdisk list DEVICE TYPE DISK GROUP STATUS aix_disk_0 auto:LVM - - LVM huawei-xsg11_8 auto:cdsdisk - - online thinrclm bash-3.2#
- Run the vxdisk list device command and check whether the number of paths and path status are correct (consistent with the actual configuration). In the following example, there are 16 paths (hdisk3 to hdisk18) to the aggregated LUN, and all paths are enabled.
bash-3.2# vxdisk list huawei-xsg11_8 Device: huawei-xsg11_8 devicetag: huawei-xsg11_8 type: auto hostid: disk: name= id=1293226805.9.aix group: name= id= info: format=cdsdisk,privoffset=256 flags: online ready private autoconfig autoimport thinrclm pubpaths: block=/dev/vx/dmp/huawei-xsg11_8 char=/dev/vx/rdmp/huawei-xsg11_8 guid: {5ee70f22-0fa6-11e0-9fc9-1772d74b5b9a} udid: HUAWEI%5FXSG1%5F2100238256791322%5F62382561007913220021612B00000000 site: - version: 3.1 iosize: min=512 (bytes) max=512 (blocks) public: slice=0 offset=65792 len=209639920 disk_offset=0 private: slice=0 offset=256 len=65536 disk_offset=0 update: time=1293226805 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 hdisk10 state=enabled hdisk7 state=enabled hdisk8 state=enabled hdisk9 state=enabled hdisk6 state=enabled hdisk5 state=enabled hdisk3 state=enabled hdisk4 state=enabled hdisk12 state=enabled hdisk11 state=enabled hdisk13 state=enabled hdisk14 state=enabled hdisk15 state=enabled hdisk16 state=enabled hdisk17 state=enabled hdisk18 state=enabled bash-3.2# - 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 AA, and the HyperMetro storage systems are correctly aggregated into huawei-xsg11.
bash-3.2# vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT FIRMWARE =================================================================================================== disk Disk DISKS CONNECTED Disk 1 610A huawei-xsg11 HUAWEI-XSG1 2100238256791322 CONNECTED A/A 1 6000 bash-3.2#
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-3.2# 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-3.2#
- Run the cfgmgr -v 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-3.2# vxddladm list devices DEVICE TARGET-ID STATE DDL-STATUS (ASL) =============================================================== hdisk3 - Online CLAIMED (libvxhuawei.so) hdisk4 - Online CLAIMED (libvxhuawei.so) hdisk5 - Online CLAIMED (libvxhuawei.so) hdisk6 - Online CLAIMED (libvxhuawei.so) hdisk7 - Online CLAIMED (libvxhuawei.so) hdisk8 - Online CLAIMED (libvxhuawei.so) hdisk9 - Online CLAIMED (libvxhuawei.so) hdisk10 - Online CLAIMED (libvxhuawei.so) hdisk11 - Online CLAIMED (libvxhuawei.so) hdisk12 - Online CLAIMED (libvxhuawei.so) hdisk13 - Online CLAIMED (libvxhuawei.so) hdisk14 - Online CLAIMED (libvxhuawei.so) hdisk15 - Online CLAIMED (libvxhuawei.so) hdisk16 - Online CLAIMED (libvxhuawei.so) hdisk17 - Online CLAIMED (libvxhuawei.so) hdisk18 - Online CLAIMED (libvxhuawei.so) hdisk0 - Online CLAIMED (Disk) bash-3.2#
- 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-3.2# vxdisk list DEVICE TYPE DISK GROUP STATUS aix_disk_0 auto:LVM - - LVM huawei-xsg11_8 auto:cdsdisk - - online thinrclm bash-3.2#
- 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 (hdisk3 to hdisk18) 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-3.2# vxdisk list huawei-xsg11_8 Device: huawei-xsg11_8 devicetag: huawei-xsg11_8 type: auto hostid: disk: name= id=1293226805.9.aix722zj group: name= id= info: format=cdsdisk,privoffset=256 flags: online ready private autoconfig autoimport thinrclm pubpaths: block=/dev/vx/dmp/huawei-xsg11_8 char=/dev/vx/rdmp/huawei-xsg11_8 guid: {5ee70f22-0fa6-11e0-9fc9-1772d74b5b9a} udid: HUAWEI%5FXSG1%5F2100238256791322%5F62382561007913220021612B00000000 site: - version: 3.1 iosize: min=512 (bytes) max=512 (blocks) public: slice=0 offset=65792 len=209639920 disk_offset=0 private: slice=0 offset=256 len=65536 disk_offset=0 update: time=1293226805 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 hdisk18 state=enabled type=active/non-optimized hdisk16 state=enabled type=active/non-optimized hdisk17 state=enabled type=active/non-optimized hdisk14 state=enabled type=active/optimized(p) hdisk15 state=enabled type=active/non-optimized hdisk13 state=enabled type=active/optimized(p) hdisk11 state=enabled type=active/optimized(p) hdisk12 state=enabled type=active/optimized(p) hdisk10 state=enabled type=active/non-optimized hdisk9 state=enabled type=active/non-optimized hdisk7 state=enabled type=active/non-optimized hdisk8 state=enabled type=active/non-optimized hdisk4 state=enabled type=active/optimized(p) hdisk5 state=enabled type=active/optimized(p) hdisk3 state=enabled type=active/optimized(p) hdisk6 state=enabled type=active/optimized(p) bash-3.2# - 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-3.2# vxdmpadm listenclosure all ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT FIRMWARE =================================================================================================== disk Disk DISKS CONNECTED Disk 1 610A huawei-xsg11 HUAWEI-XSG1 2100238256791322 CONNECTED ALUA 1 6000 bash-3.2#