A Linux administrator is investigating very slow file transfers and thousands of CRC errors on interface enp2s0 of a file server. The connected switch port is manually configured to 100 Mb/s full-duplex with auto-negotiation disabled. Relevant output from the server is:
Because the switch port is hard-set to 100 Mb/s full-duplex while the Linux NIC is still performing auto-negotiation, the NIC can determine the speed but cannot discover the duplex mode. Following the standard algorithm, it therefore falls back to half-duplex, creating a duplex mismatch. Half-duplex on one side and full-duplex on the other produces late collisions, CRC/FCS errors, and poor performance. Enabling auto-negotiation on the switch allows both ends to exchange their capabilities and agree on 100 Mb/s full-duplex, eliminating the mismatch. Changing the server to 10 Mb/s half-duplex would further reduce throughput, increasing MTU size does not address duplex, and disabling flow control does nothing to resolve collisions created by the mismatch.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is duplex mode in networking?
Open an interactive chat with Bash
What are CRC errors in network communication?
Open an interactive chat with Bash
How does auto-negotiation work in Ethernet networks?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Troubleshooting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access