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).
ECS Network Fault Diagnosis

ECS Network Fault Diagnosis

This section applies only to the Region Type I 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 packet 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.
  • ManageOne has been interconnected with the call chain tool.

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 ECS Network Fault Diagnosis.

    NOTE:

    If the ECS Network 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.

  4. On the ECS Network Fault Diagnosis page, select a search type, enter a keyword, and press Enter. Find the target ECS.
  5. Click Diagnosis.
  6. On the Diagnosis page, check whether the ECS is running properly.

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

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

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

  8. 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 9.

  9. Select a traffic interruption detection scenario. Table 4-1 describes the traffic interruption scenarios.

    Table 4-1 Traffic interruption detection scenarios

    Detection Type

    Description

    Traffic Between VMs

    This detection type is used when background services exist between the source and destination ECSs.

    1. Click the Traffic Between VMs tab.
    2. On the displayed page, set Src IP and Dst IP to the IP addresses of the corresponding VMs and click to obtain the corresponding VM IDs, as shown in Figure 4-1.
      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 4-1 Traffic Between VMs
    3. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    EIP Traffic Detection

    This detection type is used when background services exist between the source and destination EIPs.

    1. Click the EIP Traffic Detection tab.
    2. On the displayed page, set Local EIP and Remote IP, as shown in Figure 4-2.
      • 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.
      Figure 4-2 EIP Traffic Detection
    3. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    EIP Ping Detection

    This detection type is used when no background services exist between the source and destination EIPs.

    1. Click the EIP Ping Detection tab.
    2. Enter the local EIP, destination IP address, and packet quantity of the VM to be detected, as shown in Figure 4-3.
      • Dst IP: indicates the IP address of the destination VM.
      • Pkt Num: indicates the number of packets sent from the source VM to the target VM.
      Figure 4-3 EIP Ping Detection
    3. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    EIP Packet Trace

    This detection type helps O&M personnel locate packet loss points on virtual and physical networks.

    1. 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 4-4.
      Figure 4-4 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 10.
      • If no, click Export to export logs and then go to 10.

    VPN Traffic Detection

    This detection type is used when background services exist between the source and destination IP addresses.

    1. Click the VPN Traffic Detection tab.
    2. On the displayed page, set VM IP to the IP address of the VM to be detected and click to obtain the corresponding VM ID, as shown in Figure 4-5.
      Figure 4-5 VPN Traffic Detection
    3. Enter the remote IP address used to communicate with the VM to be detected.
    4. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    VPN Ping Detection

    This detection type is used when no background services exist between the source and destination IP addresses.

    1. Click the VPN Ping Detection tab.
    2. Set Src IP to the FIXED_IP of the VM to be detected, and click the search icon on the right of the text box to obtain the source ID.
    3. Enter the destination IP address and number of packets, as shown in Figure 4-6.
      • Dst IP: indicates the IP address of the destination VM.
      • Pkt Num: indicates the number of packets sent from the source VM to the target VM.
      Figure 4-6 VPN Ping Detection
    4. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    VPN Packet Trace

    This detection type helps O&M personnel locate 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 4-7.
      Figure 4-7 VPN packet trace
    3. 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 10.
      • If no, click Export to export logs and then go to 10.

    ELB East-West Traffic Detection

    This detection type is used when background services exist between the source and destination IP addresses.

    1. Click the ELB East-West Traffic Detection tab.
    2. On the displayed page, set VM IP to the FIXED_IP of the client VM and click to obtain the corresponding VM ID, as shown in Figure 4-8.
      Figure 4-8 ELB East-West Traffic Detection
    3. Enter the corresponding LB VIP and port number.

      LB VIP: indicates the VIP of the corresponding ELB service.

    4. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

    ELB South-North Traffic Detection

    This detection type is used when background services exist between the source and destination IP addresses.

    1. Click the ELB South-North Traffic Detection tab.
    2. Enter the IP address (EIP or public IP address) of the client VM that initiates LB access, as shown in Figure 4-9.
      Figure 4-9 ELB South-North Traffic Detection
    3. Enter the EIP of the LB VIP to be accessed and the port number monitored by the LB.

      LB EIP: indicates the EIP corresponding to the VIP of the ELB service.

    4. Click Check to 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 10.
      • If no, click Export to export logs and then go to 10.

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

    Figure 4-10 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.
  • ELB: An ELB evenly distributes service requests to associated hosts based on the specified policies, achieving load balancing among the hosts and ensuring service stability and reliability.
  • VPN: A VPN is used to securely and remotely access the private network of a private cloud through a public network.
  • Southbound and northbound traffic: indicates traffic between external users and internal cloud servers in the data center.
  • Background service traffic: indicates Layer-4 TCP packets between two VMs in the ELB southbound and northbound traffic monitoring scenario and ELB eastbound and westbound traffic monitoring scenario, and indicates ICMP ping packets between two VMs in other scenarios.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22916

Downloads: 37

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