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

Huawei SAN Storage Host Connectivity Guide for Red Hat

HUAWEI SAN Storage Host Connectivity Guide for Red Hat Servers

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

Veritas/Symantec DMP

Storage System Configuration

If you use DMP, you must select Uses third-party multipath software for the initiator, as shown in Figure 6-15.

Figure 6-15 Initiator setting when DMP is used

The Switchover Mode and Path Type depend on the actual services, as described in Table 6-5.

Table 6-5 Storage system configuration

DMP

Storage Array

OS Setting

Third-Party Multipathing Software

Switchover Mode

Special Mode

Path Type

DMP 7.1 or later

Dual-controller

Linux

Enabled

Special mode

Mode 1

Optimal

Multi-controller

Linux

Enabled

Special mode

Mode 1

Optimal

DMP 6.0.x to DMP 7.0

Dual-controller

Linux

Enabled

ALUA not used

-

Optimal

Multi-controller

Linux

Enabled

ALUA not used

-

Optimal

  • Use Huawei Storage Interoperability Navigator to query the volume management and cluster software supported by DMP.
  • If a LUN has been mapped to the host, you must restart the host for the configuration to take effect after you modify the initiator parameters. 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.
  • Versions earlier than DMP 7.1 do not support multi-controller ALUA.
  • If you do not use the recommended configurations, DMP may fail to identify paths or process paths incorrectly.
  • For the software supported by SF DMP 5.x, contact Huawei technical support engineers.
  • DMP 7.1 and later versions do not support common ALUA. Special mode 1 is supported on OceanStor Dorado V3 V300R002C10SPH105 and later patch versions, OceanStor V5 V500R007C30SPH105 and later patch versions, OceanStor V5 V500R007C10SPH015 and later patch versions, OceanStor V3 V300R006C50SPH105 and later patch versions, OceanStor V3 V300R006C20SPH015 and later patch versions, OceanStor Dorado V3 V300R002C20, OceanStor V5 V500R007C50, and OceanStor V3 V300R006C60. For other earlier versions, set Switchover Mode to ALUA not used.
  • When the storage system is connected to a host with DMP 7.x and you have selected Uses third-party multipath software for the storage initiator and set the switchover mode to a special mode, the maximum number of online ports (FC, FCoE, or Ethernet) supported by a single storage system or HyperMetro storage systems is limited because the default RTPG buffer of Veritas VxVM (DMP) is 255. For details, consult Huawei engineers for evaluation. If the number exceeds the limit, problems such as path identification errors may occur.
  • For a dual-controller storage system, you cannot add controllers online or create HyperMetro online under the following conditions: The storage system is connected to a host using DMP multipathing software; the initiator settings on the storage system are Uses third-party multipath software and ALUA not used; and the A/A mode is disabled. Otherwise, host services may be interrupted. To check whether the A/A mode is enabled, run show tgt_switch storage_work_mode on OceanStor V3 or V5 storage systems, or show scsi_upgrade_config storage_work_mode on Dorado storage systems. The following is an example:
    developer:/>show scsi_upgrade_config storage_work_mode
    Switch Type : A/A Work Mode
    AA Switch   : Off

    In the command output, Off indicates that the A/A mode has been disabled. For a dual-controller storage system, if you want to add controllers online, enable the A/A mode by running change tgt_switch storage_work_mode switch=on on OceanStor V3 or V5, or change scsi_upgrade_config storage_work_mode aa_switch=on on Dorado storage systems.

Host Configuration

Pre-installation Check

DMP cannot coexist with the operating system's native multipathing software. Before installing DMP, you must disable the OS native multipathing software. You can use the following methods to check whether the native multipathing software of Red Hat has been disabled.

For Red Hat 6 and earlier versions, run the following command on the host:

[root@rhel6u91 ~]# /etc/init.d/multipathd status 
multipathd (pid  6831) is running...

The preceding command output indicates that the native multipathing software has been enabled. You must stop services and run the /etc/init.d/multipathd stop command to disable it.

If the status of multipathd is stopped, the native multipathing software has been disabled.

[root@rhel6u91 ~]# /etc/init.d/multipathd stop 
Stopping multipathd daemon:                                [  OK  ] 
[root@rhel6u91 ~]# /etc/init.d/multipathd status 
multipathd is stopped

After disabling the native multipathing software, forbid it to run automatically at system startup using the following command:

chkconfig multipathd off

For Red Hat 7 and later versions, run the following command on the host:

[root@rhel76 ~]# systemctl status multipathd 
   multipathd.service - Device-Mapper Multipath Device Controller 
   Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled) 
   Active: inactive (dead) 
Condition: start condition failed at Wed 2015-09-16 00:27:29 CST; 3s ago 
           ConditionPathExists=/etc/multipath.conf was not met 
[root@rhel76 ~]# 

In the preceding command output, inactive indicates that the native multipathing software has been disabled. If it is enabled, you must stop services and run the systemctl stop multipathd.service command to disable it.

After disabling the native multipathing software, forbid it to run automatically at system startup using the following command:

systemctl disable multipathd.service

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 Storage Foundation 6.2.1 in Red Hat 6.9 is used as an example. For details on how to install Veritas Storage Foundation 6.2.1, see the Veritas Storage Foundation Installation Guide.

After installing Veritas Storage Foundation, 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.

Verification

  1. Run the vxddladm listsupport all | grep huawei command to verify the ASL installation. In the following example, the multipathing software has correctly identified XSG1.

    [root@rhel6u91 ~]# 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 
    [root@rhel6u91 ~]# 

  2. Run the vxdisk list command to check the device name. A correct device name is in the huawei-xxx format. Then run the vxdisk list device name command and check whether the number of paths and path status are correct (consistent with the actual configuration). In the following example, there are 12 paths to a LUN, and all of them are enabled.

    [root@rhel6u91 ~]# vxdisk list huawei-xsg10_0
    Device:    huawei-xsg10_0
    devicetag: huawei-xsg10_0
    type:      auto
    hostid:    rhel6u92
    disk:      name= id=1554661367.14.rhel6u92
    group:     name=dg1 id=1554661430.16.rhel6u92
    info:      format=cdsdisk,privoffset=256,pubslice=3,privslice=3
    flags:     online ready private autoconfig autoimport
    pubpaths:  block=/dev/vx/dmp/huawei-xsg10_0s3 char=/dev/vx/rdmp/huawei-xsg10_0s3
    guid:      {25474db8-5962-11e9-93c2-5083e60ea627}
    udid:      HUAWEI%5FXSG1%5F21009c37f486823e%5F69C37F410086823E000E3AF200000012
    site:      -
    version:   3.1
    iosize:    min=512 (bytes) max=1024 (blocks)
    public:    slice=3 offset=65792 len=209639920 disk_offset=0
    private:   slice=3 offset=256 len=65536 disk_offset=0
    update:    time=1555080569 seqno=0.8
    ssb:       actual_seqno=0.0
    headers:   0 240
    configs:   count=1 len=51360
    logs:      count=1 len=4096
    Defined regions:
     config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
     config   priv 000256-051423[051168]: copy=01 offset=000192 enabled
     log      priv 051424-055519[004096]: copy=01 offset=000000 enabled
     lockrgn  priv 055520-055663[000144]: part=00 offset=000000
    Multipathing information:
    numpaths:  12
    sdbo     	state=enabled
    sdbg     	state=enabled
    sday     	state=enabled
    sdc      	state=enabled
    sdk      	state=enabled
    sds      	state=enabled
    sdaa     	state=enabled
    sdaq     	state=enabled
    sdai     	state=enabled
    sdbw     	state=enabled
    sdce     	state=enabled
    sdcm     	state=enabled
    [root@rhel6u91 ~]# 

  3. Run the vxdmpadm getattr enclosure ENCLR_NAME command to check the current path selection policy, which is MinimumQ by default. In this example, ENCLR_NAME is huawei-xsg10.

    [root@rhel6u91 ~]# vxdmpadm getattr enclosure huawei-xsg10
    ENCLR_NAME      ATTR_NAME                     DEFAULT        CURRENT
    ============================================================================
    huawei-xsg10   iopolicy                      MinimumQ       MinimumQ
    huawei-xsg10   partitionsize                 512            512           
    huawei-xsg10   use_all_paths                 -              -             
    huawei-xsg10   recoveryoption[throttle]      Nothrottle[0]  Nothrottle[0]
    huawei-xsg10   recoveryoption[errorretry]    Timebound[300] Timebound[300] 
    huawei-xsg10   redundancy                    0              0
    huawei-xsg10   dmp_lun_retry_timeout         0              0
    huawei-xsg10   failovermode                  -              -              
    [root@rhel6u91 ~]# 

    If the path selection policy is not MinimumQ, run the vxdmpadm setattr ENCLR_NAME iopolicy=MinimumQ command to set it to MinimumQ.

Download
Updated: 2020-01-17

Document ID: EDOC1000150157

Views: 68369

Downloads: 2059

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next