FlashArray-Implementation-Specialist Questions and Answers

The command purehw list --enclosures displays detailed information about shelf enclosures and their cable connections, helping verify physical connectivity.

The command purenetwork list --all provides a comprehensive view of all network interfaces and their status on the FlashArray.

For an NDU from FlashArray//X70R2 to //X90R3, the minimum required hardware from the shipped array is the controllers, which are swapped into the existing chassis and power infrastructure.

Mirrored Write statistics appear in the Purity GUI’s Analysis section when ActiveCluster is enabled, as it tracks synchronous replication activity between clusters.

The purehost iobalance --check command validates whether I/O is balanced evenly across initiators, helping ensure optimal performance and distribution.

FlashArray ActiveCluster is designed for synchronous replication between two FlashArray systems, enabling active-active configurations across two sites. This setup allows both arrays to serve I/O simultaneously, providing high availability and zero RPO (Recovery Point Objective). Each array in the ActiveCluster configuration maintains identical volume identities, ensuring seamless access for hosts regardless of the array they connect to. The configuration supports metro-area clustering, with a maximum round-trip latency of 11 milliseconds between arrays. Additionally, the Pure1 Cloud Mediator or an on-premises mediator is utilized to manage failover and prevent split-brain scenarios, eliminating the need for a third site or external gateway.

While ActiveCluster supports a two-site configuration, it does not support additional arrays within the same synchronous setup. For scenarios requiring protection across more than two sites, asynchronous replication solutions like ActiveDR™ can be employed. ActiveDR allows for asynchronous replication to a third site, providing broader disaster recovery capabilities.

Therefore, the maximum number of arrays supported in a single ActiveCluster configuration is two.

FlashArray//XL arrays require four power cables with C19 (receptacle) to C20 (plug) connectors to connect properly to rack PDUs, supporting redundant power supplies and higher power demands.

Reducing SafeMode retention and eradication settings requires approval from two designated SafeMode approvers via Pure1’s step-up authentication to ensure secure and authorized policy changes.

The FlashArray//XL supports up to four DirectFlash Shelves (DFS), each providing up to 1.9PB of effective capacity, enabling a total effective capacity of up to 7.6PB when fully expanded.

FlashArray//E models utilize 25Gb Ethernet (25G) ports for connecting to DirectFlash Shelves (DFS). These 25G ports are designed to handle the high throughput demands of DFS, providing efficient data transfer between the storage array and expansion shelves. This configuration ensures optimal performance and scalability for FlashArray//E systems.

The pureboot list command shows the versions of Purity installed and indicates which version will be loaded on the next system boot.

Opening a support case before starting the installation ensures timely assistance and coordination with support throughout the deployment process.

A swing shelf is installed during the SAS to NVMe Evergreen XFORM upgrade only if the array lacks enough free capacity to evacuate data packs, enabling safe data migration during transformation.

For ActiveCluster with Ethernet replication, a total of 8 IP addresses are typically required; if 3 are already provided, 5 additional IPs are needed to complete the configuration.

On FlashArray//XL, the PCIe slot 8 supports installation of 4-port Fibre Channel cards, allowing higher port density for SAN connectivity.

Cage nuts should be placed in the lowest square hole of the lowest rack unit (RU) where the array rails will be installed to ensure proper alignment and support.

Installing four DirectFlash Modules in a 9.1 TB Conversion Kit is intended to widen an existing write group, improving performance and capacity distribution within the FlashArray.