FlashArray-Implementation-Specialist Pure Certified FlashArray Implementation Specialist (FAIS) Exam Questions and Answers

Establishing a serial console session is a fundamental step for initializing a new FlashArray or troubleshooting boot issues. To successfully communicate with the FlashArray controllers via the DB9 or Micro-USB serial port, the terminal emulator (such as PuTTY or TeraTerm) must be configured with specific parameters.

The verified standard settings for all modern FlashArray controllers are:

Baud Rate:115,200(This is faster than the legacy 9600 standard used on older network gear).

Data Bits:8

Parity:None (N)

Stop Bits:1

Flow Control:Xon/Xoff(Software flow control is preferred over hardware RTS/CTS).

Configuring these settings incorrectly (e.g., wrong baud rate) will result in garbled text ("garbage characters") or a completely blank screen when connecting to the console, preventing the engineer from running the puresetup initialization script.

The puresetup initialization script automatically runs a series of network validation tests to ensure the array can reach default gateways, DNS servers, and Pure1. If the management network is not yet live or is air-gapped during the install, these tests will fail, potentially blocking the setup process.

To proceed with the initialization despite the missing network, the Implementation Engineer must append the--skip-management-connectivity-testsflag to the puresetup command.

This flag instructs the script to bypass the ping/DNS lookup checks on the management interface.

It allows the engineer to complete the array initialization (naming, IP assignment) so the array is "up" and ready for local config, with the understanding that full management connectivity will be established and verified later.

=========

The puresupport command suite is used to manage and verify the connectivity between the FlashArray and Pure Storage Support (Pure1). Specifically, to test theRemote Assistfunctionality—which allows Pure Support to securely log in to the array for troubleshooting—the correct command is puresupport test.

While phonehome is a related concept (sending logs out), Remote Assist is a distinct inbound tunnel feature. purearray test pinghome is often confused with phonehome but is an older or specific test for the log sender. The puresupport test command runs a comprehensive check of the support channel connectivity, including the ability to establish the Remote Assist tunnel. If this test passes, the Implementation Engineer can be confident that Support can access the array if needed during or after the deployment.

=========

To reconcile the IP configuration, the Implementation Engineer must correct the invalid netmask to the standard Class C subnet mask of255.255.255.0(Option B).

The netmask provided in the workbook, 255.255.255.223, is mathematically invalid for a subnet mask. Subnet masks function by having a continuous sequence of binary '1's followed by '0's. The decimal value 223 (binary 11011111) breaks this rule due to the zero bit in the middle of the octet. Therefore, the array initialization script would reject this value as a syntax error.

In most standard implementation scenarios where a gateway of 10.24.18.1 is provided, the intended network is a /24 (255.255.255.0), which allows for hosts 10.24.18.1 through 10.24.18.254. While Option C (/23) is a valid subnet mask, it assumes a larger network scope than is typically implied by a standard typo. Correcting the mask to the standard /24 is the safest and most logical remediation to ensure the array can communicate with the gateway and the management network.

To verify the history and transmission status of Phonehome log bundles, the correct command ispurearray phonehome --list.

Before starting a controller upgrade (NDU), it is mandatory to ensure that the array can successfully transmit diagnostic data to Pure Storage. This allows Support to review the "pre-flight" checks and ensures that if an issue occurs during the upgrade, logs will be available for triage.

Usage:Running purearray phonehome --list displays a table of recent log bundles generated by the system.

Verification:The Engineer must look at the Status column for the most recent entries. A status of"uploaded"confirms that the array has successfully connected to the Pure Storage cloud and transferred the data. If the status is "queued" or "failed," the upgrade should not proceed until network connectivity (firewall/proxy) is resolved. Options A and C are incorrect CLI syntax for this specific verification task.

The Purity upgrade process involves two main phases: installing the software image (placing the bits on the boot drive) and then activating it (booting into the new kernel).

After the pureinstall command has successfully unpacked and staged the new Purity version, the changes are not live until the system reboots. In a Non-Disruptive Upgrade (NDU), this is done one controller at a time.

The required step to commit and run the new version is toReboot the controller.

The pureinstall workflow typically prompts for or automatically initiates this reboot.

The secondary controller reboots first, loads the new Purity version, and rejoins the cluster.

Then, the primary controller fails over services to the updated secondary, reboots, and updates itself.

A full "Reboot the array" (simultaneous reboot) would be disruptive and is not the standard procedure for an NDU. "Logging out" has no effect on the system state.

The management ports (typically eth0 and eth1 on the controllers) are the dedicated interfaces for administrative access to the FlashArray. They host the Purity GUI (Graphical User Interface), the CLI (Command Line Interface) via SSH, and the REST API endpoints.

If the customer's network team has failed to provision or patch these ports:

The customer will be unable to log in to the array.There is no other standard path for administration.

While the arraycantechnically serve data over Fibre Channel or iSCSI (if those data ports are connected), the array cannot be managed, monitored, or configured.

The Implementation Engineer can perform the initial setup using the direct serial console connection, but handing over a functional system to the customer requires functioning management networking. Without it, the customer is locked out of the dashboard and cannot perform day-to-day operations.

=========

The FlashArray//XL chassis is designed with specific PCIe lane allocations to support high-performance host I/O and backend connectivity. The 4-Port Fibre Channel (FC) cards are high-bandwidth devices that require x16 PCIe lanes to function at full line rate without oversubscription.

In the FlashArray//XL architecture,PCIe slots 3 and 8are designated x16 slots capable of supporting these dense 4-port host interface cards. Other slots, such as slot 5 or slot 2, may be x8 slots or reserved for other functions (like the backend SAS/Ethernet fabric or offload engines like the DCA), and thus may not physically accept or electrically support the 4-port card variant.

Implementation Engineers must adhere strictly to the slot map provided in the hardware guide. Installing a 4-port card into an unsupported slot (like an x8 slot) could lead to the card not training, the array failing to boot, or the card operating at reduced bandwidth, severely impacting host performance. Verifying the BOM and slot map forSlots 3 and 8ensures the correct electrical and thermal environment for these critical host-facing components.

=========

A valid transfer path forre-using iSCSI cardsduring a controller upgrade is from aFlashArray//XR2 to a FlashArray//XR3(Option A).

Hardware Continuity:The FlashArray//XR2 and //XR3 generations share a high degree of physical component compatibility, particularly regarding PCIe form factors and supported interface cards.

Upgrade Workflow:When performing an "Intra-Series" upgrade (refreshing just the controllers from R2 to R3 to gain CPU performance), the existing I/O cards (Fibre Channel or iSCSI) from the R2 chassis can typically be transferred directly into the new R3 controllers.

Legacy Limitations:Migrating cards from a much olderFlashArray//M(Option B or C) is generally restricted. The //M series often used older generation PCIe cards or different form factors (like onboard risers) that are not validated or physically compatible with the modern PCIe slots found in the //X series. Therefore, for //M to //X upgrades, new I/O cards are usually required, whereas R2 > R3 supports reuse.

Proper airflow and thermal management are critical for the reliability of high-density storage arrays. FlashArray chassis are designed with specific airflow baffles and cooling zones that rely on the drive bays being populated in a specific order.

When installing a new FlashArray with a single data pack (typically 10 drives), the Implementation Engineer must install the DirectFlash Modulesstarting in bay 0, filling from left to right.

Bay 0is typically the leftmost slot (when facing the front of the array).

Filling slots 0–9 ensures that the first "cooling zone" is properly pressurized, forcing air through the populated modules and the chassis midplane correctly.

Leaving gaps (e.g., installing in slots 10–19 while 0–9 are empty) can disrupt the airflow path, potentially leading to hotspots or inefficient cooling for the controllers behind the backplane.

Additionally, the software enumeration of drives often expects contiguous population starting from the lowest index for logical clarity, though cooling is the primary physical constraint.

=========

FlashArray controllers operate in an Active/Active high-availability cluster. Each controller (CT0 and CT1) has its own physical IP address for hardware-level management. However, Purity configures aVirtual IP (VIP)that floats between the two controllers.

TheVirtual management IPis the recommended address for all administrative access, including the GUI, CLI, and API integrations. Using the VIP ensuresHigh Availability (HA)for management sessions. If an Implementation Engineer were to log in directly to CT0's IP and CT0 subsequently rebooted (e.g., during an NDU or failure), the management session would be disconnected.

By contrast, the VIP automatically fails over to the surviving controller (CT1) in the event of a disruption, allowing the management session (and the GUI) to remain accessible. This abstraction layer simplifies administration, as the user does not need to know which controller is currently "primary" for management tasks. Direct controller IPs are typically reserved for specific hardware troubleshooting steps where accessing a specific node is required.

=========

The pureadm command suite is the primary CLI tool used by Implementation Engineers and Support to manage the Purity operating environment's services and high-availability states. After a controller reboot—whether part of a hardware replacement, NDU, or fresh install—it is critical to verify that the Purity software stack has initialized correctly and that all sub-services (such as the I/O handling process, management daemon, and scut) are running.

The specific command pureadm list is the correct syntax to display a summary of the Purity services and their current status (e.g., running, stable, or stopped) on the local controller. This command provides a clean, immediate view of the service stack's health. If the output shows all expected services as "running," the engineer can confirm the controller has successfully rejoined the cluster and is ready to handle operations.

While pureadm alone might print help text and pureadm status is often a valid guess for other systems, the strict syntax for FlashArray implementation verification relies on pureadm list. This step is a standard part of the "Health Check" procedures found in upgrade guides. Failing to verify service status before proceeding (e.g., failing over to the other controller) could lead to an outage if the rebooted controller hasn't actually fully started its data services. Therefore, pureadm list is the validation checkpoint before declaring the controller healthy.

=========

On theFlashArray//XL,PCIe Slot 5is explicitly reserved forNon-Disruptive Upgrade (NDU)procedures and specific control plane functions.

The FlashArray//XL chassis (5U) features a redesigned controller layout with 9 PCIe slots per controller (numbered 0-8). While slots 0-3 and 6-8 are generally available for Host I/O (FC/iSCSI) or Backend Expansion (SAS/NVMe-oF),Slot 5is kept open or populated with specific interconnect cards used during controller upgrades.

During a "Data-in-Place" upgrade (e.g., moving from an //X to an //XL or upgrading //XL generations), this slot facilitates the high-speed link required to cluster the old and new controllers or to transfer state information. Implementation Engineers must ensure this slot is not populated with standard customer I/O cards (like FC HBAs) during the initial configuration, as doing so would block the ability to perform future non-disruptive hardware upgrades.

Complex upgrades that involve both removing old capacity (evacuation) and replacing controllers (hardware NDU) require a "checkpoint" with Pure Storage Support to ensure data safety.

The correct procedure dictates contacting supportafter removing the fully evacuated drives but before proceeding with the hardware NDU.

Why?Once the old drives are physically removed, the array's configuration state has changed. Support needs to verify that the evacuation was 100% successful, that no stale objects or pointers to the removed drives remain in the database, and that the system is fully healthy and redundant.

Proceeding directly into a controller reboot (NDU) without this verification could lead to issues if the array still "thinks" it needs the removed drives, potentially causing a boot failure or data unavailability during the controller failover.

TheFlashArray//Econnects to its DirectFlash Shelves (DFS) using25Gb Ethernet (RoCE).

The FlashArray//E is the "Capacity Optimized" member of the FlashArray family, designed to replace spinning disk repositories with all-flash efficiency. While the high-performance FlashArray//XL utilizes 100GbE for its backend NVMe-oF connectivity to maximize throughput for mission-critical databases, the //E prioritizes cost-efficiency, density, and power consumption.

Architecture:To maintain this efficiency balance, the backend connectivity for expansion shelves on the //E platform is standardized on25GbE. This provides ample bandwidth for the QLC-based workloads (typically unstructured data, repository, or Tier 2 block) without the higher cost and power draw of 100GbE optics and controllers.

Comparison:Option A (40G) is a legacy QSFP standard not used in modern Pure backend designs. Option C (100G) is reserved for the performance-tier //XL and high-end //X models.

The correct pre-implementation step is tomake space in the rack where the chassis is located.

Cabling Standards:DirectFlash Shelves (DFS) connect to the FlashArray via RoCE (RDMA over Converged Ethernet) using QSFP28 cables. The standard cabling kits provided by Pure Storage typically include short-range Passive DACs (e.g., 1m to 3m) or short Active Optical Cables (AOCs).

Distance Constraint:A distance of6 metersbetween racks usually exceeds the length of standard included cables and introduces complexity regarding cable management, signal integrity, and "span" policies. While custom long-range optical cables exist, they are not standard stock and relying on ordering a non-standard "7m" cable (Option B) is a risk.

Best Practice:Pure Storage installation guides explicitly recommend installing expansion shelves in thesame rackand contiguous to the controller chassis whenever possible. This ensures optimal airflow, ease of serviceability, and adherence to standard cabling schematics. Moving the entire controller chassis (Option C) is a disruptive and heavy-lift operation, whereas clearing 3U of space (Option A) is the standard facility preparation task required for a successful deployment.

When installing rails for a FlashArray in a rack requiring cage nuts (square hole racks that are not using the tool-less mechanism, or specific threaded adaptations), the correct placement for the cage nut is thetop square of the lowest Rack Unit (RU)that the rail will occupy.

Pure Storage rail kits typically secure at the bottom of the targeted rack unit.

The "3-Hole" Rule:A standard Rack Unit (1U) consists of three vertical holes (often referred to as the bottom, middle, and top hole).

Alignment:The rail flange is designed to align such that the retaining screw or positioning stud engages specific holes to support the weight. For the standard securement point, the documentation specifies installing the cage nut in thetop holeof the specific RU where the rail base sits (often the "lowest" RU if the device spans multiple U's, though the rail itself is 1U high).

Precision:Placing it in the "Lowest square of the lowest RU" (Option A) would interfere with the rail's shelf lip or the device below it. Correct alignment ensures the rail is level and the chassis slides in without binding.

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.

=========

The correct procedure is tomove the 20TB chassis Data Pack (DP) to the external shelf (SH0)to free up a chassis slot for the new high-capacity pack.

Capacity Analysis:The array has ~52TB total raw capacity (20+10+22) and is 83% full (~43TB used).

Constraint:You cannot simply "evac" the chassis drives (Option A) because the remaining capacity (22TB in the shelf) is insufficient to hold the 43TB of data. Similarly, evacuating the shelf first (Option C) leaves only 30TB in the chassis, which is also insufficient.

The Solution (Option B):

Relocate:The engineer physically moves the 20TB pack from the Chassis (Slot 0) to the empty slot in Shelf 0 (SH0). This is a supported non-disruptive operation (assuming compatible shelf/pack types).

Install:This clears Chassis Slot 0, allowing the installation of the massive91TB Data Pack.

Consolidate:The system now has huge capacity (10+20+22+91). Purity can safely evacuate the old 10TB pack (Chassis) and the external shelf packs (20+22) into the new 91TB internal capacity.

Final State:The array ends up with the single 91TB pack in the chassis, meeting the "X50R2-91/0" target configuration.

For the FlashArray//X50 R2 and R3 models, the default Fibre Channel (FC) configuration utilizes a4-port PCIe Fibre Channel card installed in Slot 0.

The hardware architecture of the FlashArray//X series differentiates slot usage based on the model controller chassis.

FlashArray//X10 and //X20:These lower-end models utilizeSlot 2for host connectivity (Fibre Channel or iSCSI) because Slots 0 and 1 are typically reserved or occupied by onboard controllers/mezzanine cards. The standard card for these models is often a 2-port card.

FlashArray//X50, //X70, and //X90:These mid-to-high-range models feature a different PCIe bus layout.Slot 0is the primary designated slot for Host I/O connectivity. To support the higher performance capabilities and port density requirements of the X50, Pure Storage defaults to4-portFC cards (typically 16Gb or 32Gb).

Therefore, identifying the model number is crucial. Since the question specifies theX50(R2/R3), the correct placement is Slot 0, and the correct card type is the 4-port model. Option A is incorrect because the 2-port card is not the standard default for the performance-tier X50. Option B describes the configuration for an X20, not an X50.

The FlashArray//XL series (such as the XL130R5) utilizes a modern backend connectivity architecture for its expansion shelves, specifically the DirectFlash Shelf (DFS). Unlike older generations that might have used SAS (Serial Attached SCSI) for shelf connectivity, the //XL architecture relies on high-speed Ethernet with RoCE (RDMA over Converged Ethernet) to communicate with external media shelves. This ensures that the NVMe drives in the shelf perform with the same low latency as those in the head unit.

To attach a DirectFlash Shelf to a FlashArray//XL130R5, the chassis must be populated with specific PCIe interface cards designated for shelf back-end connectivity. The correct part for this is theFA-XL-100G Ethernet/RoCE 2-Portcard. This card provides the necessary 100 Gigabit Ethernet bandwidth and RoCE protocol support required for the NVMe-oF (NVMe over Fabrics) backend fabric that Pure Storage uses.

It is crucial to distinguish this from host-facing cards. While an "iSCSI/RoCE" card exists, the shelf connectivity specifically utilizes the "Ethernet/RoCE" designation in the BOM to differentiate backend fabric ports from frontend host ports. The 200G options are generally reserved for host connectivity or inter-array clustering in specific high-performance setups, but the standard validated card for connecting the DFS to the //XL130R5 is the 100G Ethernet/RoCE adapter. Verifying this line item on the BOM prevents onsite delays where the engineer might otherwise find themselves with incompatible ports for the expansion shelves.

At the completion of an upgrade, the correct command to manually trigger the upload of the relevant logs ispurearray phonehome --send-today.

Purpose:This specific argument (--send-today) instructs the array to bundle and upload all log files generated within the current 24-hour window. This is the standard procedure post-upgrade because it ensures that all logs capturing the pre-upgrade state, the upgrade process itself, and the immediate post-upgrade health checks are transmitted to Pure Support.

Verification:This allows the Support team to validate that the upgrade completed successfully and that no dormant issues were triggered during the controller failovers.

Syntax:Option A (purelogs) is not a valid command. Option B (--send-logs) is a generic approximation, but the specific "today" flag is the best practice command cited in upgrade checklists to avoid uploading gigabytes of historical data irrelevant to the immediate event.

DirectFlash Shelves (DFS) are populated with DirectFlash Modules (DFMs) or DFMDs (DirectFlash Module with Distributed NVRAM, though usually just DFMs in shelves). For theGen 2 DirectFlash Shelf, Pure Storage offers specific "starter packs" or partially populated configurations to allow for capacity flexibility while maintaining necessary performance and electrical balance.

The validated starter configurations for a Gen 2 DFS are12-slot and 14-slotpopulations. This means the shelf must be populated with at least this number of drives to be a supported configuration. Populating fewer than this (e.g., 8 or 10) might result in insufficient bandwidth utilization across the shelf's internal fabric or fail strict configuration checks in the Purity operating system. Engineers must verify the drive count matches these supported increments during inventory to avoid configuration errors during initialization.

=========

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.

The FlashArray//XL features a robust2+2power supply unit (PSU) redundancy configuration. Unlike the smaller FlashArray//X chassis (3U), which typically utilizes two power supplies in a 1+1 redundancy setup, the FlashArray//XL utilizes a larger 5U chassis designed for higher performance and density, requiring a more substantial power infrastructure.

The //XL chassis is equipped with four physical Power Supply Units. These are configured to operate in an N+2 mode (effectively 2+2), meaning the system requires two PSUs to support the full electrical load of the chassis, while the other two provide redundancy. This architecture allows the array to survive the simultaneous failure or loss of input power to up to two power supplies without any interruption to service.

This design ensures maximum availability even in scenarios where an entire power grid feed (A-side or B-side) fails, or if multiple hardware components malfunction simultaneously. Options A (1+1) applies to the standard //X series, and Option C (3+1) is not a supported configuration for the FlashArray//XL. The 2+2 design is critical for maintaining the "Always-On" reliability standards required for the mission-critical workloads that the //XL platform supports.

For aDark Sitecustomer (where Remote Assist and PhoneHome are disabled), the appropriate next step before performing a shelf evacuation is touse the evac_checks script.

Risk Mitigation:Evacuating a shelf is a resource-intensive operation that permanently removes physical capacity from the system. In a connected environment, Pure Support runs remote diagnostics to verify the array has enough free space and system resources to handle the evacuation safely.

Dark Site Procedure:Since Support cannot log in remotely, the Implementation Engineer must manually run the evac_checks python script (typically loaded via USB or available in the Purity toolkit). This script performs the equivalent validation: checking effectively used capacity, dedup ratios, and system load to predict if the remaining drives can absorb the data from Shelf 01 without filling the array to 100% or causing performance degradation. Relying solely on a generic percentage (Option B or C) is dangerous because it doesn't account for data reduction overhead or specific RAID overheads.

When performing a Hardware Non-Disruptive Upgrade (HWNDU) or preparing for a Purity software upgrade, the Implementation Engineer must log in with a user account that has full administrative privileges to execute upgrade commands, run health checks, and manage the array state.

Thepureuseraccount is the standard administrative superuser for the FlashArray. It is used for all day-to-day administration and maintenance tasks, including initiating upgrades via the CLI (pureinstall or pureupdate commands) and verifying system health (purearray health, pureadm list). The puresetup account is strictly for initial array initialization (setting IPs and array name) and is disabled or restricted once the array is up and running. pureinstall is a command, not a user account. Therefore, pureuser is the correct authenticated session required to manage the upgrade process.

=========

To facilitate aCapacity Consolidation(CapCon) in a chassis that is physically full (both data pack slots occupied) and logically utilized above the threshold to allow internal evacuation, the standard procedure requirestemporary external capacity, often referred to as "swing gear."

In this scenario, the FlashArray//X20 chassis is fully populated with two 22TB data packs. Since there are no empty slots to insert the new 45TB pack, one of the existing packs must be removed first. However, with the array at80% usage, the data residing on the pack designated for removal (roughly half the raw capacity) cannot fit into the remaining free space of the other pack.

Therefore, Pure Storage Support will provision aDirectFlash Shelf (DFS) containing temporary capacity(e.g., a 63TB pack as mentioned in Option B). The Implementation Engineer attaches this shelf, adds it to the system, and utilizes it as a destination to evacuate data from the old 22TB pack. Once the old pack is empty and removed, the new 45TB pack is installed into the chassis. Finally, the data is moved from the temporary shelf back into the new chassis capacity, and the temporary shelf is disconnected and returned. Option A is incorrect because an empty shelf provides no storage to offload data, and Option C is operationally unfeasible for most customers.

The FlashArray//XR5 (and //E family) introduces a significant architectural shift regarding Non-Volatile RAM (NVRAM). In previous generations (like R2/R3), NVRAM was provided by dedicated PCIe modules installed in specific "NVB" slots in the chassis.

In the //XR5 architecture, Pure Storage moved toDistributed NVRAM. The NVRAM functionality is integrated directly into the DirectFlash Modules (specifically theDFMDs- DirectFlash Module with Distributed NVRAM). This allows the NVRAM capacity to scale with the storage and removes the bottleneck of dedicated slots.

For a system to function correctly, a minimum number of these NVRAM-equipped modules must be present to form the initial write buffer and system quorum. The standard installation requirement for an //XR5 is that thefirst 10 slots (Slots 0-9)are populated with these specific DFMDs. This ensures there is sufficient distributed NVRAM capacity to boot the Purity operating environment and handle incoming writes safely. The Implementation Engineer must populate these slots first before adding standard DFMs in the remaining slots.

=========

To safely stop the Purity operating environment on a specific controller during a physical controller upgrade (such as upgrading from FlashArray//X to //XL or performing a chassis swap), the correct command ispureadm stop.

This command is a system administration utility located in the Linux shell of the controller (accessible via the puresh prompt when logged into the specific controller's physical IP address). It is designed to stop the local Purity services on the node where the command is executed.

Procedure:In a non-disruptive controller upgrade, the engineer manually fails over primary services to the peer controller. Then, they log into the controller designated for removal (e.g., CT0) and run pureadm stop. This ensures that all Purity processes, I/O handling, and cache operations are cleanly terminated and flushed before the hardware is physically powered down or removed.

Syntax:The pureadm tool generally operates on the local instance. Options B and C utilize invalid flags (--secondary or --controller) for this specific command context. The engineer must be physically logged into the target controller to execute the stop command for that node.

To complete the Non-Disruptive Upgrade (NDU) from an//X70R2to an//X90R3using a fully shipped array, the Implementation Engineer must extract and use theControllers and NVRAM modules.

Stateless Architecture:The FlashArray upgrade philosophy allows the chassis and data drives (Data Packs) to remain in place while the compute (controllers) and cache (NVRAM) are swapped.

Component Compatibility:

Controllers:The X90R3 controllers provide the upgraded CPU/performance required.

NVRAM:The NVRAM modules (located in the chassis front or rear slots depending on generation, but logically paired with controller performance) often differ between generations (R2 vs. R3) and performance tiers (70 vs. 90). The X70R2 NVRAM modules are typically not compatible with X90R3 controllers. Therefore, the engineermustswap the NVRAM modules along with the controllers to ensure the write cache is recognized.

Power Supplies:Both the X70R2 and X90R3 utilize the same high-capacity1600W Power Supply Units. Unless the existing PSUs are faulty, they do not technicallyneedto be swapped for the system to function, making "Controller and NVRAM" the precise minimum requirement for the logic upgrade.

To expand a FlashArray//X10 from a5/5(fully populated chassis with two 5TB equivalent packs) to an11/11(two 11TB equivalent packs) configuration, the correct action is toinstall a swing shelf with loan capacity.

The Constraint:The "5/5" notation implies the chassis slots are already occupied by the existing media. Since the customer isreplacingthe existing packs with larger ones (Capacity Consolidation) rather than just adding new ones, the engineer needs a place to put the data during the swap.

Why Swing Shelf:The FlashArray//X10 chassis has limited slots. You cannot simply pull a pack (Option A) if the remaining pack doesn't have enough free space to hold all the data (which is typical in upgrade scenarios). ASwing Shelf(temporary external SAS or NVMe shelf provided by Pure) is attached to the array. The data is evacuated from the internal drives to this shelf. Once the internal slots are empty, the new 11TB packs are installed. The data is then moved back from the shelf to the new packs, and the shelf is removed.

The FlashArray//XL series (specifically the //XLR5 in this context) utilizes a 100 Gigabit Ethernet-based back-end fabric to communicate with DirectFlash Shelves (DFS). This connection relies on the RoCE (RDMA over Converged Ethernet) protocol to ensure low-latency access to the external NVMe modules.

The specific PCIe interface card validated for this connectivity is often labeled in the Bill of Materials (BOM) or configuration guides as the2-Port 100GbE iSCSI/RoCEcard (or simply the 100GbE Ethernet/RoCE card depending on the specific firmware/labeling revision). Crucially, it must be a100GbEcapability card.

The //XL platform standardized on 100GbE for its shelf interconnects, moving away from the 50GbE used in some previous generations of the //X series. The 200GbE cards are typically reserved for high-speed host connectivity or clustering, not the standard shelf loop. Therefore, ensuring the BOM includes the correct 100GbE RoCE-capable cards is essential for successful shelf detection and operation during installation.

When upgrading from a FlashArray//X to a FlashArray//XL, the hardware migration often involves handling DirectMemory Modules (DMMs) differently than standard data drives. DMMs are high-performance cache modules that reside in the controller chassis.

In this specific scenario—migrating a fully populated //X90R3 to an //XL that already has its own set of DirectFlash Modules (DFM-Ds)—the DMMs from the old chassis need to be moved to the new chassis to preserve their cache function or be properly decommissioned.

The correct procedure is toEvacuate DMMs as a datapack then install into any slot in //XL.

DMMs cannot be simply "hot-swapped" randomly while the system is live in a way that disrupts the cache map.

They must be logically grouped and evacuated (conceptually "vacated" of active data) so they can be safely removed from the old chassis.

Once removed, they can be installed into the new //XL chassis. The //XL architecture supports DMMs in specific slots, and Purity will detect and re-incorporate them into the cache pool.

This ensures that the expensive SCM (Storage Class Memory) hardware is reused in the new system without causing data integrity issues during the transition.

=========

When performing a standard installation on a FlashArray, the first logical configuration step is theCT0 configuration(typically via the puresetup utility on the primary controller).

Workflow:After the physical rack-and-stack, cabling, and power-on, the Implementation Engineer must establish a management connection to the array. This is done by connecting to the serial console or the default IP ofController 0 (CT0).

Initialization:The puresetup process on CT0 initializes the system, sets the management IP addresses (VIP, CT0, CT1), and configures the gateway/DNS. This step effectively "builds" the array cluster.

Why not C?While ensuring the array is on the target code version is critical, a "Code Upgrade" is typically performedafterthe array is initialized and network-accessible (or via the Pure1 SSU workflow). The only exception is a manual USB re-image for a factory reset, but the standard installation procedure definesConfiguration/Initializationas the primary step to bring the system online. Configuration of CT1 (Option B) happens automatically as part of the cluster creation initiated from CT0.

After a controller upgrade or any maintenance that involves path failovers, it is critical to verify that the host multipathing software has restored connectivity to all paths and that I/O is being distributed correctly. The specific command to validate this in Purity ispurehost monitor --balance.

purehost monitor --balance: This command provides a real-time view of I/O statistics per initiator (host path). It highlights imbalances where one path might be taking zero traffic while others are overloaded, which typically indicates a pathing configuration issue, a bad cable, or a host that has not correctly rediscovered the path after the controller reboot.

purehost list simply displays configured hosts, not live performance data.

pureport list displays the status of array ports but does not show the per-host I/O distribution required to verify "balance."

=========

During and after a Hardware Non-Disruptive Upgrade (HWNDU), the FlashArray may generate various alerts related to component removals, path failovers, or temporary redundancy reductions. Once the upgrade is physically complete and the software has stabilized, the Implementation Engineer must verify that the array has returned to a fully healthy state.

The commandpurealert listis the primary tool for this verification. It displays the current table of active alerts on the system.

If the array is healthy, this list should be empty or contain only "Info" level messages.

If the system is still recovering, you might see alerts with a status indicating they are "closing" or "downgrading" as the conditions resolve (e.g., "Controller redundancy restored").

pureaudit list shows the history of user commands, not system health alerts. puremaintenance is not a standard command for checking alert status. Therefore, purealert list is the correct command to validate that no critical hardware or software issues remain active after the maintenance window.

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.

The FlashArray//XR4 introduces a new chassis layout and PCIe slot numbering scheme compared to previous generations. For expansion connectivity, specific slots are designated for the backend SAS or Ethernet/RoCE fabric cards that connect to DirectFlash Shelves.

According to the //XR4 hardware guide and expansion best practices,PCIe slot 3is the designated location for the additional expansion interface card required when adding a second DirectFlash Shelf (or for specific shelf configurations). Slots 0 and 1 are often reserved for host I/O or other functions, and slot numbering/priority is strict to ensure the BIOS and Purity software correctly recognize the card function.

Installing the card in the wrong slot (like slot 0 or 4, if those are reserved for other uses or primary I/O) could result in the shelf not being detected, the array failing to boot, or suboptimal performance due to PCIe lane allocation. Therefore, the engineer must install the DFS expansion card intoPCIe slot 3and cable the second shelf to the ports on that specific card to ensure a supported and functional configuration.

To view the currently configured Network Time Protocol (NTP) servers on a FlashArray, the correct command ispurearray list --ntpserver.

Command Hierarchy:While NTP is a networking function, in the Purity CLI object model, time synchronization is considered a global array attribute rather than a specific interface setting. Therefore, it falls under the purearray command namespace.

Usage:Running purearray list --ntpserver returns a list of the IP addresses or FQDNs of the time servers the array is currently using to sync its system clock.

Invalid Options:

purenetwork list (Option B) displays IP interface configurations (IPs, subnets, gateways) but does not list service-level pointers like NTP.

puredns list (Option A) is strictly for DNS nameservers and suffix configurations.

Importance:Verifying NTP is critical for log timestamp accuracy, ActiveCluster mediation, and Kerberos authentication.

ForPhoneHome(telemetry) andRemote Assist(support tunnels) to function correctly,TCP Port 443 (HTTPS)must be open for outbound traffic from all management ports (CT0.ETH0, CT1.ETH0, and the Virtual Management IP).

Pure Storage utilizes a secure, encrypted connection to communicate with the Pure1 Cloud and Support infrastructure.

PhoneHome:The array sends logs and heartbeat data to purestorage.com (and associated subdomains) via HTTPS over Port 443. If this port is blocked, the array cannot report its health status, preventing proactive support.

Remote Assist:This feature creates a reverse SSH tunnel encapsulated over HTTPS (websocket or similar secure transport) to allow Pure Support to remotely log in. It initiates the connectionoutboundto the support relay servers on Port 443.

Option A (Port 80) is generally not used for secure management traffic in modern configurations, often only serving as a redirect. Option C (Port 123) is required for NTP (Network Time Protocol) synchronization, which is critical for logs but is not the transport port for the PhoneHome/Remote Assist data stream itself. Therefore, verifying firewall rules for Port 443 is the primary troubleshooting step.

The Pure1 mobile app provides convenient access to array monitoring and management features from anywhere. Most features, such as viewing performance telemetry (Option A) or managing support tickets (Option B), are cloud-native and accessible over the public internet via the secure Pure1 connection.

However,Opening Remote Assist (RA)—the feature that creates a secure tunnel for Pure Storage Support to access the array remotely—is a privileged security action. To prevent unauthorized external actors from enabling this access, the Pure1 app often enforces a "proximity" or network validation check. The user must be connected to theinternal company network(e.g., via Wi-Fi or VPN) that has visibility to the array's management interface to authorize the Remote Assist session. This requirement ensures that only an authorized administrator physically or logically present within the customer's secure environment can grant external access to the storage system.

=========

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.

=========