NetApp ONTAP Performance Monitoring Commands Guide

When a NetApp cluster starts feeling slow, the fastest way to separate storage latency from client-side issues is the ONTAP command line. This article walks through the official NetApp knowledge base set of performance-monitoring commands — statistics show-periodic, sysstat, statit and wafltop — and explains which columns to read for CPU, disk IOPS and per-drive latency problems in ONTAP 9.

Statistics Show-Periodic: Cluster-Wide View

statistics show-periodic -node node1

Watch the cpu busy column for CPU utilization across domains, the data columns for Ethernet throughput across all NICs, and the cluster columns for Cluster LIF traffic. This is the first command to run when throughput numbers look wrong.

Sysstat: Per-Second CPU and Consistency Points

sysstat -x 1
sysstat -M 1

sysstat -x 1 refreshes every second: CPU shows utilization, CP time shows time flushing consistency points (CPs) from RAM to disk, and CP_Ty is worth watching when you see back-to-back CPs — the classic sign of dirty-buffer pressure. sysstat -M 1 adds the Nwk_Exmpt (network CPU processing) and WAFL_Ex (data processing/WAFL) columns. Note that sysstat, statit and wafltop are node shell commands requiring diagnostic privilege (priv set diag).

Statit: Per-Drive IOPS and Latency Breakdown

statit

Statit shows ut% (percentage of time the disk had I/O commands outstanding), xfers (average IOPS per drive), chain (I/O size in 4 kB units — 1 chain = 4 kB, 2 chains = 8 kB) and usecs (microsecond latency per IOP type per drive). A single drive with high usecs while others stay low points at a failing disk; uniform high latency points at a CP or queueing problem.

Wafltop and QoS Statistics

For workload-level insight use wafltop (per-workload CPU/disk activity) and qos statistics for Adaptive QoS counters. When performance is degraded, correlate these with aggregate space usage — a nearly full aggregate can silently throttle writes — and review ONTAP network configuration best practices if the bottleneck looks like it is on the wire instead of the disk.

Related: ONTAP dedup space errors explained.

原文链接：https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/What_commands_are_useful_to_monitor_the_performance_in_ONTAP_9