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 SUSE

HUAWEI SAN Storage Host Connectivity Guide for SUSE Linux 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).
OS Native Multipathing Software

OS Native Multipathing Software

Storage System Configuration

If you use OS native multipathing software, you must select Uses third-party multipath software for the initiator, as shown in Figure 6-19.

Figure 6-19 Using OS native multipathing software

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

Table 6-8 Storage array configuration

Server OS

HyperMetro Working Mode

Storage Array

OS Setting

Third-Party Multipathing Software

Switchover Mode

Special Mode

Path Type

SUSE

Load balancing

Local

Linux

Enable

Common ALUA

-

Optimal

Remote

Linux

Enable

Common ALUA

-

Optimal

Local preferred

Local

Linux

Enable

Common ALUA

-

Optimal

Remote

Linux

Enable

Common ALUA

-

Non-optimal

For details about the SUSE 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

Installing Multipathing Software

Generally, multipathing software packages in SUSE are rpm packages starting with device-mapper or multipath-tools, and are installed by default. To install the software manually, upload the software package to the server and use the rpm command to install it. Figure 6-20 shows how to verify the multipathing software.

Figure 6-20 Verifying multipathing software

Modifying the Configuration File

DM-Multipath's most important configuration file is /etc/multipath.conf.

Some operating systems have this file by default. If your operating system does not have this file, you can copy the multipath.conf.synthetic file to the /etc directory to generate one, as shown in Figure 6-21.

Figure 6-21 Generating the multipathing configuration file

For SUSE 11, add the contents in Figure 6-22 to the /etc/multipath.conf file.

Figure 6-22 Configuration file for SUSE 11

NOTE:

The WWIDs in the blacklist are local disk information on the server. Fill in the information based on onsite conditions. This also applies to SUSE 12. For details, go to the following website.

https://www.suse.com/documentation/sles-12/stor_admin/data/sec_multipath_trouble.html

dev_loss_tmo and fast_io_fail_tmo specify the retry time and switchover time in the event of a link fault. The preceding figure provides recommended values for these two parameters, and you can modify them according to your own requirements.

For SUSE 12, add the contents in Figure 6-23 to the /etc/multipath.conf file.

Figure 6-23 Configuration file for SUSE 12

NOTE:

dev_loss_tmo and fast_io_fail_tmo specify the retry time and switchover time in the event of a link fault. The preceding figure provides recommended values for these two parameters, and you can modify them according to your own requirements.

Starting the Multipathing Software

After configuring the configuration file, run the following command on the host to start the DM-Multipath process on SUSE11 and earlier versions:

/etc/init.d/multipathd start

For SUSE12 and later versions, run the following command to enable the multipathing process:

systemctl start multipathd.service
Setting the Multipathing Software to Run at System Startup

After enabling the software, you can run the following command to run the software at system startup:

chkconfig multipathd on

Verification

Run the multipath -ll command to verify that the configuration has taken effect.

Figure 6-24 Verifying the multipathing configuration

As shown in Figure 6-24, paths to the HyperMetro storage systems have been converged successfully and the number of paths is correct. status=active corresponds to the AO path to the owning controller of the LUN, and status=enabled corresponds to the AN path to the non-owning controller of the LUN. This indicates that the ALUA configuration has taken effect.

NOTE:

Generally, the prio value of an AO path on a Linux system is 50, and that of an AN path is 10.

Download
Updated: 2019-05-16

Document ID: EDOC1000150158

Views: 38287

Downloads: 535

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next