EC2 OS/Kernel Symptom Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EC2 OS/kernel symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 5 | Network packets dropped and new connections fail to establish | ethtool -S eth0 showing conntrack_allowance_exceeded | Connection tracking exceeded the maximum allowance for the instance type, preventing new connections from being established. | N/A |
| 6 | ENA Express falls back to standard ENA transmission, increasing the possibility of dropped packets | ethtool -S eth0 | grep ena_srd showing high ena_srd_resource_utilization | The network card attached to the instance has used up its maximum memory utilization for concurrent SRD connections. | N/A |
| 7 | Eligible outgoing SRD packets fall back to standard ENA transmission | Significant differences between ena_srd_eligible_tx_pkts and ena_srd_tx_pkts | An eligible packet is over the maximum transmission unit (MTU) limit, causing it to fall back to standard ENA transmission. | sudo ip link set dev eth0 mtu 8900 |
| 8 | Traffic to the DNS service, Instance Metadata Service, or Amazon Time Sync Service is dropped | ethtool -S eth0 showing linklocal_allowance_exceeded | The packet-per-second (PPS) traffic to local proxy services exceeded the maximum allowance for the network interface. | N/A |