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.
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.
This document takes Linux and Windows CVM as an example to describe how to use MTR and analyze the report.
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.
MTR is a network diagnostic tool for Linux integrated with Ping, traceroute and nslookup features. ICMP packets are used by default to test the network connection between two nodes.
Currently, all released versions of Linux have MTR preinstalled. If not, you can install MTR using the following command:
yum install mtr
sudo apt-get install mtr
Take a local machine to server (IP: 119.28.98.39) as an example.
Execute the following command to output the diagnostic result of MTR in a report.
mtr 119.28.98.39 -- report
A message similar to the one below is returned:
[root@VM_103_80_centos ~]# mtr 119.28.98.39 -- report
Start: Mon Feb 5 11:33:34 2019
HOST:VM_103_80_centos Loss% Snt Last Avg Best Wrst StDev
1.|-- 100.119.162.130 0.0% 10 6.5 8.4 4.6 13.7 2.9
2.|-- 100.119.170.58 0.0% 10 0.8 8.4 0.6 1.1 0.0
3.|-- 10.200.135.213 0.0% 10 0.4 8.4 0.4 2.5 0.6
4.|-- 10.200.16.173 0.0% 10 1.6 8.4 1.4 1.6 0.0
5.|-- 14.18.199.58 0.0% 10 1.0 8.4 1.0 4.1 0.9
6.|-- 14.18.199.25 0.0% 10 4.1 8.4 3.3 10.2 1.9
7.|-- 113.96.7.214 0.0% 10 5.8 8.4 3.1 10.1 2.1
8.|-- 113.96.0.106 0.0% 10 3.9 8.4 3.9 11.0 2.5
9.|-- 202.97.90.206 30.0% 10 2.4 8.4 2.4 2.5 0.0
10.|-- 202.97.94.77 0.0% 10 3.5 4.6 3.5 7.0 1.2
11.|-- 202.97.51.142 0.0% 10 164.7 8.4 161.3 165.3 1.2
12.|-- 202.97.49.106 0.0% 10 162.3 8.4 161.7 167.8 2.0
13.|-- ix-xe-10-2-6-0.tcore2.LVW 10.0% 10 168.4 8.4 161.5 168.9 2.3
14.|-- 180.87.15.25 10.0% 10 348.1 8.4 347.7 350.2 0.7
15.|-- 180.87.96.21 0.0% 10 345.0 8.4 343.4 345.0 0.3
16.|-- 180.87.96.142 0.0% 10 187.4 8.4 187.3 187.6 0.0
17.|-- ??? 100.0% 10 0.0 8.4 0.0 0.0 0.0
18.|-- 100.78.119.231 0.0% 10 187.7 8.4 187.3 194.0 2.5
19.|-- 119.28.98.39 0.0% 10 186.5 8.4 186.4 186.5 0.0
The main output information is as follows
Due to network asymmetry, we recommend you collect two-way MTR data (from the local machine to the destination server and from the destination server to the local machine) if any network error occurs.
Was this page helpful?