Which command shows per-network interface statistics, including RX and TX counters and errors?

Prepare for the Google Data Center Technician Exam. Use our interactive quiz featuring flashcards and multiple choice questions with hints and explanations. Get exam-ready today!

Multiple Choice

Which command shows per-network interface statistics, including RX and TX counters and errors?

Explanation:
Per-network interface statistics with RX and TX counters and errors are best retrieved with a command that lists each interface and its detailed summaries. The ip -s link command does exactly that: it iterates over every network device and, for each one, shows receive (RX) and transmit (TX) statistics along with error counters. You’ll see metrics like RX packets, RX errors, RX dropped, TX packets, TX errors, and more for every interface, giving a clear view of how much data has moved and where problems may be occurring on both sides of the traffic. Other options provide related information but not as directly. Ifconfig -a shows historical interface configurations and some basic stats, but it’s an older tool and not as consistently informative across systems. netstat -i gives a quick table of interface stats, but it’s less detailed and not as focused on per-interface RX/TX counters and errors. ethtool <iface> reveals NIC-specific hardware stats and features, which is valuable for driver or hardware issues but isn’t the straightforward per-interface summary you get with ip -s link. So, for a clear, per-interface view of RX/TX counters and errors across all interfaces, ip -s link is the best fit.

Per-network interface statistics with RX and TX counters and errors are best retrieved with a command that lists each interface and its detailed summaries. The ip -s link command does exactly that: it iterates over every network device and, for each one, shows receive (RX) and transmit (TX) statistics along with error counters. You’ll see metrics like RX packets, RX errors, RX dropped, TX packets, TX errors, and more for every interface, giving a clear view of how much data has moved and where problems may be occurring on both sides of the traffic.

Other options provide related information but not as directly. Ifconfig -a shows historical interface configurations and some basic stats, but it’s an older tool and not as consistently informative across systems. netstat -i gives a quick table of interface stats, but it’s less detailed and not as focused on per-interface RX/TX counters and errors. ethtool reveals NIC-specific hardware stats and features, which is valuable for driver or hardware issues but isn’t the straightforward per-interface summary you get with ip -s link.

So, for a clear, per-interface view of RX/TX counters and errors across all interfaces, ip -s link is the best fit.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy