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).
Cloud Service Management Plane Fault Diagnosis

Cloud Service Management Plane Fault Diagnosis

This section describes how to diagnose cloud service provisioning failures and cloud service instance operation failures by checking operation logs and alarms and collecting logs.

Symptom

  • Cloud service provisioning fails. For example, an ECS, an EVS disk, or a VPN fails to be created.
  • Operations on cloud service instances fail. For example, an EVS disk or a vNIC fails to be attached.

Possible Causes

  • Insufficient computing, storage, or network resources in the resource pool
  • Incorrect configurations ECS or EVS disk configurations

Diagnosis Process

Prerequisites

  • ManageOne is interconnected with the resource pool.

Procedure

  1. Log in to the ManageOne OM plane using a browser.

    Login address: https://Address for accessing the homepage of the ManageOne OM plane:31943, for example, https://oc.type.com:31943.

    Default account: admin; default password: Huawei12#$

  2. Click on the main menu.
  3. Click Cloud Service Management Plane Fault Diagnosis.

    NOTE:

    If the Cloud Service Management Plane Fault Diagnosis portal does not exist, create a diagnosis task by following the instructions provided in "Getting Started with the ManageOne OM Plane" in FusionCloud 6.3.1.1 O&M Guide.

Checking operation logs

  1. In the navigation pane, choose Operation Log Viewing.
  2. Enter the OperationId to query the logs of the failed task. For details about operation log IDs, see Obtaining Operation Log IDs.

    If the query result is empty, contact technical support for assistance.

  3. Locate the row that contains the fault and click to view the log details.
  4. Click the call chain link on the right of the row that contains the log to access the topology details page. On this page, you can view component calling relationships and identify abnormal components to locate faults, as shown in Figure 3-1.

    Figure 3-1 Topology information
    Table 3-1 Topology information

    Parameter

    Description

    Related Operation

    Success

    A green aperture node indicates a normal node whose components have no error.

    Click a red aperture node to display the error data of the corresponding component. Click a green aperture node to display the IP address of the corresponding component.

    Error

    A red aperture node indicates an abnormal node whose components have errors.

    First Service

    A node in the gray background indicates the first node, that is, the first component invoked.

  5. Click any data record to go to the Timeline page, as shown in Figure 3-2.

    Figure 3-2 Timeline
    Table 3-2 Timeline details

    UI Label

    Description

    Existing Time

    Specifies the service invocation start time.

    Duration

    Specifies the time that the invocation takes.

    Response Code

    Specifies the HTTP response code returned from the service entrance invocation.

    Service Name

    Specifies the service name of an exception log.

    Operation/URL

    Specifies the URL of the service dotting entrance.

    RequestId

    Click RequestId to query the associated logs of cloud services and the original trace data.

    HostIP

    Specifies the IP address of a faulty node.

    Status

    In the Status column, indicates that the logs are normal, and indicates that the logs are abnormal.

    Time Axis

    Specifies the response duration during service execution.

  6. In the Exceptions area, click the service name of the exception record to go to the Details dialog box, as shown in Figure 3-3.

    Figure 3-3 Details
    NOTE:

    A trace chain consists of several spans. Each span connects to multiple sub-spans. They are connected as a trace chain tree by calling context (TraceID, ParentID, and SpanID).

    • TraceID is the unique identifier of the trace information generated during a service call.
    • SpanID is unique in the same TraceID.
    • ParentID is the parent ID of the span.

  7. Click the Exception Analysis tab to view and analyze the details about the call and call exceptions, as shown in Figure 3-4.

    RequestId and Job Id are IDs of the associated service logs. You can click the link in the RequestId column to view log details.
    • RequestId indicates the associated logs of FusionSphere OpenStack components.
    • Job Id indicates the associated logs of cloud services.
      Figure 3-4 Exception analysis

  8. If the current log information is insufficient for fault locating, perform 12 through 13 to download logs and analyze the fault.
  9. Click the Log Gather tab to go to the Log Gather page.

  10. Click Log Gather to deliver the log gather task. When the task status reaches 100%, click Download to download the log.

  11. Analyze and rectify the fault based on the downloaded logs. If the cause cannot be identified, send the downloaded logs to R&D engineers for fault locating and analysis.
  12. Check whether the fault is rectified.

    • If yes, no further action is required.
    • If no, go to 16.

Checking alarm information

  1. In the navigation pane, choose Alarm Handling.
  2. Check whether any uncleared alarm exists. If yes, clear the alarm according to the alarm help.
  3. Check whether the fault is rectified.

    • If yes, no further action is required.
    • If no, contact technical support for assistance and provide the collected trace logs. Go to 19.

  4. Technical support personnel analyze the provided trace logs and formulate troubleshooting solutions.

    Check whether the fault is rectified according to the solution provided by the technical personnel.
    • If yes, no further action is required.
    • If no, go to 20.

Collecting log information

  1. In the navigation pane, choose Run Log Collection.

    On the displayed Run Log Collection page, collect logs according to the log collection plan offered by the technical support personnel.

    NOTE:

  2. Check whether the fault is rectified.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22985

Downloads: 37

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