FAIS FlashArray-Implementation-Specialist Pure Storage Study Notes

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.

=========

To properly configure a FlashArray forActiveCluster with Ethernet replication, a total of9 IP addressesare typically required per array. If the installation document currently lists only3 IP addresses, the Implementation Engineer needs6 additional IP addresses.

The breakdown of the requirement is as follows:

Management (5 IPs):Standard ActiveCluster best practices mandate fully redundant management connectivity. This includes 1 Virtual IP (VIP) and 4 Physical IPs (CT0.eth0, CT1.eth0, CT0.eth1, and CT1.eth1). The initial "3 IP addresses" provided usually correspond to the basic setup (VIP, CT0.eth0, CT1.eth0), leaving a deficit of 2 management IPs (for the eth1 redundancy).

Replication (4 IPs):ActiveCluster over Ethernet requires dedicated replication ports separate from management. The standard configuration utilizes two physical ports per controller for redundancy (e.g., CT0.eth2, CT0.eth3, CT1.eth2, CT1.eth3), requiring 4 unique IP addresses.

Therefore, 2 additional management IPs + 4 replication IPs =6 additional IPsrequired to meet the strict redundancy standards for an ActiveCluster deployment.