Pass the Pure Storage FAIS FlashArray-Implementation-Specialist Questions and answers with Dumpstech

When performing a specific legacy upgrade from aFlashArray FA-405 to a FlashArray//X Series, the 2-Port InfiniBand card must be installed inPCIe Slot 3of the target controller (CT1).

Upgrade Architecture:The legacy FA-400 series utilized InfiniBand (IB) for its high-speed cluster interconnect. The modern FlashArray//X series utilizes PCIe/NTB over an internal midplane or different interconnects. However, during anon-disruptive upgrade (NDU)or data migration where the new //X controller is temporarily clustered with the old FA-405 controller to transfer state and data, they must share a compatible link.

Slot Reservation:The FlashArray//X hardware guide and upgrade procedures strictly designateSlot 3(the top slot on the riser in many //X chassis configurations) as the reserved location for this temporary InfiniBand interconnect card. Installing it in Slot 0 or 2 would conflict with the primary Host I/O or backend connectivity paths, potentially causing the controller to fail the upgrade pre-checks or preventing the cluster from forming.

A "4X Module" kit is specifically designedto widen an existing write group(RAID set).

Write Group Geometry:In standard FlashArray//X configurations, DirectFlash Modules (DFMs) operate in "Write Groups" (typically 10 modules wide for a standard data pack). However, to offer more flexible entry points or capacity expansion options, Pure Storage allows configurations that start with smaller write groups (e.g., 6 modules).

Widening:When a customer wants to expand capacity or performance on these smaller configurations without adding a full new 10-pack, they can purchase a widening kit (in this case, 4 modules).

Process:The Implementation Engineer installs these 4 modules into the empty slots. The Purity operating system then logically integrates these new drives into the existing narrow write group, "widening" it to the standard width (e.g., 6 + 4 = 10). This operation redistributes parity and data across the full set of 10 drives, improving performance and efficiency.

On aFlashArray//X20 (R2 or R3), the default Fibre Channel configuration is a2-port FC card installed in Slot 2.

The FlashArray//X hardware architecture differentiates slot usage based on the controller model:

Entry Level (X10/X20):These controllers have a limited number of PCIe lanes and slots available for user expansion. Slots 0 and 1 are often utilized by internal system components or reserved. Therefore, the primary Host I/O card (FC or iSCSI) is standardly installed inSlot 2. Additionally, due to the entry-level positioning, the 2-port card is the standard default (though 4-port is supported).

Performance Level (X50/X70/X90):As seen in previous questions, these models prioritizeSlot 0for Host I/O and typically default to4-portcards.

The distinction is critical for Implementation Engineers to ensure they are cabling the correct ports. For an X20, cabling Slot 0 (if a port is even visible) would be incorrect; the active host ports are in Slot 2.

On a newFlashArray//XR4installation, the Implementation Engineer must run thecobalt_check.pyscript before executing puresetup newarray.

The FlashArray//XR4 represents a significant hardware architectural shift (internally codenamed or associated with the "Cobalt" platform generation). This platform introduces new PCIe layouts, NVMe backplanes, and controller components that require specific validation beyond the standard legacy checks. The cobalt_check.py script is a specialized hardware diagnostic tool pre-loaded on the manufacturing image of //XR4 controllers.

Its purpose is to verify that the specific hardware components of the R4 platform—such as the status of the internal NVMe interconnects, the correct population of the chassis, and the health of the new controller mainboard—are functioning within strict tolerances. Running this check ensures that the physical layer is 100% healthy before the Purity operating system attempts to initialize the database and claim the storage media. Option A (pureboot list) checks boot versions but not hardware health, and Option C (purehw list) is a general command that might not catch the specific low-level architectural issues the cobalt_check.py script is designed to identify on this specific generation.

To determine the specific model of a replacement controller while in the puresetup or manufacturing shell (before the controller has joined the cluster), the correct command ishwconfig --model.

During a controller replacement procedure, the engineer often connects to the new controller via serial or a temporary IP. At this stage, the full Purity CLI (and thus purearray list) may not be fully available or relevant because the controller is in a "setup" or "unconfigured" state.

hwconfig: This is a lower-level utility used to read the Field Replaceable Unit (FRU) data directly from the hardware VPD (Vital Product Data).

--model: This flag specifically filters the output to display the model string (e.g., FA-X50R3-CT0). Verifying this string is a critical safety step to ensure the replacement hardware matches the existing cluster node before attempting the software join process (puresetup replace).

To verify the status, presence, and admission of a specific data pack, the correct command ispuredrive list --pack CH0.BAY10.

In the context of FlashArray geometry, a "Write Group" (RAID set) is formed by combining DirectFlash Modules. A"Wide Write Group"typically consists of 10 modules (a full data pack). When an engineer installs a standard 10-pack of drives (Bays 10-19), verifying that all 10 drives are successfully recognized and "admitted" confirms that the system has formed the intended wide write group.

The puredrive list command with the --pack argument filters the output to show only the drives in that specific pack. The engineer checks that all 10 drives are listed and their status is"healthy"or"admitted". If fewer drives were admitted (e.g., only 5), it would indicate a "narrow" write group or a hardware issue.

Option A (find_drive.py)is a utility script used to physically locate a drive by blinking its LED, not to check logical RAID configuration.

Option B (puredb list drives)is an internal engineering command (puredb) that is generally not intended for standard field verification and may require root-level access. The puredrive command is the standard CLI tool for this validation.

The FlashArray//X20R4-LL (Low-Line) model is a specific configuration designed for lower capacity and power entry points. Unlike the standard //X or //XL models which can support fully populated chassis and shelves, the "Low-Line" configurations often come with strict hardware limitations regarding power draw and drive count. A known constraint for specific Low-Line chassis upgrades, particularly when moving to the X20R4-LL, is a limitation on the number of DirectFlash Modules (drives) supported due to the power supply unit (PSU) capacity or thermal design targeted for that specific SKU.

In this scenario, if the source array (X20R3) was populated with more drives than the target X20R4-LL supports—specifically more than 10 drives—the upgrade validation checks (such as those performed by the upgrade script or Purity health checks) will flag a failure. Even though the voltage readings are technically correct (indicating the PDUs are providing power), the check fails because the hardware configuration exceeds the supported power budget for that specific chassis model.

Implementation Engineers must verify the drive count of the source array against the specifications of the target "Low-Line" array during the planning phase. If the source array has 11 or more drives, the target hardware cannot be an LL model; it would require a standard model to support the additional power load of the extra drives. This check prevents the array from booting into a state where it might experience power contention or thermal shutdown under load.

=========

DirectFlash Shelves (DFS) connect to the FlashArray controllers using high-speed protocols (typically RoCE - RDMA over Converged Ethernet) that require high-fidelity signal integrity. Due to the high bandwidth (50Gb or 100Gb speeds) and low latency requirements of the NVMe-oF (NVMe over Fabrics) protocol used for backend connectivity, the physical cabling length is strictly limited.

Pure Storage officially supports a maximum cable length of3 metersfor connecting DirectFlash Shelves to the controller or for daisy-chaining shelves (where supported). Cables longer than 3 meters (such as 5m or 7m) introduce signal attenuation and latency that can destabilize the backend fabric, leading to CRC errors, path flapping, or drive disconnections.

Implementation Engineers must ensure that the rack layout allows the shelves to be placed within this 3-meter radius of the controllers. Typically, shelves are racked immediately above or below the controller chassis to minimize cable run distance. Attempting to span across multiple racks using longer, unsupported cables will result in an unsupported configuration and likely immediate I/O errors.

=========

Data evacuation from a shelf is a sensitive background process where data is migrated off specific physical media to free it for removal. While the purearray evacuate command initiates the data movement, the finalization of the process—specifically the logical removal of the shelf object from the system configuration to allow for safe physical disconnection—often requires engineering-level commands or verification.

Therefore, before Pure Storage Support can log in to run these specific completion scripts or verification checks, the Implementation Engineer mustEnable Remote Assist (RA).

Remote Assist creates a secure, outbound SSH tunnel that allows Support to access the array remotely.

Without RA enabled, Support cannot connect to the array to execute the necessary puredrive or internal maintenance commands to mark the shelf as "vacated" and safe to unplug.

Powering off the shelf (Option B) before this step could result in data loss or an array outage if the system still believes data resides there.

=========

During complex maintenance procedures like a controller upgrade or replacement (puresetup replace), it is often necessary to verify the physical hardware identity of the chassis to ensure compatibility with the new controllers or software image.

The commandhwconfig --modelis the specific CLI tool used at the engineering/boot level to return the chassis model string (e.g., FA-X50R3 or FA-XL170). This confirms the hardware platform identity.

hwconfig --all would dump a massive amount of verbose configuration data, making it difficult to quickly identify just the model.

pureversion -a displays the version of the Purity operating system software, not the physical hardware model of the chassis.

Therefore, hwconfig --model is the correct and most efficient command for the Implementation Engineer to validate the hardware platform identity during the upgrade workflow.

=========