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

OceanStor UltraPath for vSphere V100R008C50 User Guide 06

This document covers the functions, features, installation, configuration, upgrade, uninstallation, maintenance, troubleshooting, and FAQs of OceanStor UltraPath for vSphere (UltraPath forvSphere). UltraPath for vSphere is the multipathing software developed by HuaweiTechnologies Co., Ltd (Huawei for short). The document aims at helping users to be fully familiar with UltraPath for vSphere and its use.
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).
Failover and Failback

Failover and Failback

UltraPath for vSphere automatically and periodically monitors path status. Once a path is found faulty, UltraPath for vSphere switches data on the faulty path to another normal one. After the faulty path recovers, the software switches the data back to the path. During the failover and failback processes, services on the application server remain online and applications continue to meet reliability and service level agreement (SLA) requirements.

Typical path fault scenarios are as follows:
  • In dual-link connection, the optimum path is faulty, as shown in Figure 1-3.
  • In dual-link switch connection, the optimum path is faulty on the application server side, as shown in Figure 1-4.
  • In dual-link switch connection, the optimum path on the storage system side is faulty, as shown in Figure 1-5.
As shown in Figure 1-3, the LUN belongs to controller A and UltraPath for vSphere selects the path between controller A and the application server as the optimum path. If the optimum path becomes faulty, UltraPath for vSphere switches data from the faulty path to the other path between the application server and controller B, ensuring service continuity.
Figure 1-3  Path failover scenario 1

As shown in Figure 1-4, the optimum path is from the HBA0 to the switch and then to controller A. If the link between the switch to controller A is faulty, UltraPath for vSphere replaces the faulty link with the link between HBA1 to the switch. The link between the switch and controller A is retained. In this way, the new path after service failover remains the optimum path, ensuring service continuity.
Figure 1-4  Path failover scenario 2

As shown in Figure 1-5, the paths work in the same way as that in Figure 1-4. If the link between the switch and controller A is faulty, UltraPath for vSphere replaces the faulty link with the link between the switch and controller B. The link between HBA0 and the switch is retained. In this way, the link fault's impact on the upper-layer service is minimized.
Figure 1-5  Path failover scenario 3

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1000105152

Views: 38838

Downloads: 783

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