linux – 在接口上丢弃数据包

前端之家收集整理的这篇文章主要介绍了linux – 在接口上丢弃数据包前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我正在运行centos 6.2并且其中一个接口具有高丢包.
这是来自ethtool的信息,这是一个网络问题吗?
  1. [root@w native]# ifconfig eth1
  2. eth1 Link encap:Ethernet HWaddr 10:1F:74:2E:6A:80
  3. UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
  4. RX packets:38459399 errors:0 dropped:38459399 overruns:0 frame:0
  5. TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
  6. collisions:0 txqueuelen:1000
  7. RX bytes:2334427918 (2.1 GiB) TX bytes:258 (258.0 b)
  8.  
  9. [root@wye native]# ethtool eth1
  10. Settings for eth1:
  11. Supported ports: [ TP ]
  12. Supported link modes: 1000baseT/Full
  13. 10000baseT/Full
  14. Supports auto-negotiation: Yes
  15. Advertised link modes: 1000baseT/Full
  16. 10000baseT/Full
  17. Advertised pause frame use: No
  18. Advertised auto-negotiation: No
  19. Speed: 1000Mb/s
  20. Duplex: Full
  21. Port: Twisted Pair
  22. PHYAD: 1
  23. Transceiver: internal
  24. Auto-negotiation: on
  25. MDI-X: Unknown
  26. Supports Wake-on: g
  27. Wake-on: d
  28. Link detected: yes
  29.  
  30.  
  31. [root@w native]# ethtool -k eth1
  32. Offload parameters for eth1:
  33. rx-checksumming: on
  34. tx-checksumming: on
  35. scatter-gather: on
  36. tcp-segmentation-offload: on
  37. udp-fragmentation-offload: off
  38. generic-segmentation-offload: on
  39. generic-receive-offload: on
  40. large-receive-offload: off
  41.  
  42. [root@w native]# ethtool -S eth1
  43. NIC statistics:
  44. tx_events: 12086471
  45. rx_crc_errors: 0
  46. rx_alignment_symbol_errors: 0
  47. rx_pause_frames: 0
  48. rx_control_frames: 0
  49. rx_in_range_errors: 0
  50. rx_out_range_errors: 0
  51. rx_frame_too_long: 0
  52. rx_address_match_errors: 163123495
  53. rx_dropped_too_small: 0
  54. rx_dropped_too_short: 0
  55. rx_dropped_header_too_small: 0
  56. rx_dropped_tcp_length: 0
  57. rx_dropped_runt: 0
  58. rxpp_fifo_overflow_drop: 0
  59. rx_input_fifo_overflow_drop: 0
  60. rx_ip_checksum_errs: 0
  61. rx_tcp_checksum_errs: 4
  62. rx_udp_checksum_errs: 2
  63. tx_pauseframes: 0
  64. tx_controlframes: 0
  65. rx_priority_pause_frames: 0
  66. pmem_fifo_overflow_drop: 0
  67. jabber_events: 0
  68. rx_drops_no_pbuf: 0
  69. rx_drops_no_txpb: 0
  70. rx_drops_no_erx_descr: 0
  71. rx_drops_no_tpre_descr: 0
  72. rx_drops_too_many_frags: 0
  73. rx_drops_invalid_ring: 0
  74. forwarded_packets: 35
  75. rx_drops_mtu: 0
  76. eth_red_drops: 0
  77. be_on_die_temperature: 50
  78. rxq0: rx_bytes: 2299912112
  79. rxq0: rx_pkts: 38331860
  80. rxq0: rx_polls: 37803085
  81. rxq0: rx_events: 0
  82. rxq0: rx_compl: 38331860
  83. rxq0: rx_mcast_pkts: 14
  84. rxq0: rx_post_fail: 0
  85. rxq0: rx_drops_no_skbs: 0
  86. rxq0: rx_drops_no_frags: 0
  87. rxq1: rx_bytes: 3398729
  88. rxq1: rx_pkts: 16154
  89. rxq1: rx_polls: 9846
  90. rxq1: rx_events: 0
  91. rxq1: rx_compl: 16154
  92. rxq1: rx_mcast_pkts: 3392
  93. rxq1: rx_post_fail: 0
  94. rxq1: rx_drops_no_skbs: 0
  95. rxq1: rx_drops_no_frags: 0
  96. rxq2: rx_bytes: 206100
  97. rxq2: rx_pkts: 3379
  98. rxq2: rx_polls: 3379
  99. rxq2: rx_events: 0
  100. rxq2: rx_compl: 3379
  101. rxq2: rx_mcast_pkts: 3319
  102. rxq2: rx_post_fail: 0
  103. rxq2: rx_drops_no_skbs: 0
  104. rxq2: rx_drops_no_frags: 0
  105. rxq3: rx_bytes: 30735472
  106. rxq3: rx_pkts: 105087
  107. rxq3: rx_polls: 105087
  108. rxq3: rx_events: 0
  109. rxq3: rx_compl: 105087
  110. rxq3: rx_mcast_pkts: 11078
  111. rxq3: rx_post_fail: 0
  112. rxq3: rx_drops_no_skbs: 0
  113. rxq3: rx_drops_no_frags: 0
  114. rxq4: rx_bytes: 180245
  115. rxq4: rx_pkts: 2998
  116. rxq4: rx_polls: 2998
  117. rxq4: rx_events: 0
  118. rxq4: rx_compl: 2998
  119. rxq4: rx_mcast_pkts: 2984
  120. rxq4: rx_post_fail: 0
  121. rxq4: rx_drops_no_skbs: 0
  122. rxq4: rx_drops_no_frags: 0
  123. txq0: tx_compl: 0
  124. txq0: tx_bytes: 0
  125. txq0: tx_pkts: 0
  126. txq0: tx_reqs: 0
  127. txq0: tx_wrbs: 0
  128. txq0: tx_compl: 0
  129. txq0: tx_stops: 0
  130. txq1: tx_compl: 0
  131. txq1: tx_bytes: 0
  132. txq1: tx_pkts: 0
  133. txq1: tx_reqs: 0
  134. txq1: tx_wrbs: 0
  135. txq1: tx_compl: 0
  136. txq1: tx_stops: 0
  137. txq2: tx_compl: 0
  138. txq2: tx_bytes: 0
  139. txq2: tx_pkts: 0
  140. txq2: tx_reqs: 0
  141. txq2: tx_wrbs: 0
  142. txq2: tx_compl: 0
  143. txq2: tx_stops: 0
  144. txq3: tx_compl: 0
  145. txq3: tx_bytes: 0
  146. txq3: tx_pkts: 0
  147. txq3: tx_reqs: 0
  148. txq3: tx_wrbs: 0
  149. txq3: tx_compl: 0
  150. txq3: tx_stops: 0
  151. txq4: tx_compl: 3
  152. txq4: tx_bytes: 258
  153. txq4: tx_pkts: 3
  154. txq4: tx_reqs: 3
  155. txq4: tx_wrbs: 6
  156. txq4: tx_compl: 3
  157. txq4: tx_stops: 0
  158. txq5: tx_compl: 0
  159. txq5: tx_bytes: 0
  160. txq5: tx_pkts: 0
  161. txq5: tx_reqs: 0
  162. txq5: tx_wrbs: 0
  163. txq5: tx_compl: 0
  164. txq5: tx_stops: 0
  165. txq6: tx_compl: 0
  166. txq6: tx_bytes: 0
  167. txq6: tx_pkts: 0
  168. txq6: tx_reqs: 0
  169. txq6: tx_wrbs: 0
  170. txq6: tx_compl: 0
  171. txq6: tx_stops: 0
  172. txq7: tx_compl: 0
  173. txq7: tx_bytes: 0
  174. txq7: tx_pkts: 0
  175. txq7: tx_reqs: 0
  176. txq7: tx_wrbs: 0
  177. txq7: tx_compl: 0
  178. txq7: tx_stops: 0

解决方法

您能提供有关服务器或应用程序正在做什么的任何信息吗?假设您有一个托管交换机,交换机端口上是否有相应的错误

>通常,首先检查物理位(布线).
>检查相关交换机端口上的接口统计信息(您标记了这个debian,那么您是否在两个系统之间发送数据?)
>使用接口错误检查系统上的系统负载和处理器利用率.
>运行测试.如果您是两台服务器之间的通信,那么iperf对于此类测试来说是一个很好的网络负载生成器.
>如果这是一致的或可重复的,您可以分析相关接口的tcpdump.
>可选 – 探索sysctl.conf设置……这实际上取决于您的服务器正在做什么.如果这是一个消息传递应用程序或需要大量的东西,我们可以查看网络缓冲区设置等.我也一直在玩dropwatch实用程序described here.

猜你在找的Linux相关文章