OS Native Multipathing Software
Storage System Configuration
If you use OS native multipathing software, you must select Use third-party multipath software for the initiator and set the Switchover Mode to common ALUA, as shown in Figure 6-12.
The Switchover Mode and Path Type depend on the actual services, as described in Table 6-10.
Server OS |
HyperMetro Working Mode |
Storage Array |
OS Setting |
Third-Party Multipathing Software |
Switchover Mode |
Special Mode |
Path Type |
---|---|---|---|---|---|---|---|
Solaris |
Load balancing |
Local |
Solaris |
Enabled |
Common ALUA |
- |
Optimal |
Remote |
Solaris |
Enabled |
Common ALUA |
- |
Optimal |
||
Local preferred |
Local |
Solaris |
Enabled |
Common ALUA |
- |
Optimal |
|
Remote |
Solaris |
Enabled |
Common ALUA |
- |
Optimal |
For details about the Solaris versions, see the Huawei Storage Interoperability Navigator.
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 you configure the initiator for the first time, restart is not needed.
Host Configuration
Solaris 8 and 9
Maintenance for Solaris 8 and Solaris 9 has discontinued and they do not support ALUA. Consequently, ALUA must be disabled on the storage systems when connected to Solaris 8 and Solaris 9, and OS native multipathing software cannot be used.
Solaris 10
Installing and Enabling Multipathing Software
In Solaris 10, the multipathing software has been installed by default, but is not enabled.
After ALUA is enabled on the storage system, run the stmsboot -D fp -e command to enable the multipathing software. You do not need to configure the software on the host.
The following is an example:
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
The host restarts after the preceding operation is performed.
After the host restarts, the following LUN information is displayed.
The path format is scsi_vhci, indicating that this path an aggregation of multiple paths.
Verification
After the LUNs are mapped to the host, scan for the LUNs on the host and verify that the numbers and status of the preferred and non-preferred paths are correct. The following is an example:
root@solarisx86:~# mpathadm show lu /dev/dsk/c0t6222222100222222000E25A800000004d0s2
Logical Unit: /dev/rdsk/c0t6222222100222222000E25A800000004d0s2
mpath-support: libmpscsi_vhci.so
Vendor: HUAWEI
Product: XSG1
Revision: 4303
Name Type: unknown type
Name: 6222222100222222000e25a800000004
Asymmetric: yes
Current Load Balance: round-robin
Logical Unit Group ID: NA
Auto Failback: on
Auto Probing: NA
Paths:
Initiator Port Name: 2100001b3210fbda
Target Port Name: 200800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 2602222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 2619222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2100001b3210fbda
Target Port Name: 202800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 201800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 2601222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 2618222222222222
Override Path: NA
Path State: OK
Disabled: no
Initiator Port Name: 2101001b3230fbda
Target Port Name: 203800ac01020304
Override Path: NA
Path State: OK
Disabled: no
Target Port Groups:
ID: 33
Explicit Failover: no
Access State: active optimized
Target Ports:
Name: 200800ac01020304
Relative ID: 8193
ID: 1
Explicit Failover: no
Access State: active optimized
Target Ports:
Name: 2602222222222222
Relative ID: 23
Name: 2601222222222222
Relative ID: 22
ID: 2
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 2619222222222222
Relative ID: 282
Name: 2618222222222222
Relative ID: 281
ID: 35
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 202800ac01020304
Relative ID: 8705
ID: 34
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 201800ac01020304
Relative ID: 8449
ID: 36
Explicit Failover: no
Access State: active not optimized
Target Ports:
Name: 203800ac01020304
Relative ID: 8961
root@solarisx86:~#
In the command output:
- If Access State is active optimized, the path is a preferred one.
- If Access State is active not optimized, the path is a non-preferred one.
In this example, there are three preferred paths and five non-preferred paths. The result is the same as configured, indicating that the configuration is successful.
Solaris 11
ALUA is enabled on the HyperMetro storage systems. The configuration method of Solaris 11 is the same as that of Solaris 10. See Solaris 10.