OS Native Multipathing Software

If you use OS native multipathing software, retain the default host and initiator settings. You can click the host name and check the settings on the Summary tab page. In storage versions earlier than 6.1.3, verify that Host Access Mode is Asymmetric. In 6.1.3 and later versions, verify that Host Access Mode is Load balancing.

Figure 6-2 Checking storage configurations in versions earlier than 6.1.3

Figure 6-3 Checking storage configurations in 6.1.3 and later versions

• 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 6.x series storage systems, configure the storage system by following instructions in Recommended Configurations for 6.x Series Storage Systems 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 Host Access Mode on the storage system is Asymmetric, comment out the vendor ID and product ID of Huawei storage in the scsi_vhci.conf configuration file. If Host Access Mode on the storage system is Load balancing, add the vendor ID and product ID of Huawei storage to the scsi_vhci.conf configuration file. For details, see How Can I Modify the Multipathing Configuration File scsi_vhci.conf?
• SAN Boot is not supported in load balancing mode.

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

For storage systems earlier than 6.1.3, Host Access Mode is Asymmetric, and the method for configuring Solaris 11 is the same as that for Solaris 10. For storage systems of 6.1.3 and later versions, Host Access Mode is Load balancing, and the scsi_vhci.conf configuration file of the host must be modified by following instructions in How Can I Modify the Multipathing Configuration File scsi_vhci.conf?

• If Host Access Mode on the storage system is Asymmetric

  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, Access State is active optimized, indicating that the paths are preferred paths. There are four target ports (201016212c374217, 201116212c374217, 200016212c374217, and 200116212c374217) and eight preferred paths, which are consistent with the actual configuration. The configuration is successful.

• If Host Access Mode on the storage system is Load balancing

  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:  no
          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 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, all paths are preferred paths; Asymmetric is no, indicating that the host is in load balancing mode. There are four target ports (201016212c374217, 201116212c374217, 200016212c374217, and 200116212c374217) and eight preferred paths, which are consistent with the actual configuration. The configuration is successful.