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).
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-18.

Figure 6-18 Using OS native multipathing software

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

Table 6-9 Storage array configuration

Server OS

HyperMetro Working Mode

Storage Array

OS Setting

Third-Party Multipathing Software

Switchover Mode

Special Mode

Path Type

Red Hat 6.x

Load balancing

Local

Linux

Enabled

Common ALUA

-

Optimal

Remote

Linux

Enabled

Common ALUA

-

Optimal

Local preferred

Local

Linux

Enabled

Common ALUA

-

Optimal

Remote

Linux

Enabled

Common ALUA

-

Non-optimal

Red Hat 7.x

Load balancing

Local

Linux

Enabled

Special mode

Mode 0

Optimal

Remote

Linux

Enabled

Special mode

Mode 0

Optimal

Local preferred

Local

Linux

Enabled

Special mode

Mode 0

Optimal

Remote

Linux

Enabled

Special mode

Mode 0

Non-optimal

For details about the Red Hat 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 Red Hat are rpm packages starting with device-mapper-multipath. If you did not install the multipathing software when installing the operating system, you can obtain the software package from the system image and use the rpm command to install it.

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-19.

Figure 6-19 Generating the multipathing configuration file

For Red Hat 6.x and 7.x, add the contents in Figure 6-20 to the /etc/multipath.conf file.

Figure 6-20 Configuration file contents

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 Red Hat 6 and earlier versions:

/etc/init.d/multipathd start

For Red Hat 7 and later versions, run the following command to start the DM-Multipath process:

systemctl start multipathd.service

Setting the Multipathing Software to Run at System Startup

For Red Hat 6 and earlier versions, run the following command to run the multipathing software at startup:

chkconfig multipathd on

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

systemctl enable multipathd.service

Verification

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

Figure 6-21 Verifying the multipathing configuration

As shown in Figure 6-21, 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.

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

Download
Updated: 2020-01-17

Document ID: EDOC1000150157

Views: 68731

Downloads: 2078

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next