The introduction of the FlashArray//XR4 and FlashArray//CR4 models represented a massive internal redesign for Pure Storage. Internally, this new hardware generation and its corresponding Baseboard Management Controller (BMC) architecture are codenamed "Cobalt" .

Because the Cobalt architecture leverages a highly complex, modular PCIe Gen4 midplane and swappable OCP 3.0 networking cards, validating that all internal hardware is seated correctly before logically forming the cluster is mandatory. If an NVRAM module, direct-attach backend cable, or OCP card is inserted into the wrong slot, the Purity operating system will fail to map its internal topology correctly, leading to unstable initialization.

To prevent this, Pure Storage engineering developed a specialized pre-flight validation script specifically for the //XR4 and //CR4 platforms. Before an Implementation Engineer executes the puresetup newarray command to define the management IPs and form the cluster, they must log into the local KVM console as the puresetup user and run cobalt_check.py .

This Python script interrogates the motherboard, scans the physical PCIe lanes, verifies the OCP module firmware, and checks the chassis topology against the expected Bill of Materials (BOM). If the script returns a clean "PASS," the engineer is cleared to run puresetup. (Note: Older generations like the //XR3 used a generic hardware_check.py script, but cobalt_check.py is the specific, required tool for the //XR4 family).