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

HUAWEI CLOUD Stack 6.5.0 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).
Common Operations

Common Operations

Rebuilding VMs on Other Hosts

Scenarios

If VMs on a host cannot run due to a host fault and these VMs do not have HA enabled, rebuild the VMs on other hosts.

This method applies only to KVM VMs, such as management VMs if FusionCompute is connected in the private cloud scenarios.

Prerequisites

You have obtained the IDs of the VMs to be rebuilt.

Procedure
  1. Use PuTTY to log in to FusionSphere OpenStack through the IP address of the External OM plane.

    The username is fsp, and the default password is Huawei@CLOUD8.
    NOTE:
    • The system supports identity authentication using both the passwords and public-private key pairs. For details about login authentication using the public-private key pairs, see Using PuTTY to Log In to a Node in Key Pair Authentication Mode.
    • To obtain the IP address of the External OM plane, search for the required parameter on the 2.1 Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
      • Region Type I scenario:

        Cascading system: Cascading-ExternalOM-Reverse-Proxy

        Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

      • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  2. Run the following command to switch to the root user:

    su - root

    The default password of the root user is Huawei@CLOUD8!.

  3. Run the TMOUT=0 command to disable user logout upon system timeout.
  4. Import environment variables. For details, see Importing Environment Variables.
  5. Run the following command to query whether the VM is booted from an image:

    nova show vm_id

    vm_id specifies the ID of the VM to be rebuilt.

    Take a note of the OS-EXT-SRV-ATTR:hypervisor_hostname value in the command output. This value is the ID of the host accommodating the faulty VM.

    Check the image field in the command output.

    • The VM boots from the secondary volume if information similar to the following is displayed. In this case, go to 6.
      | image | Attempt to boot from volume - no image supplied|
    • The VM boots from the image if information similar to the following is displayed. Information in the brackets is the image ID. In this case, contact technical support for assistance.
      | image | cirros (d0bd0551-07f2-45f6-8516-f481e0152715)|
      NOTE:

      While you rebuild a VM on another host, if the VM is started from an image, the original data in the system and temporary disks of the VM will be lost. Contact technical support for assistance before performing this high-risk operation, and install services again after the rebuilding.

  6. Check whether the OS is faulty based on the following description:

    NOTE:
    • Linux VMs fail to be logged in to, and the file system is damaged and cannot be rectified.
    • Windows VMs fail to be logged in to, blue screen of death (BSOD) occurs, and the file system is damaged and cannot be rectified
    • The VM OS cannot be started.
    • If yes, go to 7.
    • If no, go to 8.

  7. Rebuild a VM.

    To rebuild a VM in cascading scenarios:

    Run the following command in the cascading system:

    /opt/cloud/services/cascading-nova/venv/bin/python2.7 /etc/nova/nova-util/reschedule_vm.py <vm_id>

    Run the following command in the cascaded system:

    /opt/cloud/services/nova/venv/bin/python2.7 /etc/nova/nova-util/reschedule_vm.py <vm_id>

    To rebuild a VM in non-cascading scenarios, run the following command:

    /opt/cloud/services/nova/venv/bin/python2.7 /etc/nova/nova-util/reschedule_vm.py <vm_id>

    vm_id specifies the ID of the VM to be rebuilt.

    If the information "####Reschedule Command has been accepted!####" is displayed in the command output, the rebuilding instruction is successfully issued. In this case, go to 12.

    If information "Instance XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX sys volume is not found" is displayed in the command output, the system volume has been detached from the VM. In this case, follow the instructions provided in A Fault Occurs If the System Disk of a VM Is Detached.

    If other command output is displayed, contact technical support for assistance.

  8. Run the following command to query VM information:

    nova show uuid

    uuid: specifies the value obtained from the audit result processing. For details, see the methods of obtaining the value in the corresponding section.

    NOTE:
    • The host name is the value of OS-EXT-SRV-ATTR:host in the command output.
    • In the command output, the value of id in os-extended-volumes:volumes_attached is the ID of the volume attached to the VM.

  9. Run the following command to query the image ID of the VM system volume:

    cinder show uuid

    uuid: specifies the ID of the attached volume information obtained in 8.

    NOTE:
    • The drive letter of the attached disk is the value of device in attachments in the command output.
    • The volume image ID is the value of image_id in volume_image_metadata in the command output.
    • If multiple volume IDs are obtained in 8, run the command repeatedly to obtain the image IDs of the volumes whose drive letters are /dev/vda, /dev/xvda, or/dev/sda.

  10. Run the following command to check whether the image is in the ACTIVE status: In the command output, the value of status is the image status.

    nova image-show image_id

    image_id: specifies the image ID.

    • If yes, go to 11.
    • If no, contact technical support for assistance.

  11. Run the following command to rebuild the VM using the image ID:

    nova rebuild <vm_id> image_id
    • <vm_id>: indicates the VM ID obtained in 8.
    • image_id: specifies the image ID.

  12. Run the following command to check whether the VM is successfully rebuilt:

    nova show <vm_id>

    vm_id specifies the ID of the VM to be rebuilt.

    Check the status and task_state columns in the command output:

    • If the value of status is ACTIVE and that of task_state is -, the VM is successfully rebuilt. Check whether you can log in to the VM.
    • If the value of status is ERROR and that of task_state is -, the VM rebuilding fails probably due to resource insufficiency. In this case, perform 7 again. If the VM rebuilding still fails, contact technical support for assistance.
    • If the value of task_state is not -, wait for 5 minutes, and then repeat this step to check whether the rebuilding is successful. If the value of task_state is still not -, perform the rebuilding again. If the rebuilding still fails, contact technical support for assistance.

NOTE:

If the rebuilt VM is the management VM of the controller node, perform 13 to 15.

  1. After the VM is successfully rebuilt, run the following command to obtain the ID of the host where the VM is rebuilt:

    nova show <vm_id>

    vm_id specifies the ID of the VM to be rebuilt.

    Take a note of the OS-EXT-SRV-ATTR:hypervisor_hostname value in the command output. This value is the ID of the host accommodating the faulty VM.

  2. Check whether the host ID recorded in 5 is the same as that recorded in 13.

    • If yes, go to 15.
    • If no, migrate the rebuilt VM to the new host by following the instructions provided in Migrating a VM. After the migration succeeded, go to 15.

  3. Check whether the VM is started from an image by following the instructions provided in 5. If yes, check what services are deployed on the original VM based on the VM name and contact technical support for assistance to reinstall the services.

Abnormal VM Status

Symptom

The tenant VM status is abnormal or the VM status is inconsistent with the power supply status.

Possible Causes
  • Invalid parameters are specified during the VM operation process.
  • Only some OSs support the VM operations.
  • Two or more operations are performed on the VM at the same time, for example, attaching a volume, detaching a volume, installing a network interface card (NIC), uninstalling a network interface card (NIC), and rebuilding, migrating, or modifying specifications.
  • An internal system exception or network exception occurs during the VM operation process.
Procedure

Obtain the system audit document from the FusionSphere version release path and rectify the abnormal audit items.

For the Region Type I scenario, see "System Audit (Region Type I)" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference.

For Region Type II and Region Type III scenarios, see "System Audit (Region Type II&Region Type III)" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference.

Table 8-2 Abnormal VM statuses and troubleshooting methods

Abnormal VM Status

Troubleshooting Method

VM CPU Usage Exceeds the Threshold

"ALM-6036 VM CPU Usage Exceeds the Threshold" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

VM State Error

"ALM-70102 VM State Error" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

VM HA Stuck in the Intermediate State

"ALM-70106 VM HA Stuck in the Intermediate State" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

VM HA Triggered

"EVT-70107 VM HA Triggered" in HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

Faulty VM Directory File

"ALM-70108 Faulty VM Directory File" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

VM HA Malfunctions

"ALM-70130 VM HA Malfunctions" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

VM Restarts Repeatedly

"ALM-73107 VM Is Abnormally Restarted for Multiple Times" in the HUAWEI CLOUD Stack 6.5.0 Alarm&Event Reference

Replacing the SSL Certificate Used by FusionSphere OpenStack to Access Service OM Services

Scenarios

After the root SSL authentication certificate of Service OM is replaced, manually replace the SSL authentication certificate used by FusionSphere OpenStack to access Service OM services.

Prerequisites
  • A tool that can be used for remote access on various platforms, such as PuTTY, is available.
  • You have obtained a valid root certificate and named it ca.crt.
  • You have obtained the reverse proxy IP address of the first host as well as the passwords of the fsp and root users for logging in to the host.
Procedure
  1. Use WinSCP to upload the valid root certificate ca.crt to the first FusionSphere OpenStack host as the fsp user. The /home/fsp directory is used as an example in the following steps.

    Ensure that the FusionSphere OpenStack reverse proxy IP address is used to establish the connection. Set the protocol to SFTP and use the default port 22.

    The default password of the fsp user is Huawei@CLOUD8.

  2. Use PuTTY to log in to the first host in the AZ through the IP address of the External OM plane.

    The username is fsp, and the default password is Huawei@CLOUD8.
    NOTE:
    • The system supports identity authentication using both the passwords and public-private key pairs. For details about login authentication using the public-private key pairs, see Using PuTTY to Log In to a Node in Key Pair Authentication Mode.
    • To obtain the IP address of the External OM plane, search for the required parameter on the 2.1 Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
      • Region Type I scenario:

        Cascading system: Cascading-ExternalOM-Reverse-Proxy

        Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

      • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  3. Run the following command to switch to the root user:

    su - root

    The default password of the root user is Huawei@CLOUD8!.

  4. Run the TMOUT=0 command to disable user logout upon system timeout.
  5. Import environment variables. For details, see Importing Environment Variables.

    Enter 1 to import Keystone V3 environment variables.

  6. Run the following command to switch to the directory containing the uploaded certificate:

    cd /home/fsp

  7. Run the following commands to import a certificate to the server:

    ZAPPER_PATH=$(cat /etc/init.cfg|grep repo |awk -F '=' '{print $2}')

    echo $ZAPPER_PATH|grep "/$" || ZAPPER_PATH="${ZAPPER_PATH}/"

    INTERNAL_CPS_PWD=`python -c 'from FSSecurity import crypt;import ConfigParser;sys_file_parser = ConfigParser.RawConfigParser();sys_file_parser.read("/etc/huawei/fusionsphere/cfg/sys.ini");print crypt.decrypt(dict(sys_file_parser.items("system_account"))["internal_cps_password"])'`

    curl -k -i -H "X-Auth-User:internal_cps_admin" -H "X-Auth-Password:$INTERNAL_CPS_PWD" -X PUT -T /home/fsp/ca.crt ${ZAPPER_PATH}3rdvms/setup/ca.crt

    In the preceding command, ca.crt specifies the name of the root certificate.

    The server certificate is successfully replaced if information similar to the following is displayed:

    HTTP/1.1 100 Continue 
     
    HTTP/1.1 201 Created 
    Last-Modified: Mon, 28 Sep 2015 14:06:55 GMT 
    Content-Length: 0 
    Etag: c57d2f13fd66905b62c8c0420a20a548 
    Content-Type: text/html; charset=UTF-8 
    X-Trans-Id: txe0257216b17347f3ba2f9-005609497e 
    Date: Mon, 28 Sep 2015 14:06:54 GMT 
    Connection: close

    If the command output does not contain "HTTP/1.1 201 Created", run the following commands to import the server certificate:

    ZAPPER_PATH="https$(echo ${ZAPPER_PATH}|awk -F "http" '{print $2}')"

    INTERNAL_CPS_PWD=`python -c 'from FSSecurity import crypt;import ConfigParser;sys_file_parser = ConfigParser.RawConfigParser();sys_file_parser.read("/etc/huawei/fusionsphere/cfg/sys.ini");print crypt.decrypt(dict(sys_file_parser.items("system_account"))["internal_cps_password"])'`

    curl -k -i -H "X-Auth-User:internal_cps_admin" -H "X-Auth-Password:$INTERNAL_CPS_PWD" -X PUT -T /home/fsp/ca.crt ${ZAPPER_PATH}3rdvms/setup/ca.crt

  8. Perform the following operations to query the hosts accommodating the CPS service, and record the host ID of the active node and the IP address of the External OM network plane:

    cps template-instance-list --service cps cps-server

    In the command output, runsonhost indicates the ID of the host accommodating the CPS service.

    The host with status being active is the host accommodating the active CPS service. The IP address in the omip column indicates that of the External OM plane of the host.

  9. Run the following commands to log in to the host accommodating the CPS service and switch to the root user:

    su - fsp

    ssh fsp@Host External OM IP address

    Enter the private key password as prompted. The default password is Huawei@CLOUD8!. If you have successfully replaced the public and private key files, enter the new private key password. Alternatively, press Enter and enter the password of the fsp user.

    The default password of the fsp user is Huawei@CLOUD8.

    su - root

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

    TMOUT=0

    The default password of the root user is Huawei@CLOUD8!.

  10. Run the following commands on the hosts accommodating the CPS service respectively to delete the old certificates in the two directories:

    rm /etc/huawei/fusionsphere/3rdvms/ca.crt > /dev/null 2>&1

    rm /etc/huawei/3rdvms/ca.crt> /dev/null 2>&1

    In the preceding command, ca.crt specifies the name of the old certificate.

  11. Run the following command to delete the uploaded certificate:

    rm /home/fsp/ca.crt

Quickly Collecting Fault Information Using FusionSphere OpenStack

Scenarios

FusionSphere provides the fault scenario information collection function, which does not depend on the external FusionCare tool, thereby accelerating log collection in accident scenarios.

Procedure
  1. Log in to the FusionSphere OpenStack web client.

    For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode).

  2. On the FusionSphere OpenStack web client, choose O&M > Routine Maintenance.

    Figure 8-11 Quick collection of fault information

  3. In the Fault Information Quick Collection area, click Export.
  4. After about 5 minutes, check the exported file. If the system generates the FusionSphere_CollectData.tar.gz file, the fault information is collected and exported successfully.

Migrating a VM

If a host is faulty, or if it is overloaded or underloaded, migrate the VMs running on it to ensure service continuity or proper resource utilization. Available VM migration modes include live migration and cold migration.

Background
  • VM live migration can be performed in the following scenarios:
    • If a host is faulty or overloaded, migrate the VMs running on it to another host to prevent service interruption.
    • If most hosts are underloaded, migrate the VMs to a smaller number of hosts and then power off the idle hosts. This improves resource utilization and reduces power consumption.
  • VM cold migration can be performed in the following scenarios:
    • VMs need to be migrated to prepare for planned upgrade or parts replacement.
    • VMs can be cold migrated if they are in the running state and cannot be live migrated.
Restrictions
  • Migrate VMs one by one at a time. Start migrating another VM only after the previous one is successfully migrated.
  • VM live migration may take a long time if the migrated VMs are heavily loaded or have high memory usage. Therefore, perform VM live migration during off-peak hours.
  • VM live migration is not supported when the VM NIC works in SR-IOV, PF, or PCI passthrough mode.
  • If an ECS has a CD-ROM drive but does not have a local CD-ROM drive or ISO image file mounted, the ECS supports both live migration and cold migration. If an ECS has a CD-ROM drive mounted and has a local CD-ROM drive or ISO image file mounted, the ECS does not support live migration and cold migration.
  • Live migration requires that the source and destination hosts use the same type of hypervisor (KVM, VMware, or XEN).
  • VM cold migration is not supported if the virtualization type of the AZs housing the VMs is VMware.
  • Batch cold migration is supported if the virtualization type of the AZs housing the VMs is XEN.
NOTE:
  • The web client displays a timeout prompt when live migration exceeds 12 hours. However, the internal live migration timeout is 24 hours. The system gives up live migration and releases the occupied resources only after the internal timeout expires.
  • When live migrating a VM that boots from a local disk, OpenStack only checks whether the real available disk space on the target host is sufficient, regardless of the remaining disk space displayed on the hypervisor.

For details about VM migration restrictions, see Table 8-3.

Table 8-3 Restrictions

Resource-Related VM

Whether Cloud Migration Is Supported

Whether Live Migration Is Supported

Local file VM

Yes

Yes

Local disk passthrough VM

No

No

SSD passthrough VM

No

No

GPU passthrough VM

Yes

No

USB passthrough VM

No

No

VM started using a common volume

Yes

Yes

DPDK VM

Yes

Yes

PF passthrough VM

Yes

No

VM with shared volumes

Yes (Migration of the entire system is not supported.)

Yes (Migration of the entire system is not supported.)

VM using SCSI passthrough volumes

Yes

No

NUMA affinity VM

Yes

Yes

Core-binding VM

Yes

Yes

Huge-page memory VM

Yes

Yes

Prerequisites

You have logged in to the ManageOne Maintenance Portal.

Procedure
  1. Click O&M Maps on the top tab menu of ManageOne Maintenance Portal.
  2. In the Quick Links navigation bar on the right of the O&M Maps page, click Service OM. Select your region and then access the Service OM page.
  3. Choose Services > Computing > ECS > Compute Instances.
  4. In the OpenStack Name drop-down list, click , and select cascaded-az1.dc1 to switch to the cascaded system.

    NOTE:

    This step is required only in the Region Type I scenario.

  5. Perform the operations listed in Table 8-4.

    Table 8-4 Migrating a VM

    Operation

    Procedure

    Live migration

    1. Locate the row that contains the target VM, click More > Live Migrate.
    2. Determine whether to specify a host.
      • If you do not need to specify a host, select Not Specify Host and click OK. The VM is migrated by default.

      • If you need to specify a host, select Specify Host and select the destination host to which the VM is migrated.

        Method 1: In the destination host list, select the destination host and click OK.

        Method 2: In the search box, select the ID, name, management IP address, or host group, enter the keyword, select the destination host from the search result, and click OK.

        When a host is specified, a Warning dialog box is displayed. You need to click OK.

    Cold migration

    1. Locate the row that contains the target VM, click More > Cold Migrate. If the following alarm is displayed, click OK.

    2. On the Cold Migrate page, select default AZ.
    3. On the Cold Migrate page, select Specify Host or Not Specify Host.
      • Specify Host: Specify the destination host. You need to specify a destination host in the host list in the lower part of the page.

        Method 1: In the destination host list, select the destination host and click OK.

        Method 2: In the search box, select the ID, name, management IP address, and host group of the destination host, enter the keyword, select the destination host from the search result, and click OK.

      • Not Specify Host: The system automatically migrates the VM to a host.

    4. Click OK.
      NOTE:

      If VM cold migration fails, rectify the fault based on "Handling the VM Cold Migration or Flavor Change Failure" in the HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide.

    Cold migration of the entire system

    1. Locate the row that contains the target VM, click More > Cold Migrate. If the following alarm is displayed, click OK.

    2. On the Cold Migrate page, select a different AZ.
      NOTE:

      After select a different AZ, the disk needed to be migtated, so VM is cold migrated of the entire system.

    3. On the Cold Migrate page, select Specify Host or Not Specify Host.
      • Specify Host: Specify the destination host. You need to specify a destination host in the host list in the lower part of the page.

        Method 1: In the destination host list, select the destination host and click OK.

        Method 2: In the search box, select the ID, name, management IP address, and host group of the destination host, enter the keyword, select the destination host from the search result, and click OK.

      • Not Specify Host: The system automatically migrates the VM to a host.
    4. In the Migration Configuration area on the Cold Migrate page, enter the name of the migration task, select the migration rate, and select the target volume.
    5. In the Warning dialog box that is displayed, click OK.

    NOTE:

    If a VM that is started from a local disk and has data disks installed is migrated to a new host but the ECS status is ERROR because the data disks fail to be connected, run the expansion command to forcibly roll back the migration operation. For details about how to handle a VM cold migration or change specification failure, see "Resource Pool Troubleshooting > FusionSphere OpenStack Troubleshooting > Node Faults > Handling the VM Cold Migration or Flavor Change Failure" in the HUAWEI CLOUD Stack 6.5.0 Troubleshooting Guide.

Database Operations

Obtaining Logs as Required
Database Server Logs

Perform operations provided in Logging In to a Host Running the Database Service and switch to the /var/log/fusionsphere/component/gaussdb directory to obtain the database server logs.

Database Control Script Logs

Perform operations provided in Logging In to a Host Running the Database Service and switch to the /var/log/fusionsphere/component/gaussdbControl directory to obtain the database server logs.

System Logs

Perform operations provided in Logging In to a Host Running the Database Service, switch to the /var/log/uvp-getosstat directory to obtain system status logs recorded by the UVP, and switch to the /var/log/messages directory to obtain system operation logs.

Active and Standby Arbitration Component Logs

Perform operations provided in Logging In to a Host Running the Database Service, switch to the /var/log/fusionsphere/component/cps-server directory to obtain cps-server logs, and switch to the /var/log/fusionsphere/component/cps-client directory to obtain cps-client logs.

Logging In to a Host Running the Database Service
  1. Use PuTTY to log in to the first host of FusionSphere OpenStack through the IP address of the External OM plane.

    The username is fsp, and the default password is Huawei@CLOUD8.
    NOTE:
    • The system supports identity authentication using both the passwords and public-private key pairs. For details about login authentication using the public-private key pairs, see Using PuTTY to Log In to a Node in Key Pair Authentication Mode.
    • To obtain the IP address of the External OM plane, search for the required parameter on the 2.1 Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
      • Region Type I scenario:

        Cascading system: Cascading-ExternalOM-Reverse-Proxy

        Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

      • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  2. Run the following command to switch to the root user:

    su - root

    The default password of the root user is Huawei@CLOUD8!.

  3. Run the TMOUT=0 command to disable user logout upon system timeout.
  4. Import environment variables. For details, see Importing Environment Variables.
  5. Run the cps template-instance-list --service gaussdb gaussdb command to query the host where the database is located. The rows containing the active and standby states record the IDs of the active and standby database hosts, respectively. The IP address in the omip column indicates that of the External OM plane of the host. The command output is as follows:

    +------------+---------------+---------+--------------------------------------+-------------+ 
    | instanceid | componenttype | status  | runsonhost                           | omip        | 
    +------------+---------------+---------+--------------------------------------+-------------+ 
    | 0          | gaussdb       | active  | 40E3DF67-12BF-E411-8135-000000821800 | 192.168.3.7 | 
    | 1          | gaussdb       | standby | 201A5510-FBDD-E411-A9B3-000000821800 | 192.168.3.4 | 
    +------------+---------------+---------+--------------------------------------+-------------+

  6. Run the following commands to log in to the host where the database is located:

    su fsp

    ssh fsp@Host External OM IP address

    Enter the private key password as prompted. The default password is Huawei@CLOUD8!. If you have successfully replaced the public and private key files, enter the new private key password. Alternatively, press Enter and enter the password of the fsp user.

    Example:

    ssh fsp@172.28.6.3

    After you log in to the host as the fsp user, run the su - root command to switch to the root user.

    The default password of the fsp user is Huawei@CLOUD8.

    The default password of the root user is Huawei@CLOUD8!.

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

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 4396

Downloads: 22

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