How to test the route tracing and backhaul route tracing of Linux system servers

There are many test scripts about the performance and bandwidth of the Linux system server (VPS). Motao has shared good scripts. The main reason for sharing to the blog is to make it easy for everyone to use and to find them in the future.

In this article, Moto mainly introduces how to test the server, route tracing and backhaul routes. In fact, the route tracing test is very important. You can directly see whether there is a winding and what route is taken through the test. Generally, the CN2 route can be seen intuitively through the route tracing. The effect of the backhaul route tracing is the same, and it can also be seen

1、 Route tracing test

1. Use tools to test. For the server routing trace test, we can use the tool besttrace.exe It can simply and intuitively see each node passing by, and there is also an intuitive map to show it.

2. Use the server to test. The existing Linux system servers are used to trace IP routes. The command is as follows. For the IP following "mtr - rw", please change the IP address of the server you want to track. In fact, it is simple to test the routing nodes that other servers need to pass through to access the server IP you want to test.

 yum -y install mtr mtr -rw 198.55.111.5

Tracking effect display:

 [ root@DAIMIYUN20171126805  ~]# mtr -rw 198.55.111.5 Start: Mon Dec 18 21:48:04 2017 HOST: DAIMIYUN20171126805                  Loss%   Snt   Last   Avg  Best  Wrst StDev 1.|-- gateway                               0.0%    10   12.9  23.4   6.0  88.6  25.4 2.|-- 192.168.0.1                          90.0%    10    3.4   3.4   3.4   3.4   0.0 3.|-- 172.16.0.1                            0.0%    10    1.1   1.2   1.1   2.1   0.0 4.|-- 219.141.127.57                       10.0%    10    1.0   1.6   0.9   4.7   1.1 5.|-- 219.141.127.49                        0.0%    10    1.7   1.8   1.6   2.1   0.0 6.|-- 61.189.251.109                        0.0%    10    8.1   8.3   8.1   9.4   0.3 7.|-- 202.97.69.93                          0.0%    10   23.8  23.8  22.0  25.3   0.7 8.|-- ???                                   100.0    10    0.0   0.0   0.0   0.0   0.0 9.|-- 202.97.94.98                         10.0%    10   36.8  33.4  30.3  36.8   2.2 10.|-- 59.43.244.133                         0.0%    10   31.1  34.4  29.9  63.6  10.3 11.|-- 59.43.182.77                         50.0%    10  196.6 196.5 196.4 196.6   0.0 12.|-- 218.30.48.194                         0.0%    10  209.7 208.9 205.9 210.6   1.5 13.|-- 173.254.205.146.static.quadranet.com  0.0%    10  222.7 221.3 208.3 227.9   6.5 14.|-- colo-lax6.as8100.net                  0.0%    10  193.6 205.2 193.4 246.3  20.1 15.|-- sw01.corp.lax.as8100.net              0.0%    10  187.4 187.7 186.8 188.9   0.5 16.|-- repos.lax-noc.com                     0.0%    10  281.9 284.5 271.5 301.2   7.7

2、 Backhaul route tracking test

1. Test with tools. For backhaul route tracking, we can use Best Trace for Linux to test. The test command is as follows. First, use Putty, Pagoda Remote Desktop Assistant, Xshell and other tools to connect to your server through the SSH port, and then execute the following command to test. The IP address after "./besttrace - q 1" is filled in your local IP address.

 #Create a directory mkdir test && cd test #Download Best Trace for Linux and unzip wget  https://cdn.ipip.net/17mon/besttrace4linux.zip  && unzip besttrace4linux.zip #Add Execution Permission chmod +x besttrace #Route Tracking ./besttrace -q 1 123.249.20.130

Display of test results:

 [ root@iZwz981ir3uk69okkbcayiZ  test]# ./ besttrace -q 1 123.249.20.130 traceroute to 123.249.20.130 (123.249.20.130), 30 hops max, 60 byte packets 1  * 2 11.219.126.101 5.00 ms * US defense.gov 3  * 4 11.177.232.118 0.80 ms * US defense.gov 5 42.120.240.30 1.87 ms AS37963 AliCloud, Shenzhen, Guangdong, China/Telecom/Unicom/China Mobile/China Railcom/Ednet 6 42.120.242.225 1.60 ms AS37963 AliCloud, Shenzhen, Guangdong, China/Telecom/Unicom/China Mobile/China Railcom/EduNet 7 183.2.180.165 2.33 ms AS4816 Shenzhen Telecom, Guangdong, China 8 183.2.182.125 2.79 ms AS4816 Shenzhen Telecom, Guangdong, China 9 119.147.219.253 5.88 ms AS4816 Shenzhen Telecom, Guangdong, China 10 202.97.69.102 21.90 ms * Guiyang Telecom, Guizhou, China 11  * 12 219.141.127.50 39.35 ms AS4134 Telecom, Qianxinan Buyei and Miao Autonomous Prefecture, Guizhou, China 13 219.141.127.58 26.15 ms AS4134 Telecom, Qianxinan Buyei and Miao Autonomous Prefecture, Guizhou, China 14  * 15  * 16  * 17 123.249.20.130 25.87 ms AS4134 Telecom, Qianxinan Buyei and Miao Autonomous Prefecture, Guizhou, China

2. Use the command to test. Use Putty, Pagoda Remote Desktop Assistant, Xshell and other tools to connect to the server to be tested for backhaul routing through the SSH port, and run the following command. Note that it is run on the server that needs to be tested for backhaul test, not on other servers. The principle is the routing node that needs to pass when accessing other IPs locally from the server to be tested, which is what we call the backhaul routing test. The IP after "mtr rw" is filled with the known IP that can be pinged.

 mtr -rw 123.249.20.130

The test results are as follows:

 [ root@iZwz981ir3uk69okkbcayiZ  test]# mtr -rw 123.249.20.130 HOST: iZwz981ir3uk69okkbcayiZ Loss%   Snt   Last   Avg  Best  Wrst StDev 1. ???                      100.0    10    0.0   0.0   0.0   0.0   0.0 2. 11.219.126.101           0.0%    10    2.4   2.8   1.8   5.7   1.1 3. ???                      100.0    10    0.0   0.0   0.0   0.0   0.0 4. 11.177.232.118           0.0%    10    0.9   0.9   0.7   1.9   0.4 5. 42.120.240.30            0.0%    10    2.1   2.2   1.6   4.0   0.8 6. 42.120.242.225           0.0%    10    1.8   2.0   1.7   2.6   0.3 7. 183.2.180.165            0.0%    10    2.5   5.9   2.2  38.2  11.4 8. 183.2.182.125            0.0%    10    2.8   4.9   2.7  17.1   4.7 9. 119.147.220.41           0.0%    10    6.7   8.3   5.2  11.4   2.3 10. 202.97.69.90             0.0%    10   21.3  23.1  21.3  24.8   1.4 11. 61.189.251.114          90.0%    10   24.6  24.6  24.6  24.6   0.0 12. 219.141.127.42           0.0%    10   32.7  32.8  32.7  32.8   0.1 13. 219.141.127.58           0.0%    10   25.0  25.1  25.0  25.3   0.1 14. ???                      100.0    10    0.0   0.0   0.0   0.0   0.0 15. ???                      100.0    10    0.0   0.0   0.0   0.0   0.0 16. ???                      100.0    10    0.0   0.0   0.0   0.0   0.0 17. 123.249.20.130           0.0%    10   24.8  24.7  24.7  24.8   0.0