长Ping网络丢包如何排查_ping丢包测试

排查思路

长时间的Ping网络丢包可以通过以下步骤来进行排查：

1. 首先，确认是否存在网络连接问题。尝试通过其他设备或者不同的网络连接进行Ping测试，以确定是否是与特定设备或网络环境相关。

2. 检查本地网络设置。确保网络适配器正常工作，并且配置正确。确认IP地址、子网掩码和默认网关的设置是否正确。

3. 进行基础诊断。使用命令提示符或终端窗口执行ping命令，向目标主机发送一系列的网络数据包，并观察返回的结果。如果出现丢包，则可以根据返回结果中的信息来进一步分析。

4. 分析Ping结果。注意观察丢包率（packet loss）和延迟（latency）等指标。如果丢包率较高，可能是网络连接不稳定或存在网络拥塞。如果延迟较高，可能是网络质量差或者目标主机响应缓慢。

5. 检查网络设备和链路。检查所有相关的网络设备，如路由器、交换机、防火墙等，以确保它们正常工作并没有配置错误。同时，检查物理连接，确保所有电缆连接正确且完好无损。

6. 使用跟踪路由（traceroute）来寻找丢包的位置。执行traceroute命令，追踪到达目标主机的网络路径，并检查每个跳点的延迟和丢包情况。这样可以帮助确定是在本地网络还是在中间网络节点出现了问题。

7. 联系网络服务提供商（ISP）。

Ping命令各种使用姿势

ping 
	-I(指定网卡)  
	-c(设置 ping 的次数，默认无限次，可选) 
	-i(设置 ping 的时间间隔，默认1秒，可选) 
	-W(设置 ping 的超时时间，可选)
	
	-s packetsize （例如1500）
	-l preload ？？ ping -f -l  1500 
	ping -s 1473 -M do x.x.x.x ? MTUcd  
1
2
3
4
5
6
7
8
9

ping 127.0.0.1|awk '{print$0"\t" strftime("%Y-%m-%d %H:%M:%S",systime())}'
ping 本机、网关、127.0.0.1、其他节点
1
2

思路

1、确定上层交换机型号， 交换机端和服务器网卡使用的光纤模块信息。
2、两端都使用的模块一样测试是否会存在丢包。
3、两台服务器直连测试。【测试时要解除bonding测试】。
4、确认操作系统版本、驱动版本、网卡型号。

rx_dropped

ifconfig 网卡
https://blog.csdn.net/maimang1001/article/details/121786580

https://blog.csdn.net/fushengbao/article/details/131460728

port-channel

好的，您想在两台交换机之间创建一个端口聚合（port-channel）。端口聚合是将多个物理接口捆绑在一起以增加带宽和冗余性的技术。

以下是在两台交换机之间创建端口聚合的一般步骤：

1. 使用适当的网络线缆将两台交换机连接起来。
2. 在两台交换机上选择要捆绑的接口，并确保它们都具有相同的速度和双工模式设置。
3. 在每台交换机上进入配置模式（configuration mode）。
4. 在每台交换机上创建一个端口聚合组（port-channel group），通常使用命令类似于interface port-channel <group-number>。请注意，<group-number>是自定义的组号，例如1、2等。
5. 在每台交换机上进入要聚合的接口的配置模式，并将其添加到刚创建的端口聚合组中。这通常需要使用命令类似于channel-group <group-number> mode active。
6. 确保在两台交换机上使用相同的端口聚合组号和聚合模式（例如，active、passive或on）。
7. 配置其他必要的参数，如VLAN、IP地址等，以完成端口聚合的设置。

请注意，不同厂商的交换机可能会有略微不同的命令和配置步骤。因此，在实际进行端口聚合之前，建议参考相关厂商的文档或手册，以确保正确配置。

希望这些信息对您有所帮助！如果您有任何其他问题，请随时提问。

双绞线中T568A线序与T568B线序

https://zhuanlan.zhihu.com/p/550632727?utm_id=0

rp_filter

rp_filter参数用于控制系统是否开启对数据包源地址的校验
即rp_filter参数有三个值，0、1、2，具体含义：
0：不开启源地址校验。
1：开启严格的反向路径校验。对每个进来的数据包，校验其反向路径是否是最佳路径。如果反向路径不是最佳路径，则直接丢弃该数据包。
2：开启松散的反向路径校验。对每个进来的数据包，校验其源地址是否可达，即反向路径是否能通（通过任意网口），如果反向路径不同，则直接丢弃该数据包。

rp_filter（反向路径过滤）的重新设置：反向路径过滤是Linux内核中的一种网络安全功能，用于检查网络数据包的源地址是否符合预期的路径。

丢包率正常范围

丢包率正常范围一般不能大于2%，丢包率高的解决方法：
1、物理线路故障，联系服务商来解决；
2、设备故障，换一条新的模块替换掉光纤模块；
3、网络被堵塞、拥堵，检查fast switching在大流量外出端口是否被禁用，如果是，则需要重新使用；
4、路由错误，直接忽略这些数据丢包。

Ping

PING(8)                                                                            System Manager's Manual: iputils                                                                           PING(8)



NAME
       ping - send ICMP ECHO_REQUEST to network hosts

SYNOPSIS
       ping  [-aAbBdDfhLnOqrRUvV46]  [-c  count] [-F flowlabel] [-i interval] [-I interface] [-l preload] [-m mark] [-M pmtudisc_option] [-N nodeinfo_option] [-w deadline] [-W timeout] [-p pattern]
       [-Q tos] [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp option] [hop ...] destination


DESCRIPTION
       ping uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway.  ECHO_REQUEST datagrams (``pings'') have an IP and ICMP header, followed
       by a struct timeval and then an arbitrary number of ``pad'' bytes used to fill out the packet.

       ping works with both IPv4 and IPv6. Using only one of them explicitly can be enforced by specifying -4 or -6.

       ping can also send IPv6 Node Information Queries (RFC4620).  Intermediate hops may not be allowed, because IPv6 source routing was deprecated (RFC5095).

OPTIONS
       -4     Use IPv4 only.

       -6     Use IPv6 only.

       -a     Audible ping.

       -A     Adaptive  ping.  Interpacket interval adapts to round-trip time, so that effectively not more than one (or more, if preload is set) unanswered probe is present in the network. Minimal
              interval is 200msec for not super-user.  On networks with low rtt this mode is essentially equivalent to flood mode.

       -b     Allow pinging a broadcast address.

       -B     Do not allow ping to change source address of probes.  The address is bound to one selected when ping starts.

       -c count
              Stop after sending count ECHO_REQUEST packets. With deadline option, ping waits for count ECHO_REPLY packets, until the timeout expires.

       -d     Set the SO_DEBUG option on the socket being used.  Essentially, this socket option is not used by Linux kernel.

       -D     Print timestamp (unix time + microseconds as in gettimeofday) before each line.

       -f     Flood ping. For every ECHO_REQUEST sent a period ``.'' is printed, while for ever ECHO_REPLY received a backspace is printed.  This provides a rapid display of how  many  packets  are
              being  dropped.   If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hundred times per second, whichever is more.  Only the super-
              user may use this option with zero interval.

       -F flow label
              IPv6 only.  Allocate and set 20 bit flow label (in hex) on echo request packets.  If value is zero, kernel allocates random flow label.

       -h     Show help.

       -i interval
              Wait interval seconds between sending each packet.  The default is to wait for one second between each packet normally, or not to wait in flood mode. Only super-user may set  interval
              to values less 0.2 seconds.

       -I interface
              interface  is  either an address, or an interface name.  If interface is an address, it sets source address to specified interface address.  If interface in an interface name, it sets
              source interface to specified interface.  For IPv6, when doing ping to a link-local scope address, link specification (by the '%'-notation  in  destination,  or  by  this  option)  is
              required.

       -l preload
              If preload is specified, ping sends that many packets not waiting for reply.  Only the super-user may select preload more than 3.

       -L     Suppress loopback of multicast packets.  This flag only applies if the ping destination is a multicast address.

       -m mark
              use mark to tag the packets going out. This is useful for variety of reasons within the kernel such as using policy routing to select specific outbound processing.

       -M pmtudisc_opt
              Select  Path  MTU Discovery strategy.  pmtudisc_option may be either do (prohibit fragmentation, even local one), want (do PMTU discovery, fragment locally when packet size is large),
              or dont (do not set DF flag).

       -N nodeinfo_option
              IPv6 only.  Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request.  CAP_NET_RAW capability is required.

              help   Show help for NI support.

              name   Queries for Node Names.

              ipv6   Queries for IPv6 Addresses. There are several IPv6 specific flags.

                     ipv6-global
                            Request IPv6 global-scope addresses.

                     ipv6-sitelocal
                            Request IPv6 site-local addresses.

                     ipv6-linklocal
                            Request IPv6 link-local addresses.

                     ipv6-all
                            Request IPv6 addresses on other interfaces.

              ipv4   Queries for IPv4 Addresses.  There is one IPv4 specific flag.

                     ipv4-all
                            Request IPv4 addresses on other interfaces.

              subject-ipv6=ipv6addr
                     IPv6 subject address.

              subject-ipv4=ipv4addr
                     IPv4 subject address.

              subject-name=nodename
                     Subject name.  If it contains more than one dot, fully-qualified domain name is assumed.

              subject-fqdn=nodename
                     Subject name.  Fully-qualified domain name is always assumed.

       -n     Numeric output only.  No attempt will be made to lookup symbolic names for host addresses.

       -O     Report outstanding ICMP ECHO reply before sending next packet.  This is useful together with the timestamp -D to log output to a diagnostic file and search for missing answers.

       -p pattern
              You may specify up to 16 ``pad'' bytes to fill out the packet you send.  This is useful for diagnosing data-dependent problems in a network.  For example, -p ff will  cause  the  sent
              packet to be filled with all ones.

       -q     Quiet output.  Nothing is displayed except the summary lines at startup time and when finished.

       -Q tos Set Quality of Service -related bits in ICMP datagrams.  tos can be decimal (ping only) or hex number.

              In  RFC2474, these fields are interpreted as 8-bit Differentiated Services (DS), consisting of: bits 0-1 (2 lowest bits) of separate data, and bits 2-7 (highest 6 bits) of Differenti‐
              ated Services Codepoint (DSCP).  In RFC2481 and RFC3168, bits 0-1 are used for ECN.

              Historically (RFC1349, obsoleted by RFC2474), these were interpreted as: bit 0 (lowest bit) for reserved (currently being redefined as congestion control), 1-4 for Type of Service and
              bits 5-7 (highest bits) for Precedence.

       -r     Bypass  the  normal  routing tables and send directly to a host on an attached interface.  If the host is not on a directly-attached network, an error is returned.  This option can be
              used to ping a local host through an interface that has no route through it provided the option -I is also used.

       -R     ping only.  Record route.  Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets.  Note that the IP header is only large enough
              for nine such routes.  Many hosts ignore or discard this option.

       -s packetsize
              Specifies the number of data bytes to be sent.  The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data.

       -S sndbuf
              Set socket sndbuf. If not specified, it is selected to buffer not more than one packet.

       -t ttl ping only.  Set the IP Time to Live.

       -T timestamp option
              Set  special IP timestamp options.  timestamp option may be either tsonly (only timestamps), tsandaddr (timestamps and addresses) or tsprespec host1 [host2 [host3 [host4]]] (timestamp
              prespecified hops).

       -U     Print full user-to-user latency (the old behaviour). Normally ping prints network round trip time, which can be different f.e. due to DNS failures.

       -v     Verbose output.

       -V     Show version and exit.

       -w deadline
              Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after  count  packet  are  sent,  it  waits
              either for deadline expire or until count probes are answered or for some error notification from network.

       -W timeout
              Time to wait for a response, in seconds. The option affects only timeout in absence of any responses, otherwise ping waits for two RTTs.

       When using ping for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running. Then, hosts and gateways further and further away
       should be ``pinged''. Round-trip times and packet loss statistics are computed.  If duplicate packets are received, they are not included in the packet loss calculation, although  the  round
       trip  time  of these packets is used in calculating the minimum/average/maximum round-trip time numbers.  When the specified number of packets have been sent (and received) or if the program
       is terminated with a SIGINT, a brief summary is displayed. Shorter current statistics can be obtained without termination of process with signal SIGQUIT.

       If ping does not receive any reply packets at all it will exit with code 1. If a packet count and deadline are both specified, and fewer than count packets are received by the time the dead‐
       line  has  arrived, it will also exit with code 1.  On other error it exits with code 2. Otherwise it exits with code 0. This makes it possible to use the exit code to see if a host is alive
       or not.

       This program is intended for use in network testing, measurement and management.  Because of the load it can impose on the network, it is unwise to use ping during normal operations or  from
       automated scripts.

ICMP PACKET DETAILS
       An  IP  header  without  options  is 20 bytes.  An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth of ICMP header followed by an arbitrary amount of data.  When a packetsize is
       given, this indicated the size of this extra piece of data (the default is 56). Thus the amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be  8  bytes  more
       than the requested data space (the ICMP header).

       If  the data space is at least of size of struct timeval ping uses the beginning bytes of this space to include a timestamp which it uses in the computation of round trip times.  If the data
       space is shorter, no round trip times are given.

DUPLICATE AND DAMAGED PACKETS
       ping will report duplicate and damaged packets.  Duplicate packets should never occur, and seem to be caused by inappropriate link-level retransmissions.  Duplicates may occur in many situa‐
       tions and are rarely (if ever) a good sign, although the presence of low levels of duplicates may not always be cause for alarm.

       Damaged packets are obviously serious cause for alarm and often indicate broken hardware somewhere in the ping packet's path (in the network or in the hosts).

TRYING DIFFERENT DATA PATTERNS
       The  (inter)network  layer  should  never treat packets differently depending on the data contained in the data portion.  Unfortunately, data-dependent problems have been known to sneak into
       networks and remain undetected for long periods of time.  In many cases the particular pattern that will have problems is something that doesn't have sufficient ``transitions'', such as  all
       ones or all zeros, or a pattern right at the edge, such as almost all zeros.  It isn't necessarily enough to specify a data pattern of all zeros (for example) on the command line because the
       pattern that is of interest is at the data link level, and the relationship between what you type and what the controllers transmit can be complicated.

       This means that if you have a data-dependent problem you will probably have to do a lot of testing to find it.  If you are lucky, you may manage to find a file  that  either  can't  be  sent
       across  your  network  or  that  takes much longer to transfer than other similar length files.  You can then examine this file for repeated patterns that you can test using the -p option of
       ping.

TTL DETAILS
       The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away.  In current practice you can  expect  each  router  in  the
       Internet to decrement the TTL field by exactly one.

       The TCP/IP specification states that the TTL field for TCP packets should be set to 60, but many systems use smaller values (4.3 BSD uses 30, 4.2 used 15).

       The  maximum possible value of this field is 255, and most Unix systems set the TTL field of ICMP ECHO_REQUEST packets to 255.  This is why you will find you can ``ping'' some hosts, but not
       reach them with telnet(1) or ftp(1).

       In normal operation ping prints the TTL value from the packet it receives.  When a remote system receives a ping packet, it can do one of three things with the TTL field in its response:

       · Not change it; this is what Berkeley Unix systems did before the 4.3BSD Tahoe release. In this case the TTL value in the received packet will be 255 minus the  number  of  routers  in  the
         round-trip path.

       · Set  it to 255; this is what current Berkeley Unix systems do.  In this case the TTL value in the received packet will be 255 minus the number of routers in the path from the remote system
         to the pinging host.

       · Set it to some other value. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60.  Others may use completely wild values.

BUGS
       · Many Hosts and Gateways ignore the RECORD_ROUTE option.

       · The maximum IP header length is too small for options like RECORD_ROUTE to be completely useful.  There's not much that can be done about this, however.

       · Flood pinging is not recommended in general, and flood pinging the broadcast address should only be done under very controlled conditions.

SEE ALSO
       netstat(1), ifconfig(8).

HISTORY
       The ping command appeared in 4.3BSD.

       The version described here is its descendant specific to Linux.

       As of version s20150815, the ping6 binary doesn't exist anymore.  It has been merged into ping. Creating a symlink named ping6 pointing to ping  will  result  in  the  same  funcionality  as
       before.

SECURITY
       ping  requires  CAP_NET_RAW capability to be executed 1) if the program is used for non-echo queries (See -N option), or 2) if kernel does not support non-raw ICMP sockets, or 3) if the user
       is not allowed to create an ICMP echo socket.  The program may be used as set-uid root.

AVAILABILITY
       ping is part of iputils package and the latest versions are  available in source form at http://www.skbuff.net/iputils/iputils-current.tar.bz2.



iputils-160308                                                                                                                                                                                PING(8)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242