Interface Errors & Dropped Packets: ip -s link, ifconfig
Interface Errors & Dropped Packets: ip -s link, ifconfig
Monitor network interface errors and dropped packets to track network health, detect connectivity issues, and ensure reliable network performance. This guide shows you how to check network errors and set up automated monitoring.
For comprehensive network monitoring, see Network Health Monitoring. For troubleshooting network issues, see Network Connectivity Issues.
Why Checking Network Errors Matters
Network interface errors and dropped packets indicate network problems that can cause connectivity issues, slow performance, and service failures. Monitoring network errors helps detect and resolve network issues early.
Method 1: Check Network Interface Statistics
View Interface Statistics
# Check network interface statistics
ip -s link show
# Check specific interface statistics
ip -s link show eth0
# View detailed statistics
ip -s -s link show eth0
# Check errors and dropped packets
ip -s link show eth0 | grep -E "errors|dropped"
Monitor Network Errors
# Get error statistics
ip -s link show eth0 | grep -A 5 "RX:"
# Count receive errors
ip -s link show eth0 | grep "RX:" | awk '{print $3}'
# Count transmit errors
ip -s link show eth0 | grep "TX:" | awk '{print $3}'
# Count dropped packets
ip -s link show eth0 | grep -E "dropped" | awk '{sum+=$2} END {print sum}'
Method 2: Check Network Errors with ifconfig
View Interface Statistics
# Check interface statistics
ifconfig eth0
# View errors and dropped packets
ifconfig eth0 | grep -E "errors|dropped|collisions"
# Get error counts
ifconfig eth0 | grep "RX errors" | awk '{print $3}'
ifconfig eth0 | grep "TX errors" | awk '{print $3}'
Method 3: Check Network Errors from /proc
Monitor Network Statistics
# Check network interface statistics
cat /proc/net/dev
# Get error statistics for specific interface
cat /proc/net/dev | grep eth0
# Parse error statistics
cat /proc/net/dev | grep eth0 | awk '{print "RX errors:", $4, "TX errors:", $12, "RX dropped:", $5, "TX dropped:", $13}'
Method 4: Automated Network Error Monitoring with Zuzia.app
Manual checks work while you are looking. To keep running them without you, Zuzia uses its agent and scheduled tasks.
How it works in Zuzia
- Install the Zuzia agent on the server with one command. CPU, RAM, disk, load and network metrics start reporting on their own, with alerts on a threshold, on drift from the server's normal, or on a disk fill-up forecast.
- Save the commands from this guide as a scheduled task and choose how often it runs, from every minute to once a year. The agent runs it on every host you pick.
- If a command fails, you get an alert right away by email, Slack, Discord, push (through your Pushover account) or SMS (through your Vonage account).
- The output of every run is kept, so you can look back at what changed. On paid plans, AI can read the output and alert you only when it spots a problem.
Setting it up
- Add the server in the Zuzia dashboard and install the agent.
- Create a scheduled task with the check commands below, then choose the hosts and how often it runs.
- Choose your notification channels. Turn on maintenance mode during planned work so it doesn't trigger alerts.
Best Practices for Network Error Monitoring
1. Monitor Network Errors Continuously
- Track error counts regularly
- Alert when errors exceed thresholds
- Monitor error trends over time
- Optimize network configuration based on data
2. Distinguish Error Types
- Monitor RX errors separately from TX errors
- Track dropped packets separately
- Investigate root causes of different error types
- Optimize based on error patterns
3. Set Appropriate Thresholds
- Set thresholds based on network capacity
- Adjust thresholds for different interface types
- Monitor errors during peak traffic
- Alert on error spikes
4. Correlate Errors with Performance
- Compare errors with network performance
- Monitor errors during peak traffic
- Track error patterns
- Identify network bottlenecks
Troubleshooting Network Error Issues
Step 1: Identify Network Problems
When network errors are high:
# Check current error statistics
ip -s link show eth0
# Check error types
ip -s link show eth0 | grep -E "errors|dropped"
# Check network connectivity
ping -c 5 gateway-ip
# Review network logs
dmesg | grep -i "eth0\|network\|error"
Step 2: Resolve Network Issues
Based on investigation:
Fix Network Hardware:
- Check network cables
- Replace faulty network cards
- Fix network hardware issues
Optimize Network Configuration:
- Tune network settings
- Optimize interface configuration
- Update network drivers
Scale Network Infrastructure:
- Add network capacity if needed
- Implement network optimization
- Upgrade network equipment
FAQ: Common Questions About Network Error Monitoring
How often should I check network errors?
For production servers, continuous automated monitoring is essential. Zuzia.app can check network errors every few minutes, storing historical data and alerting you when errors exceed thresholds.
What is considered high network error rate?
High network error rate depends on your network capacity and traffic volume. Generally, any consistent errors indicate potential issues and should be investigated. Set thresholds based on your network requirements.
How do I reduce network errors?
Reduce network errors by fixing network hardware issues, optimizing network configuration, updating network drivers, ensuring proper network cabling, and monitoring network performance continuously.
Can network error monitoring impact network performance?
Network error monitoring commands have minimal impact on network performance when done correctly. Use appropriate monitoring frequency and avoid monitoring during peak traffic periods.
Related guides, recipes, and problems
Related guides
guides--monitoring-network-bandwidth-linux.mdguides--network-health-monitoring-server-management.md
Related recipes
recipes--monitor-network-errors-dropped-packets.mdrecipes--monitor-network-connections-linux.md
Related problems
problems--network-connectivity-issues-linux.mdproblems--server-slow-performance-issues.md