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.


eSight V300R009C00 Single-Node System Software Installation Guide (SUSE Linux) 09

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 Components Without Independent Packages in Incremental Mode

Installing Components Without Independent Packages in Incremental Mode

eSight supports incremental installation. That is, a component not installed during initial installation of eSight can be installed during the second installation of eSight.


  • Ensure that the version of the incremental installation package is the same as the baseline version of the running eSight.

    The version number of the incremental installation package is in the format of eSight_VxxxRxxxCxx or eSight_VxxxRxxxCxxSPCx00.

  • If the running eSight has the patch installed, you need to reinstall the patch after the incremental installation.
  • eSight service has stopped. For details, see Stopping the eSight Service.

Installation Process

  • To check whether the running eSight has the patch installed, perform the following steps:

    Log in to the eSight server, go to eSight installation directory/mttools/var/iemp/esightversion, and check the last record in the Version_Path.conf file. If the patch has been installed, the version number will be recorded in the last record. Otherwise, the patch has not been installed.

  • For details about how to install a new component, see Centralized Deployment.
  • If the new component is license controlled, import the matching license file after the installation.
Updated: 2019-05-17

Document ID: EDOC1100011860

Views: 92784

Downloads: 138

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