Pearson FlashArray-Implementation-Specialist New Attempt

When submitting a Pure Engagement Request (PER) or an Implementation Workbook (IWB) for a new Pure Storage FlashArray deployment, adhering to the strict naming conventions of the Purity//FA operating system is critical to ensure a smooth, error-free initialization. In this scenario, attempting to name the array "123" will cause the puresetup script to immediately reject the configuration.

According to the official FlashArray deployment documentation, a valid array name must adhere to specific alphanumeric rules. While the name can certainly contain numbers and hyphens (e.g., Prod-Array-01), it must always begin with a letter . It cannot begin with a digit, nor can it consist entirely of numbers. Furthermore, the name must be between 1 and 63 characters in length, and it cannot end with a hyphen.

Because "123" begins with a numeric digit, it violates the foundational naming schema required by the Purity OS for DNS resolution, Call Home telemetry tagging, and ActiveCluster synchronous replication identification. The Implementation Engineer must work with the customer to revise the array name in the IWB to a compliant format (such as FA-123 or Storage123) before proceeding with the onsite deployment and running the serial console initialization scripts.

Pure Storage enforces strict naming conventions for FlashArrays to ensure compatibility with network protocols (like DNS), replication pairing, and fleet management tools. The allowable character set for an array name is alphanumeric characters (A-Z, a-z, 0-9) and hyphens (-).

The proposed name "corporate Lab-0L" contains a space character between "corporate" and "Lab-0L". FlashArray names cannot contain spaces .

Hyphens (Option A) are allowed and commonly used (e.g., FlashArray-01).

Numbers (Option B) are allowed (e.g., Lab-01).

To resolve the error, the Implementation Engineer should replace the space with a hyphen or remove it entirely (e.g., corporate-Lab-0L or corporateLab-0L). This restriction prevents issues with CLI parsing and host hostname resolution where spaces are often interpreted as delimiters.

The FlashArray//XL currently supports a maximum of 2 DirectFlash Shelves (DFS) .

The FlashArray//XL is a high-density, performance-optimized platform housed in a 5U chassis.

Rack Unit Math: According to the FlashArray//XL specifications and site planning guide, the system supports a maximum configuration footprint of 11 Rack Units (11U) .

The base controller chassis occupies 5U .

Each DirectFlash Shelf occupies 3U .

Therefore: 5U (Base) + 3U (Shelf 1) + 3U (Shelf 2) = 11U .

Capacity: Because the //XL chassis itself holds 40 DirectFlash Modules (compared to 20 in a standard //X), and each shelf holds 28 modules, a fully populated system with two shelves provides nearly 100 drives of capacity (40 + 28 + 28 = 96 drives). This massive density reduces the need for "daisy-chaining" large numbers of shelves like legacy SAS architectures. Adding a third shelf would push the total height to 14U, exceeding the current platform definition.

When expanding a Pure Storage FlashArray//XL130 R5 with an external DirectFlash Shelf (DFS), the backend connection between the shelf controllers and the main chassis relies on massive 100GbE bandwidth via the NVMe-oF (RoCE) protocol. Validating the Bill of Materials (BOM) before an onsite installation is a critical preparatory step to ensure the correct internal hardware was shipped to support this connection.

According to the official Pure Storage hardware matrix, the supported PCIe expansion card required for //XL series shelf connectivity is the FA-XL-100G Ethernet/RoCE 2-Port CX6 . This card utilizes the modern Mellanox/Nvidia ConnectX-6 (CX6) chipset, which is explicitly engineered to provide the necessary 100GbE RDMA capabilities to maintain ultra-low latency, NVMe-level speeds across the external storage fabric.

Option B (the CONNECTX-5 card) is an older, End-of-Sale component generally associated with legacy deployments or specific frontend iSCSI requirements, not the modern //XL backend loop. Option C (a 200G CX7 card) is not the standard validated BOM component for a single DFS loop on an //XL130 R5. Confirming the presence of the 100G CX6 card ensures the engineer has the exact hardware required to successfully cable the 100GbE backend ports.