During a hardware upgrade, software update, or initial deployment, FlashArray controllers are frequently rebooted. When a controller comes back online, the underlying Linux kernel boots first, followed by the proprietary Purity//FA operating system services. It is an essential responsibility of the Implementation Engineer to verify that the controller has not just powered on, but has successfully loaded its storage processes and rejoined the high-availability cluster.
The definitive Purity CLI command used to validate this state is pureadm list .
Executing pureadm list outputs a clear, tabular view of the array's cluster topology. It displays the hostname of both controllers (CT0 and CT1) and explicitly lists their current operational state.
A healthy cluster will show one controller in the "Primary" state (actively handling backend drive negotiations and primary administrative duties) and the other in the "Ready" / "Secondary" state.
If a controller has rebooted but the Purity services have not fully started, or if it is struggling to synchronize its NVRAM mirror with the primary node, pureadm list will flag that controller's status as "Offline," "Updating," or "Not Responding."
Options like pureadm status or purecluster status are fabricated syntaxes. The standard, unmodified pureadm list command is the documented best practice for verifying that Purity services have cleanly initialized and High Availability (HA) is restored.
