tencent cloud

Feedback

CVM Network Latency and Packet Loss

Last updated: 2022-03-30 14:49:19

    Problem Description

    When you access the CVM from a local machine or access other network resources from the CVM, network stutters. Packet loss or high latency is found when you execute the ping command.

    Problem Analysis

    Packet loss or high latency may be caused by backbone network congestion, network node failure, high load or system configuration. You can use MTR for further diagnosis after ruling out CVM problems.
    MTR is a network diagnostic tool and provides reports that help you locate networking problems.

    Solution

    This document uses Linux and Windows CVM instances as an example to describe how to use MTR and analyze the report.

    Note

    If ping is disabled on the local server or in the CVM instance, MTR will not generate any result.

    Please see the MTR introduction and instructions corresponding to the host operating system.

    WinMTR is a free network diagnostic tool for Windows integrated with Ping and tracert features. Its graphical interface allows you to intuitively see the response time and packet loss of each node.

    Installing WinMTR

    1. Log in to the Windows CVM.
    2. On the operating system interface, visit the official website (or other legal channels) through the browser to download the WinMTR installer package corresponding to your operating system.
    3. Unzip the WinMTR installer package.

    Using WinMTR

    1. Double-click WinMTR.exe to open WinMTR tool.
    2. Enter the IP or domain name of the host in the Host field. Then click Start as shown below:
    3. Wait for WinMTR to run for a while and click Stop to stop the test as shown below:

      Key information of the test result is as shown below:
    • Hostname: IP or name of each host passed through on the path to the destination server.
    • Nr: Number of nodes that have been passed through.
    • Loss%: Packet loss of each node.
    • Sent: Number of data packets sent.
    • Recv: Number of responses received.
    • Best: Shortest response time.
    • Avrg: Average response time.
    • Worst: Longest response time.
    • Last: Last response time.

    Report analysis and troubleshooting

    Note

    Due to network asymmetry, we recommend you collect two-way MTR data (from the local server to the destination server and from the destination server to the local server) if any network error occurs.

    1. According to the report, check whether there is packet loss on the destination IP.
    • If there is no packet loss on the destination IP, network conditions are normal.
    • If there is packet loss on the destination IP, perform Step 2.
    1. Check the result to locate the node where the first packet loss occurred.
    • If packet loss occurred at the destination server, it may be caused by incorrect network configuration of the destination server. Please check its firewall configuration.
    • If packet loss occurred at the first three hops, it may be caused by network problems of the local machine’s ISP. If the problem also happens when you access other addresses, report it to your ISP.
    • If packet losses frequently occur and the network is considered unstable, submit a ticket for assistance and attach the test screenshots to help the engineer locate the problem.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support