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 Using VUM

Installing UltraPath for vSphere Using VUM

This section describes how to install UltraPath for vSphere using VMware Update Manager (VUM).


  • The ESXi hosts are being managed by vCenter.
  • VUM has been installed on vCenter.


To ensure service continuity and avoid data loss, migrate all virtual machines to other hosts or power them off before installing UltraPath for vSphere Using VUM.


  1. Log in to vCenter.
  2. Proceed to Update Manager.
    1. On the menu bar of the ***— vSphere Client page, click Home.

      The *** of ***— vSphere Client is the host name.

    2. In the Solutions and Application area, click Update Manager, as shown in Figure 2-1.

      Figure 2-1  Clicking Update Manager

      The Update Manager Administration for *** page is displayed.

  3. Import the patch program.
    1. On the Update Manager Administration for *** page, click Patch Repository, as shown in Figure 2-2.

      Figure 2-2  Clicking Patch Repository

    2. On the upper right, click Import Patches.

      The Import Patches dialog box is displayed.

    3. In the Import Patches dialog box, click Browse.

      The Select file,containing the patches dialog box is displayed.

    4. Select a .zip file containing a patch and click Open, as shown in Figure 2-3.

      Figure 2-3  Select .zip file

      The Security Warning dialog box is displayed.

    5. In the Security Warning dialog box, select Install this certificate and do not display any security warnings for "" and click Ignore, as shown in Figure 2-4.

      Figure 2-4  Security warning

      The Import Patches dialog box is displayed.

    6. Select the programs you want to repair and click Finish, as shown in Figure 2-5.

      Figure 2-5  Importing the patch program

  4. Create Baselines and Groups.
    1. On the Update Manager Administration for *** page, click Baselines and Groups.
    2. Click Create, as shown in Figure 2-6.

      Figure 2-6  Creating baseline and group

      The New Baseline dialog box is displayed.

    3. Enter the baseline name and type and click Next, as shown in Figure 2-7.

      Figure 2-7  Baseline

    4. On the right function page, select the baselines that need to be extended and click to add the baselines to the Extensions to Add pane, as shown in Figure 2-8.

      Figure 2-8  Creating a new baseline

    5. Click Next.
    6. Click Finish.
  5. Attach baselines and groups.
    1. On the Home page, click Hosts and Clusters.
    2. In the left function pane, select hosts, and then select Update Manager.
    3. Click Attach as shown in Figure 2-9.

      Figure 2-9  Hosts and clusters

      The Attach Baselines or Group dialog box is displayed.

    4. Select the baseline you have created in step 4 and click Attach, as shown in Figure 2-10.

      Figure 2-10  Attaching baselines and groups

  6. Scan for the attached baselines and groups.
    1. On the upper right, click Scan.

      The Confirm Scan dialog box is displayed.

    2. Select Patches and Extensions and click Scan, as shown in Figure 2-11.

      Figure 2-11  Scanning

  7. Remedy the patches.
    1. After the scanning is complete, on the upper right, Non-Compliance is displayed under Host Compliance, and the circle in Host Compliance is red. On the lower right, click Remediate, as shown in Figure 2-12.

      Figure 2-12  

      The Remediate dialog box is displayed.

    2. In the Baseline function pane of the Remediate dialog box, select the objects you want to remedy and click Next, as shown in Figure 2-13.

      Figure 2-13  Selecting objects to remedy

    3. Patches and Extensions is displayed. Select the patches and extensions you want to use and click Next.
    4. Host Remediation Options is displayed. Set the maintenance mode options for the tasks, as shown in Figure 2-14.

      Figure 2-14  Host remediation options

    5. Optional: Cluster Remediation Options is displayed if system is cluster, as shown in Figure 2-15.

      Figure 2-15  Cluster Remediation Options

    6. In Host Compliance on the upper right, check that 0 is displayed after Non-Compliant and the circle in the Compliant function pane is green, as shown in Figure 2-16.

      Figure 2-16  Compliant

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: 37527

Downloads: 782

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