Shulou(Shulou.com)06/02 Report--

What I want to share with you in this article is how to solve the very large network delay of CVM. The editor thinks it is very practical, so I share it with you. I hope you can learn something after reading this article. Let's take a look at it with the editor.

When accessing the network resource stutter of the CVM, Ping found packet loss or high delay, which may be caused by backbone link congestion, link node failure, high server load, system setup problems and so on. After excluding the cause of the CVM, you can use MTR for further diagnosis.

WinMTR is a free network diagnosis tool for Windows system, which integrates the functions of Ping and tracert. It has a graphical interface and can directly see the response time and packet loss of each node.

1. Download the corresponding installation package according to the operating system type, extract it, and double-click to run WinMTR.exe in it.

two。 Enter the destination server IP or domain name at Host, and then click Start to test.

3. After running for a period of time, click Stop to end the test. View the test results.

Due to the asymmetry of network conditions, it is recommended to collect bidirectional MTR data (from local to CVM and CVM to local) when you encounter network problems from local to server.

4. Check whether the destination IP has lost packets, and the fact that the destination has not lost packets basically proves that the network is normal. Packet loss in intermediate nodes may be caused by ICMP restrictions or other policies of link nodes, but in fact there is no packet loss. So when looking at the results of WinMTR/MTR, first check to see if there is any packet loss at the last destination. If there is no packet loss, it proves that there is nothing wrong with the network.

5. If a packet loss occurs at the destination, continue to look up and locate the node where the packet was lost for the first time. If the packet loss occurs on the destination server, it may be caused by improper network configuration of the destination server. Check the firewall configuration of the destination CVM.

6. If the packet loss starts in the first three hops, it is usually caused by the network problem of the local operator. It is recommended to check whether the same situation exists when visiting other URLs, and then feedback it to the operator for processing. On the contrary, if the packet loss occurs in a few hops close to the destination server, the network problem of the destination server operator may be dealt with by feedback with the cloud service provider.

The above is how to solve the very large network delay of the CVM. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.