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 Local HA System Software Installation Guide (SUSE Linux + MySQL + OMMHA) 10

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).
Configuring the OS

Configuring the OS

After you create a VM, the OS has been installed, but you need to perform the following operations. The operations for configuring the OSs on the active and standby servers are the same.


You have configured the mapping relationship between the haproxyIP and the FusionSphere OpenStack domain name on the local PC.

For the detail, you can refer to the Setting Mapping Relationship Between haproxyIP and FusionSphere OpenStack Domain Name in the Solution Documentation of FusionCloud NFVI.

To obtain the Solution Documentation:

  1. Log in to support website.

    For carrier users, visit

  2. Enter the keyword FusionCloud NFVI xxx Solution Documentation in the search box and click Search.

    xxx: represents the FusionCloud NFVI version.

  3. Download the Solution Documentation document.


The following steps are performed on the active server. When the steps are completed, you need to repeat them on the standby server.

  1. Log in to the FusionSphere OpenStack management console. The Google Chrome browser is recommended.

    1. Perform the following operations to log in to the FusionSphere OpenStack management console:

      Enter https://IP address of the FusionSphere OpenStack reverse proxy:8890 to log in to the installation deployment page of the FusionSphere OpenStack, choose Cloud Service > FusionSphere OpenStack OM, and click the FusionSphere OpenStack OM link to access the FusionSphere OpenStack management console.

    2. Set the view type to the administrator view, enter the user name and password, and log in.

      Set the user name and password to those collected in section "Collecting Information."

  2. Choose Resources > Computing > Compute Instances from the main menu.
  3. Select the VM created before and choose More > VNC Login in the Operation column.
  4. On the operating system login page, click Not listed? to switch to the root user.


    The default password of the root user is Changeme123.

  5. Change the OS host name.

    1. Right-click a blank area on the desktop. In the dialog box that is displayed, click Open Terminal. Run the yast2 command to access the YaST2 Control Center page.
    2. Select System and click Network Settings.
    3. On the Hostname/DNS tab change, change the host name.
    • Set different host names for the active and standby servers. For example, the active server name is eSightServer1 and the standby server name is eSightServer2.
    • The host name of the VM operating system must be the same as the VM name set during VM creation.

    1. Click OK.

  6. Change the time and time zone of the operating system to be local ones.

    1. Click Data and Time.

      Sometimes the system displays a message which indicates that the file has been changed. In this case, ignore the message and click Continue.

    2. Set the current date and time zone in the Clock and Time Zone interface.

    3. Click OK.

  7. Close the YaST2 Control Center page.
  8. Run the following commands to change the number of operating system handles to 65535:

    1. Use PuTTY to log in to the eSight server as the root user through the system IP address.
    2. Run the following command to change the number of operating system handles:

      # sed -i '/^[^#].*[[:space:]]\+nofile[[:space:]]\+/d' /etc/security/limits.conf

      # sed -i '$a\* - nofile 65535' /etc/security/limits.conf

    3. Run the following command to check whether the configuration is successful:

      # cat /etc/security/limits.conf | grep nofile

      If the following information is displayed, the configuration is successful:

      * - nofile 65535
    4. Restart the operating system.

      # reboot

Updated: 2019-09-02

Document ID: EDOC1100011856

Views: 90951

Downloads: 53

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