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).
Working Principles of OS Native Multipathing Software

Working Principles of OS Native Multipathing Software

When ALUA works, the host multipathing software classifies the physical paths to disks as Active Optimized (AO) and Active Non-optimized (AN) paths. The host preferentially delivers services to the storage system via the AO paths.

  • An AO path is the optimal I/O access path between the host and the owning controller of a LUN.
  • An AN path is the suboptimal I/O access path between the host and a non-owning controller.

ALUA Working Principles and Failover in Non-HyperMetro Scenarios

If an AO path fails, the host will deliver I/Os to another AO path.

If all AO paths on the owning controller fail, the host will deliver I/Os to the AN paths on the non-owning controller, as shown in "Path failure" in Figure 6-1.

If a LUN's owning controller fails, the system will activate the other controller as the new owning controller, as shown in "SP failure" in Figure 6-1.

Figure 6-1 Failover in non-HyperMetro scenarios

ALUA Working Principles and Failover in HyperMetro Scenarios

When HyperMetro works in load balancing mode, the host multipathing software defines the paths to the owning controllers on both HyperMetro storage arrays as AO paths, and those to the other controllers as AN paths. The host accesses the storage arrays via the AO paths. If an AO path fails, the host will deliver I/Os to another AO path. If a LUN's owning controller fails, the system will activate the other controller to maintain load balancing.

Figure 6-2 Load balancing mode

When HyperMetro works in local preferred mode, the host multipathing software defines the paths to the owning controller on the local storage array as AO paths. This ensures that the host delivers I/Os only to the owning controller on the local storage array, reducing link consumption. If all AO paths fail, the host will deliver I/Os to the AN paths on the non-owning controller. If the owning controller of the local storage array fails, the system will activate the other controller to maintain the local preferred mode.

Figure 6-3 Local preferred mode

Download
Updated: 2019-05-16

Document ID: EDOC1000150158

Views: 37749

Downloads: 534

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