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).
ECS Network Troubleshooting (Region Type II)

ECS Network Troubleshooting (Region Type II)

This section applies only to the Region Type II scenario.

This section describes how to diagnose network faults on the cloud platform by viewing the ECS status, collecting the ECS alarms, checking network configurations, and executing traffic interruption detection.

Symptom

  • The network between two ECSs of a tenant cannot communicate with each other.
  • The ECS bound to an EIP cannot access external networks.
  • The tenant ECS with VPN configured cannot ping the peer end.
  • Ping packets loss occurs on the EIP of southbound and northbound tenant ECSs.
  • Ping packet loss occurs on the VPN between southbound and northbound tenant ECSs.

Possible Causes

  • The ECS is stopped.
  • ECS configurations are incorrect.
  • The host where the ECS resides is faulty.
  • The external physical network is disconnected.

Diagnosis Process

Prerequisites

ManageOne has been successfully interconnected with FusionSphere OpenStack.

Procedure

  1. Log in to ManageOne Maintenance Portal using a browser.

    URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943

    Default account: admin; default password: Huawei12#$

  2. Click on the main menu.
  3. In the assurance area, click ECS Network Troubleshooting.
  4. Click Diagnose.

    • Batch diagnosis
      1. On the ECS Network Troubleshooting page, click to select multiple target ECSs.
      2. Click Diagnose on the upper left of the page.
    • Single diagnosis
      1. On the ECS Network Troubleshooting page, select a search type, enter a keyword, and press Enter. Find the target ECS.
      2. Click Diagnose in the Operation column.

  5. Check whether the ECS is running properly.

    • If yes, rectify the fault by following the instructions provided in Abnormal VM Status.
    • If no, go to 6.

  6. Check whether any alarm related to the fault exists.

    • If yes, handle it according to the alarm help.
    • If no, go to 7.

  7. Check whether network configurations of the ECS are incorrect.

    NOTE:

    Exception information includes exception information at both the cascading and cascaded systems.

    • If yes, click Export. View detailed information and rectify the fault.
    • If no, go to 8.

  8. Select a traffic interruption detection scenario. Table 5-1 describes the traffic interruption scenarios.

    Table 5-1 Traffic interruption detection scenarios

    Detection Type

    Description

    EIP Packet Trace

    This detection type is used when EIP network locates packet loss points on virtual and physical networks.

    1. In the navigation tree, choose EIP Traffic Detection > Packet Trace.
    2. Enter the EIP, remote IP address, tracing direction, number of packets, packet type, packet flag, and injection time as prompted, as shown in Figure 5-1.
      Figure 5-1 EIP Packet Trace
      • Local EIP: indicates the EIP of the VM to be detected.
      • Remote IP: indicates the remote IP address used to communicate with the VM to be detected.
    1. Click Check. About 3 to 5 minutes later, check whether the traffic diagram and traffic path diagram are abnormal.
      • If yes, "Device is abnormal" or "Device has not network traffic" is displayed. Rectify the fault based on the check suggestions provided in the check result and then go to 9.
      • If no, click Export to export logs and then go to 9.

    VPN Packet Trace

    This detection type is used when VPN network locates packet loss points on virtual and physical networks.

    1. In the navigation tree, choose VPN Traffic Detection > Packet Trace.
    2. On the displayed page, set VM IP to the IP address of the VM to be detected, click to obtain the corresponding VM ID and remote IP address, and set the packet quantity, tracing direction, packet type, injection time, and packet flag, as shown in Figure 5-2.
      NOTE:

      If only one IP address is specified, the VM ID is automatically filled. Otherwise, a VM drop-down list is displayed. You can select one as required.

      Figure 5-2 VPN Packet Trace
    1. Click Check. About 3 to 5 minutes later, check whether the traffic diagram and traffic path diagram are abnormal.
      • If yes, "Device is abnormal" or "Device has not network traffic" is displayed. Rectify the fault based on the check suggestions provided in the check result and then go to 9.
      • If no, click Export to export logs and then go to 9.

    VPC Packet Trace

    This detection is used when the VM to be detected and destination VM locate packet loss points on virtual and physical networks.

    1. In the navigation tree, choose VPC Traffic Detection > Packet Trace.
    2. On the displayed page, set Src IP to the IP address of the VM to be detected, click to obtain the corresponding VM ID, set Dst IP to the IP address of the VM to be detected, click , and set the packet quantity, tracing direction, packet type, injection time, and packet flag, as shown in Figure 5-3.
      NOTE:

      If only one IP address is specified, the VM ID is automatically filled. Otherwise, a VM drop-down list is displayed. You can select one as required.

      Figure 5-3 VPC Packet Trace
    1. Click Check. About 3 to 5 minutes later, check whether the traffic diagram and traffic path diagram are abnormal.
      • If yes, "Device is abnormal" or "Device has not network traffic" is displayed. Rectify the fault based on the check suggestions provided in the check result and then go to 9.
      • If no, click Export to export logs and then go to 9.

  9. Check whether the ECS performance indicators are abnormal. If the green line reaches 100%, the performance indicator is abnormal, as shown in Figure 5-4.

    Figure 5-4 ECS performance monitoring data
    • If yes, contact technical support for assistance.
    • If no, no further action is required.

References

  • EIP: An EIP is an independent public IP address. You can dynamically bind an EIP to an ECS so that the ECS can access the Internet. An EIP can be bound to any VM owned by a user. If a VM is unavailable, the EIP can be quickly redirected to the public IP address of any other VMs owned by the user.
  • VPN: A VPN is used to securely and remotely access the private network of a private cloud through a public network.
  • Virtual Private Cloud (VPC): indicates a virtual network connection based on the service characteristics of tenants.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 2103

Downloads: 12

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