How to detect the network condition between the local network and the ECS instance

The content of this article is about how to detect the network status between the local network and the ECS instance. It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Detect the network condition between the local network and the ECS instance

If the upload bandwidth of your local network is large, but the speed of uploading data to the ECS instance is very slow, you need to detect the local network to the ECS instance Network conditions between instances.

The network conditions between your local network and the ECS instance are affected by the following three factors:

The peak outbound bandwidth and inbound bandwidth of the ECS instance. Regardless of the classic network or VPC network, the maximum outbound bandwidth is 200 Mbit/s, while the maximum inbound bandwidth is determined by the outbound bandwidth. For details, see Public Network Bandwidth Billing.

The upload bandwidth of your local network.

The quality of the network between your local computer and the ECS instance.

The following describes how to detect the network status between local and ECS instances.

Prerequisites

#Add rules in the security group where the ECS instance is located to allow remote pinging of the ECS instance address. For more information, see Typical Applications of Security Group Rules.

The ECS instance is in running status.

Operation steps

Assume that your local machine is running Windows system and uses the Alibaba Cloud DNS IP address (223.5.5.5) as the Alibaba Cloud ECS Example of the public IP address of the instance.

Follow the following steps to check the network status between the local machine and the ECS instance:

Open the command prompt (cmd) on the local machine.

Run ping [public IP address of the ECS instance]. In this example, running ping 223.5.5.5 returns the following results.

正在 Ping 223.5.5.5 具有 32 字节的数据: 
来自 223.5.5.5 的回复: 字节=32 时间=17ms TTL=56
来自 223.5.5.5 的回复: 字节=32 时间=17ms TTL=56
来自 223.5.5.5 的回复: 字节=32 时间=5ms TTL=56
来自 223.5.5.5 的回复: 字节=32 时间=9ms TTL=56
223.5.5.5 的 Ping 统计信息:
数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)，
往返行程的估计时间(以毫秒为单位):
最短 = 5ms，最长 = 17ms，平均 = 12ms

Description: This command is used to detect whether the network is connected, the network delay, whether the network is stable, whether there is packet loss, etc. If the network is normal, the average time is generally tens of milliseconds.

Run tracert -d [the public IP address of the ECS instance]. In this example, running tracert -d 223.5.5.5 returns the following results.

Trace route to 223.5.5.5 via up to 30 hops

1    13 ms     4 ms     4 ms  10.1.40.1
2     2 ms    27 ms    15 ms  10.64.200.33
3     8 ms    10 ms     6 ms  10.64.1.1
4    10 ms     2 ms     5 ms  42.120.74.4
5    20 ms     3 ms     4 ms  42.120.253.233
6    28 ms    12 ms     7 ms  42.120.244.170
7     3 ms     4 ms     4 ms  42.120.244.234
8     *        *        *     请求超时。
9     5 ms    10 ms     7 ms  223.5.5.5

Trace completed.

Description: This command is used to detect the network path between your local network and the ECS instance, as well as the delay of each intermediate network device. In mainland China, the delay for normal access to each route is generally tens of milliseconds. It may happen that some intermediate nodes time out but the ECS instance can still be reached in the end. This may be because the intermediate link does not have a high priority for ICMP responses, or ICMP responses are disabled. For more information about tracert, see the instructions for link testing when ping packet loss or disconnection occurs.

The above is the detailed content of How to detect the network condition between the local network and the ECS instance. For more information, please follow other related articles on the PHP Chinese website!