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).
How Do I Handle Drive Letter Changes?

How Do I Handle Drive Letter Changes?

Symptom

In a troubleshooting scenario, a host is reinstalled using preboot execution environment (PXE), but the disk configuration of the newly installed host is inconsistent with that of other hosts in the system. As a result, system installation fails.

Procedure

  1. Use PuTTY to log in to any host in the availability zone (AZ) to which the faulty host belongs.

    Ensure that the fsp user and the IP address of the external OM plane are used to establish the connection.

    NOTE:
    • The system supports login authentication using a password or private-public key pair. If a private-public key pair is used for login authentication, seeUsing PuTTY to Log In to a Node in Key Pair Authentication Mode.
    • For details about the IP address of the External OM plane, see the LLD generated by FCD sheet of the xxx_export_all.xlsm file exported from FusionCloud Deploy during software installation, and search for the IP addresses corresponding to VMs and nodes.The parameter names in different scenarios are as follows:
      • Cascading layer in the Region Type I scenario : Cascading-ExternalOM-Reverse-Proxy, Cascaded layer : Cascaded-ExternalOM-Reverse-Proxy.
      • Region Type II and Type III scenarios : ExternalOM-Reverse-Proxy.
  2. Run the following command and enter the password of user root to switch to user root:

    su - root

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  4. Import environment variables. For details, see Importing Environment Variables.

    Enter fixed value 4 to import the keystone V3 environment variables as the cloud_admin user.

  5. Run the following command to display the host list:

    cps hostcfg-list

    Locate the faulty host and check whether it is in a group whose type is storage.

    • If yes, locate the row that contains the target host ID in the hosts column and the storage value in the type column, take a note of the name value ($hostgroup1 is used in the following steps), and go to 6.
    • If no, contact technical support for assistance.
  6. Run the following commands to delete the host from the original group whose Type is storage:

    cps hostcfg-host-delete --host hostid=$hostid --type storage $hostgroup1

    cps commit

    $hostid specifies the ID of the target host.

  7. Run the following commands to add the host to a new group whose Type is storage:

    cps hostcfg-add --type storage $hostgroup2

    cps hostcfg-host-add --host hostid=$hostid --type storage $hostgroup2

    cps commit

    $hostgroup2 specifies the name of the new group. Name the group in either of the following formats based on the host type:

    • If the host is a controller node, name the group in the format of control_group_xxx.
    • If the host is a compute node, name the group in the format of compute_group_xxx.

      xxx is a number, which must be greater than the number of hosts in the system. You are advised to set it to a value greater than 1000 to prevent it from conflicting with the name of the automatically created group.

  8. Restart the faulty host and install an OS for it using PXE.
  9. Configure disks for the host and configure remote storage for logical disks. For details, see "Configure the disk" in "Releasing FusionCloud Deploy to the Computing Node Pool" in the FusionCloud 6.3.1.1 Software Installation Guide.
  10. If the faulty host has GaussDB, MongoDB, or image-cache services deployed and the services use dedicated SCSI hard disks (including SSDs), choose Configuration > Disk and configure partitions for these services.
  11. If the swap partition has been configured for the faulty host group, choose Configuration > Disk on the FusionSphere OpenStack web client, click the group where the faulty host resides, and click in the Logical Disk area to configure the swap partition. Ensure that the partition size is the same as the original one. You are advised to select an independent volume group. In the Expand Storage Capacity area, click to submit the modification.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22616

Downloads: 37

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