200-301 · Question #942
A client experiences slow throughput from a server that is directly connected to the core switch in a data center. A network engineer finds minimal latency on connections to the server, but data…
The correct answer is A. a physical cable fault. An FCS error is a legal sized frame with a bad frame check sequence (CRC error). An FCS error can be caused by a duplex mismatch, faulty NIC or driver, cabling, hub, or induced noise. Sometimes FCS errors will increment when there is induced noise on the physical cable. Perform…
Question
A client experiences slow throughput from a server that is directly connected to the core switch in a data center. A network engineer finds minimal latency on connections to the server, but data transfers are unreliable, and the output of the show interfaces counters errors command shows a high FCS-Err count on the interface that is connected to the server. What is the cause of the throughput issue?
Options
- Aa physical cable fault
- Ba speed mismatch
- Chigh bandwidth usage
- Da cable that is too long
How the community answered
(34 responses)- A59% (20)
- B24% (8)
- C12% (4)
- D6% (2)
Explanation
An FCS error is a legal sized frame with a bad frame check sequence (CRC error). An FCS error can be caused by a duplex mismatch, faulty NIC or driver, cabling, hub, or induced noise. Sometimes FCS errors will increment when there is induced noise on the physical cable. Perform a cable test. Check the environment for electrical changes (industrial electrical motor turning on, EMI radiation, etc.). Make sure your physical wiring is safe from Electro-magnetic interference.
Topics
Community Discussion
No community discussion yet for this question.