OS Native Multipathing Software

If you use OS native multipathing software, retain the default host and initiator settings. By default, Host Access Mode is Asymmetric. You can click the host name and check the settings on the Summary tab page.

Figure 6-2 Checking storage configurations

• For details about the Solaris versions, see the Huawei Storage Interoperability Navigator.
• 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. If you map the LUN for the first time, restart is not needed.
• When data is migrated from other Huawei storage systems (including Dorado V3, OceanStor V3, and OceanStor V5) to Dorado V6, configure the storage system by following instructions in Recommended Configurations for OceanStor Dorado V6 for Taking Over Data from Other Huawei Storage Systems When the Host Uses the OS Native Multipathing Software.
• The information displayed on the GUI may vary slightly with the product version.

In Solaris 10 and later versions, the multipathing software has been installed by default, but is not enabled.

When Host Access Mode on the storage system is Asymmetric, run the stmsboot -D fp -e command to enable the multipathing software. You do not need to configure the software on the host.

If the vendor ID and product ID of Huawei storage have been added to the scsi_vhci.conf configuration file, modify the configuration file by following instructions in How Can I Modify the Multipathing Configuration File scsi_vhci.conf?

Run the stmsboot -D fp -e command on the host to activate the STMS function. The multipathing software takes effect after the host restarts.

bash-3.2# stmsboot -D fp -e 
WARNING: This operation will require a reboot. 
Do you want to continue ? [y/n] (default: y) y 
The changes will come into effect after rebooting the system. 
Reboot the system now ? [y/n] (default: y) y 
updating /platform/sun4u/boot_archive

When Host Access Mode is Asymmetric, the method for configuring Solaris 11 is the same as that for Solaris 10.

After the LUNs have been mapped to the host, scan the LUNs on the host and verify that the number and status of the LUNs are correct. The following is an example:

root@S113:~# mpathadm show lu /dev/rdsk/c0t6010203100040577001ACD6C00000025d0s2
Logical Unit:  /dev/rdsk/c0t6010203100040577001ACD6C00000025d0s2
        mpath-support:  libmpscsi_vhci.so
        Vendor:  HUAWEI  
        Product:  XSG1            
        Revision:  6000
        Name Type:  unknown type
        Name:  6010203100040577001acd6c00000025
        Asymmetric:  yes
        Current Load Balance:  round-robin
        Logical Unit Group ID:  NA
        Auto Failback:  on
        Auto Probing:  NA

        Paths:  
                Initiator Port Name:  2100000e1e1a9b31
                Target Port Name:  201016212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b31
                Target Port Name:  201116212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b31
                Target Port Name:  200016212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b31
                Target Port Name:  200116212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b30
                Target Port Name:  201016212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b30
                Target Port Name:  201116212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b30
                Target Port Name:  200016212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

                Initiator Port Name:  2100000e1e1a9b30
                Target Port Name:  200116212c374217
                Override Path:  NA
                Path State:  OK
                Disabled:  no

        Target Port Groups:  
                ID:  1
                Explicit Failover:  no
                Access State:  active optimized
                Target Ports:
                Name:  201016212c374217
                Relative ID:  0

                Name:  201116212c374217
                Relative ID:  0

                Name:  200016212c374217
                Relative ID:  0

                Name:  200116212c374217
                Relative ID:  0
root@S113:~# 

In the command output, there are four target ports (201016212c374217, 201116212c374217, 200016212c374217, and 200116212c374217) and eight preferred paths (Access State being active optimized), which are consistent with the actual configuration. The configuration is successful.