Which set of commands should be used for troubleshooting Ethernet connectivity problems from the storage system console?

• A. ifstat, netdiag
• B. perfstat, tracert
• C. sysconfig - cr, sysstat
• D. dishshm_stats, sysstat

Answer: (A)

When diagnosing Ethernet connectivity from the storage system console, you want both visibility into the network interface and the ability to test reachability. Ifstat provides per‑interface counters (traffic in/out, errors, drops, etc.), so you can see if the NIC is actually handling traffic and if there are link- or data-path issues. Netdiag adds quick, practical network tests and status checks—pinging peers, verifying routes, ARP, DNS, and overall interface health—so you can confirm reachability and identify where the path fails.

This combination is ideal because it immediately reveals whether the problem is at the local link (bad cable, NIC, or switch port) or somewhere beyond the storage system, while other options focus more on performance metrics, tracing the path, or tools not as targeted to Ethernet health on the console.