Important:
This content is for reference only. Always consult official vendor documentation for your distribution. Test thoroughly in a lab environment before production use. In case of conflicts, vendor documentation takes precedence.
NVMe-TCP Troubleshooting Flowchart
Diagnostics Command Reference
Network:
ip addr show # Show IP configuration
ip route show # Show routing table
ip link show # Show interface status
ethtool <interface> # Show NIC settings
ping <ip> # Test connectivity
traceroute <ip> # Trace network path
nc -zv <ip> 4420 # Test NVMe-TCP port
NVMe Storage:
lsblk # List block devices
nvme list # List NVMe devices
nvme list-subsys # List NVMe subsystems and paths
nvme discover -t tcp -a <ip> # Discover subsystems
nvme smart-log /dev/nvme0n1 # Check device health
cat /sys/class/nvme-subsystem/nvme-subsys*/iopolicy # Check IO policy
Performance:
iostat -x 1 # I/O statistics
iotop # I/O by process
iftop -i <interface> # Network bandwidth
top # CPU and memory
mpstat -P ALL 1 # Per-CPU statistics
Logs:
journalctl -f # Follow system logs
journalctl -u nvmf-autoconnect # NVMe autoconnect logs
dmesg -T | grep nvme # NVMe kernel messagesCommon Troubleshooting Articles
Connection Issues
Performance Issues
Multipath Issues
-
KB0022959: Paths Showing as Non-Live While Using NVMe-TCP on RHEL/Rocky/AlmaLinux
Boot and Persistence Issues
RHEL-Specific Issues