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


To have a better experience, please upgrade your IE browser.


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).
Installing UltraPath for vSphere on the ESXCLI

Installing UltraPath for vSphere on the ESXCLI

This section describes how to install UltraPath for vSphere on the ESXCLI.


To ensure uninterrupted virtual machine (VM) services in a VMware HA cluster, you must enter the maintenance node on a host and wail until all VMs on the host have been migrated before installing UltraPath for vSphere on the host.


  1. Save the UltraPath for vSphere installation package to any directory on the ESXi host.

    You are advised to create a new directory to save the installation package. This section uses the /opt directory to save the installation package as an example.

  2. Log in to the ESXi host.
  3. Run esxcli software vib install -d /opt/ to start the installation.

    ~ # esxcli software vib install -d /opt/
    Installation Result
       Message: Operation finished successfully.
       Reboot Required: false
       VIBs Installed: HUAWEI_bootbank_ultrapath.cim_8.06.010-00, HUAWEI_bootbank_ultrapath.cli_8.06.010-00, HUAWEI_bootbank_ultrapath.mpp_8.06.010-00
       VIBs Removed: 
       VIBs Skipped: 

  4. Run esxcli software vib list |grep ultrapath to check whether the installation is successful. If the ultrapath.cim, ultrapath.cli, and ultrapath.mpp files are all displayed, the installation is successful. The following figures show possible outputs:

    ~ # esxcli software vib list |grep ultrapath                                              
    ultrapath.cim         8.06.010-00                         HUAWEI    VMwareAccepted    2016-04-22  
    ultrapath.cli         8.06.010-00                         HUAWEI    VMwareAccepted    2016-04-22  
    ultrapath.mpp         8.06.010-00                         HUAWEI    VMwareAccepted    2016-04-22  
    If Pre-Installation Check is not properly completed, restart the ESXi host.

Follow-up Procedure

  • In SAN boot scenarios, restart the EXSi host immediately after UltraPath for vSphere is installed. In non-SAN boot scenarios, perform the following operations:
    1. Run /etc/init.d/hostd restart command to restart the /etc/init.d/hostd service on ESXCLI.
      ~ # /etc/init.d/hostd restart
    2. If the CIM Agent service is disabled, or the ESXi 6.0 system is installed on the host before you install UltraPath for vSphere, enable the CIM Agent service after the installation.
      ~ # /sbin/esxcfg-advcfg -A CIMvmw_ultrapath-providerProviderEnabled -T int -E "Enable or Disable the CIMvmw_ultrapath-providerProviderEnabled" -F 1 -N 0 -M 1
      ~ # esxcfg-advcfg --set 1 /UserVars/CIMvmw_ultrapath-providerProviderEnabled
      ~ # /etc/init.d/sfcbd-watchdog restart
      ~ # /etc/init.d/sfcbd-watchdog status 
      sfcbd is running.
  • After the UltraPath is installed, change the system log size to provide sufficient storage space for system logs, facilitating subsequent analysis and maintenance of the UltraPath. You are advised to set the sizes of both syslog.log and vmkernel.log to 30M and keep the default value 8 of rotations. For details about how to set these parameters, see How to Set System Logs? Select one method.
Updated: 2019-03-06

Document ID: EDOC1000105152

Views: 36591

Downloads: 782

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