ActiveCluster Connectivity Models: In an ActiveCluster environment, hosts can connect to the arrays using either a Uniform or Non-Uniform access model. In a Uniform model, the host has active paths to both FlashArrays in the cluster.
The Failover Scenario: When the replication network between the two arrays fails (a "split-brain" scenario), the Mediator decides which array keeps the pod online (the winner) and which array takes it offline (the loser) to ensure data consistency.
Analyzing the Symptoms:
The pod failed over, meaning one array is now the exclusive servicer for that pod.
Most volumes in that pod stayed online for the host. This proves that the host is correctly registered in Purity (ruling out Option C) and that the general ActiveCluster/Pod logic is functioning.
Only one specific volume lost connectivity.
The Root Cause (Zoning/Access): If a single volume loses connectivity while others do not, it indicates a pathing issue specific to that volume's visibility. In an ActiveCluster failover, if the "winning" array does not have a physical path to the host for that specific volume (due to missing FC Zoning or Ethernet VLAN tagging on the switches), the host will lose access once the "losing" array drops its paths.
Why Option A is unlikely: If "Uniform access" (the ability to see both arrays) was the issue, it would typically affect all volumes in the pod equally during a failover, not just a single outlier. The fact that the rest of the volumes remained available suggests the host is configured for uniform access, but the specific network plumbing (zoning) for that one volume's path to the surviving array is missing.
!