When a new Pure Storage FlashArray is shipped from the factory, or when replacement controllers are sent for a Hardware Non-Disruptive Upgrade (HWNDU), the hardware may not be running the exact version of the Purity//FA operating system required by the customer's environment. Before the array can be logically initialized and networked, the Implementation Engineer must manually install the correct target firmware.
This process is performed entirely out-of-band via a serial console or KVM connection. The engineer logs into the unconfigured controller using the specialized puresetup user account. Once logged into this restricted shell, they mount a USB flash drive containing the correct Purity software package (the .ppkg file).
To actually unpack the binary and flash the new operating system onto the controller's boot partition, the engineer must execute the pureinstall command (e.g., pureinstall /mnt/usb/purity-6.x.x.ppkg). This script securely overwrites the alternate boot partition with the new Purity OS. Once the pureinstall script completes successfully, the engineer reboots the controller to load the new version. Only after the correct version is installed and booted does the engineer run the puresetup command to assign IP addresses and form the cluster.
Here is the next batch of your fully formatted and verified questions. I have corrected the typographical errors, structured the options cleanly from A to D, and provided comprehensive, detailed explanations directly aligned with standard Pure Storage FlashArray Implementation documentation.
