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

FusionCloud 6.3.1.1 Troubleshooting Guide 02

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).
Performing the Preinstallation Check

Performing the Preinstallation Check

This section describes how to check the OS versions, data disks, and deployment environment of VMs before the ManageOne installation.

Prerequisites

  • VMs have been configured, OSs have been installed on the VMs, and data disks have been mounted to the VMs.
  • Microsoft Office Excel 2007 or later has been installed on the PC.

Procedure

  1. Check whether you can use PuTTY to log in to each VM using user root and its default password Changeme_123. If the login fails, contact the DC administrator to set the default user name and password of the VM to root and Changeme_123, respectively. Do not change the default user name and password during the entire installation process.
  2. Verify that the OS version meets requirements and the data disk has been mounted.

    1. Use PuTTY to log in to the OS of any VM in the current region as user root.
    2. Run the following command to query the name of the new data disk, record the name, and verify that each VM has only one system disk and one data disk:

      fdisk -l

      Information similar to the following is displayed:

      Disk /dev/xvda: 75.2 GB, 75161927680 bytes
      255 heads, 63 sectors/track, 9137 cylinders, total 146800640 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00082be6
      
          Device Boot      Start         End      Blocks   Id  System
      /dev/xvda1   *        2048     2088959     1043456   83  Linux
      /dev/xvda2         2088960    35633151    16772096   83  Linux
      /dev/xvda3        35633152    71280639    17823744   83  Linux
      /dev/xvda4        71280640   146800639    37760000    f  W95 Ext'd (LBA)
      /dev/xvda5        71282688    73369599     1043456   83  Linux
      /dev/xvda6        73371648    83843071     5235712   83  Linux
      /dev/xvda7        83845120    90124287     3139584   83  Linux
      /dev/xvda8        90126336   132055039    20964352   83  Linux
      /dev/xvda9       132057088   136247295     2095104   83  Linux
      /dev/xvda10      136249344   146800639     5275648   83  Linux
      
      Disk /dev/xvde: 569.1 GB, 569083166720 bytes
      255 heads, 63 sectors/track, 69187 cylinders, total 1111490560 sectors
      Units = sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00000000
      
      Disk /dev/xvde doesn't contain a valid partition table
      NOTE:

      /dev/xvda indicates the system disk name and /dev/xvde indicates the data disk name. Data disk names start from /dev/xvde and increase in ascending order, for example, /dev/xvde, /dev/xvdf, and /dev/xvdg. /dev/xvda and /dev/xvde are examples only. Replace them with actual disk names as required.

    3. Decompress the ManageOne_init_tools.zip installation tool package on your PC. Locate the ManageOne_init_tools folder.
      NOTE:

      You are advised to decompress the ManageOne_init_tools folder to the desktop of your PC. If the decompression path is too long, errors may occur during the installation.

    4. Go to the /check directory in the ManageOne_init_tools folder.
    5. Open the environment node table template. Modify the IP addresses (IP address), floating IP addresses (Access IP), server names (Server Name), AZs (AZName), and server groups (ServerGroup) for all nodes, and click Save. Only the VM information to be checked needs to be retained in the table. Delete the information in the rows corresponding to the VMs that do not need to be checked.
      • If the log center nodes are not installed, use the environment node table template allNodes.csv.
      • To install a log center node, use the environment node table template allNodes_log.csv.
      • When you modify the environment node table, do not enter spaces in front of or behind an IP address or a floating IP address.
      Table 26-5 describes the parameters that need to be modified in the environment node table.
      Table 26-5 Description of parameters in the environment node table

      No.

      Parameter

      Description

      Example Value

      1

      IP address

      IP address of the VM to be checked.

      10.31.32.6

      2

      Server Name

      Name of the VM to be checked.

      MOC-ManageOne-Service01

      3

      Access IP

      Floating IP address of the VM to be checked. This parameter needs to be set only for the O&M nodes. In a region, O&M nodes have the same floating IP address.

      10.31.32.9

      4

      AZName

      AZ name. Set this parameter to the value of AZName in environment planning.

      cn-global-1-a

      5

      ServerGroup

      Server group name. You only need to change the region alias in the server group name to the region alias of the VM in environment planning.

      MOC-Agent-AppNodes|MOC-OM-Global-RHMessage|MOC-OM-Global-MOElastic

    6. Double-click checkEnv.bat in the current directory on your PC.
      NOTE:

      If an error occurs indicating that a DLL file is unavailable, install the Visual C++ software package. For details, see What Do I Do If a Batch Processing File Failed to Be Launched?

    7. When the following information is displayed, enter y and press Enter:
      Are you sure you want to continue(y/n):
    8. When the following information is displayed, enter the password of user root of the node and press Enter:
      Input the default password for all hosts:
    9. Enter the data disk name obtained in 2.b and press Enter.
      Input data disk name[/dev/xvde]:
      NOTE:

      If you press Enter without entering any text, the data disk name is set to /dev/xvde by default.

    10. Check the execution result.

      If information similar to the following is displayed, view the VMs that succeed in or fail the check based on VM IP addresses. If the check is successful, the OS version meets requirements and the data disk has been mounted.

      Success Hosts:['IP address of the node that is successfully initialized'...]
      Failed Hosts:['IP address of the node that fails the check'...]
    11. If a VM fails the check, the OS version of the VM does not meet the requirements of ManageOne or the data disk has not been mounted. In this case, contact the DC administrator to reconfigure the VM.

  3. In the result folder under the current directory, use Excel to open the envInfo.csv file and check whether the environment information of each VM is consistent with the live-network planning.

    • If the information is consistent, perform the operations in the following sections.
    • If the information is inconsistent, contact the DC administrator to reconfigure the VMs.

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23290

Downloads: 37

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