blocks|key|875423|text|我找到了民族工具，它允许我诊断我的网卡自动配置为100/半。把它改得满满的，问题就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://linux.about.com/od/commands/l/blcmdl8_ethtool.htm^0|4|4|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

I found <a href="http://linux.about.com/od/commands/l/blcmdl8_ethtool.htm" rel="nofollow noreferrer">ethtool</a> which allowed me to diagnose that my NIC auto-configured to 100/half. Changed it to full and was problems went away.

blocks|key|4975936|text|更换电缆，然后改变端口，然后开关，然后发送网卡，然后接收网卡，然后发送主板，然后接收主板。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Replace the cable, then change ports, then the switch, then the sending NIC, then the receiving NIC, then the sending motherboard, then the receiving motherboard.

blocks|key|4976013|text|你的网卡也是100全双工吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4976014|开关日志中有错误吗？|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Is your NIC set to 100 full duplex too?

Are there any errors in the switch log?

blocks|key|4975985|text|通常是电缆或网卡，如果网络上有其他与交换机一起工作的系统，那么它可能不是交换机。若要测试是否可以使用其他端口，只需查看交换机上是否有一两个坏端口(取决于每次要测试的切换到不同端口的端口)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4975986|先修补电缆，然后再看NIC，我会说。如果有活动灯，您也可以检查和查看是否有什么东西正在关闭交换机，即网络上感染的东西和淹没交换机的路由表。tcpdump或wireshark可能会告诉你一些这方面的事情。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Usually it's cabling or nic, if you have other systems on the network that are working with the switch then it may not be the switch. To test that you can just use other ports to see if the switch as a bad port or two on it (depending on which you switch out to a different port each time to test).

Patch cables first, then look at NICs, I'd say. If there's activity lights you can also check and see if something is slamming the switch, i.e., something infected on the network and flooding the switch's routing table. tcpdump or wireshark might tell you something about that.

blocks|key|4976090|text|考虑到在以全双工方式运行的微分割网络上不可能发生冲突。也许它们不是碰撞，而是ICMP源Quench请求？更多信息--+这里、这里和这里。最近，我看到许多较新的设备报告ICMP源Quench请求为冲突。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/ICMP_Source_Quench|1|http://www.symantec.com/business/security_response/attacksignatures/detail.jsp?asid=20012|2|http://www.freesoft.org/CIE/RFC/896/8.htm|3|http://www.networksorcery.com/enp/protocol/icmp/msg4.htm^0|12|B|0|1N|2|1|1Q|2|2|1T|2|3^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]|$A|U|B|V|1|W]|$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]|K|$5|F|G|H|C|$I|L]]|M|$5|F|G|H|C|$I|N]]|O|$5|F|G|H|C|$I|P]]]]

Consider that a collision is impossible on a microsegmented network running at full duplex. Perhaps they are not collisions, but <a href="http://en.wikipedia.org/wiki/ICMP_Source_Quench" rel="nofollow noreferrer">ICMP Source Quench</a> requests? More information <a href="http://www.symantec.com/business/security_response/attacksignatures/detail.jsp?asid=20012" rel="nofollow noreferrer">here</a>, <a href="http://www.freesoft.org/CIE/RFC/896/8.htm" rel="nofollow noreferrer">here</a>, and <a href="http://www.networksorcery.com/enp/protocol/icmp/msg4.htm" rel="nofollow noreferrer">here</a>. Lately, I have seen many newer devices reporting ICMP Source Quench requests as collisions.

I recently attempted to transfer a 3 GB file to a machine on my LAN using rsync -azvP. I noticed I was only getting 50kpbs. Both switch ports are 100/full. When I do an ifconfig, here's what I get:

<pre><code>eth0 Link encap:Ethernet HWaddr 00:30:48:2E:A3:78 
 inet addr:172.16.0.1 Bcast:172.16.0.255 Mask:255.255.255.0
 inet6 addr: fe80::230:48ff:fe2e:a378/64 Scope:Link
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:747209956 errors:0 dropped:0 overruns:0 frame:0
 TX packets:864422049 errors:16806813 dropped:0 overruns:0 carrier:16806813
 collisions:20239785 txqueuelen:1000 
 RX bytes:793010164 (756.2 MiB) TX bytes:2059589267 (1.9 GiB)
 Base address:0x4000 Memory:da400000-da420000
</code></pre>

I noticed: 
TX packets:864422049 errors:16806813
and
collisions:20239785

Looks like I'm getting errors and collisions. Is there something obvious that I'm missing? My next step is to change the cable. What if that is unsuccessful?

How do I diagnose slow file transfers from NIC errors/collisions?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

最近，我试图使用rsync -azvP将一个3GB文件传输到局域网上的一台机器上。我注意到我的体重只有50公斤。两个交换机端口都是100/满。当我执行ifconfig时，下面是我得到的内容：eth0      Link encap:Ethernet  HWaddr 00:30:48:2E:A3:78            inet addr:172.16.0.1  Bcast:172.16.0.2

问如何诊断来自NIC错误/冲突的慢文件传输？
EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断来自NIC错误/冲突的慢文件传输？EN

回答 5

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断来自NIC错误/冲突的慢文件传输？
EN