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).
Information Collection

Information Collection

Collecting Fault Information

Scenarios

When the system is not working properly, maintenance engineers can use either of the following methods to collect information:

Prerequisites
  • FusionCare has been installed and configured.
  • The browser must be Internet Explorer 9.0 to 11.0, Firefox 27.0 to 38.0, or Google Chrome 30.0 to 41.0.
  • The IP address, user name, and password of FusionCare have been obtained.
Procedure
  1. Log in to FusionCare using a browser.

    The address must be in the format of https://FusionCareIP address:8803/hct/index.action.

    The default username is admin and the default password is Hchk@CLOUD8!.

    NOTE:
    • If FusionCare is deployed on a local PC running Windows, enter https://localhost:8803/hct/index.action in the address bar of the browser.
    • Change the password as instructed upon your first login.

  2. Check whether the FusionSphere OpenStack node to be checked has been configured.

    • If yes, go to 5.
    • If no, go to 3.

  3. Choose System Management > Environment Configuration and click Use Wizard to Configure to switch to the Configuration Wizard page.
  4. Enter a valid project name and environment name in Create a project and Create an environment and click Next.
  5. On the Select products page, select FusionSphereOpenStack and click Next. Then, add the product information.
  6. On the Add FusionSphere OpenStack Information page, configure the following parameters:

    • FusionSphere OpenStack node: Set Component Type to KeyStone. Enter the domain name of Keystone in URL in the following format: service type.domain name. Domain name is the AZ name configured during host installation.
    • FusionSphere OpenStack OM node: Set Component Type to OpenStack OM and determine whether to select Deployed on VMs based on site conditions. If you select this item, enter the IP address of the External API or External OM plane for the node. Change the default username as required and enter the password. Then, click Next. If you do not select this item, click Next.
    NOTE:

    If multiple AZs are deployed, you need to add the node multiple times to add the configuration for each AZ and configure the Keystone node information of the AZ.

  7. When the added information passes the validity check, a page indicating node adding success is displayed. Click Finish.
  8. On the Info Collection page, click Create Task.
  9. On the Set Collection Duration page, specify Task Name, Start Time, and End Time, select Collect by Log id or Collect by Scene, and click Next.

    • Task Name: specifies the collection task name, which will be displayed in the information collection list after the task is complete.
    • Start Time and End Time: specify the time range when the log and host running status information is to be collected.

    The system can collect information for a maximum of five nodes at a time and can only collect information generated within a maximum of two days.

  10. On the Select Scene page, select the node for information collection and click Next.

    If multiple nodes are selected, the selected nodes are displayed in a list.

  11. On the Select Nodes page, select the information collection items for each node and click Finish.
  12. Click Yes to collect logs.

    After the system displays a message indicating that the collection task has been successfully added, the collection task begins to execute. Click OK. The time needed for information collection depends on the numbers of target nodes and collection items. The information collection task is complete if the collection progress reaches 100%.

  13. Click Download to download the collected information to the local PC.

    If a ZIP file is downloaded, contact technical support for assistance.

Sending Back Fault Information

Scenarios

After using FusionCare to collect fault information, maintenance engineers should send back only the information needed by technical support engineers to diagnose and locate the fault conditions. In this way, the time needed to send back the collected information is reduced, accelerating the fault location process.

Prerequisites

You have obtained the zip file that contains the information collected using FusionCare.

Procedure
  1. Decompress the zip file to obtain the log_* folder.
  2. Enter the log_*\fsp directory.

    The directory contains several zip files marked by different log levels, as shown in the following figure:

Send the logs of multiple nodes to technical support engineers based on the log level.

  1. Send the required log package to technical support engineers based on the three log packages obtained in 2. You are advised to send error.zip to technical support engineers for the first time.

Send back the error logs of specified modules.

Prerequisite: Technical support engineers will provide the list of nodes and modules whose logs are needed for troubleshooting. The following table provides a sample of such list.

Node Name

007487FD-FBDD-E411-A88B

403A62B2-F7DD-E411-A5A6

Module

cps

rabbitmq

log

  1. Decompress error.zip obtained in 2 and switch to the error folder. Node names are circled in a red box shown in the following figure.

  2. Decompress the package whose name contains 007487FD-FBDD-E411-A88B, and open the obtained folder to check the folders named using the module names, as shown in the following figure.

  3. Create folder info-collect_error and subfolder 007487FD-FBDD-E411-A88B, which will be used for storing the information to be sent back.
  4. Copy the log folders, for example, cps, log, and rabbitmq, obtained in 5 to the 007487FD-FBDD-E411-A88B folder created in 6.
  5. Perform 5 to 7 to copy the logs of the specified modules of the other specified nodes to the info-collect_error folder.
  6. Compress the info-collect_error folder and send the compressed package to technical support engineers.

Send back the info logs of specified modules.

Prerequisites

If technical support engineers are unable to locate the fault based on the error logs, the info.zip package is required. Technical support engineers need to provide the node list and module list, as detailed in the following table.

Node Name

007487FD-FBDD-E411-A88B

403A62B2-F7DD-E411-A5A6

Module

cps

rabbitmq

log

  1. Decompress info.zip obtained in 2 and switch to the info folder. Node names are circled in a red box shown in the following figure.

  2. Decompress the package whose name contains 007487FD-FBDD-E411-A88B, and open the obtained folder to check the folders named using the module names, as shown in the following figure.

  3. Create folder info—collect_info and subfolder 007487FD-FBDD-E411-A88B used for storing the information to be sent.
  4. Copy the folders, for example, cps, log, and rabbitmq, obtained in 11 to the 007487FD-FBDD-E411-A88B folder created in 12, as detailed in the following figure. The following figure shows an example.

  5. Repeat 10 to 13 to copy the related logs of other nodes to the info-collect_info folder.
  6. Compress the info-collect_info folder and contact technical support for assistance.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23150

Downloads: 37

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