FlashArray path validation should be part of the daily storage health routine, especially in environments where OpenShift Virtualization and Portworx depend on backend SAN connectivity for VM disks and persistent volumes. This check confirms that worker nodes still have healthy access to FlashArray-presented storage and that path redundancy has not silently degraded.
This review applies to FC, iSCSI, and NVMe/TCP environments. While the transport differs, the operational goal is the same: detect backend connectivity issues early, before they cause VM failures, PVC mount issues, migration failures, or degraded storage performance.
This check validates that:
Worker nodes retain expected backend connectivity
FC, iSCSI, or NVMe/TCP paths are intact
Path redundancy is healthy for the transport in use
FlashArray-backed storage remains visible to the OpenShift worker nodes
No backend connectivity issue is likely to impact Portworx, VMs, or PVCs
- In the OpenShift web console, go to Compute > Nodes.
- Identify the worker nodes participating in storage operations.
- Confirm that storage-serving worker nodes are still in the Ready state.
- Open any suspicious node and review: conditions, recent events, resource pressure, whether the node is part of the storage-serving set.
- Review Portworx health from the OpenShift console. If Portworx nodes, pools, or volumes show abnormal behavior, treat that as a signal to validate backend path health.
- If VM storage operations, PVC attachment, or provisioning behavior looks abnormal, treat that as a signal to validate backend path health.
FC Path Validation Focus
In FC-backed environments, the daily goal is to confirm that worker HBAs still have healthy connectivity through the expected fabrics and that no FC path has silently dropped.
A healthy FC environment should show:
storage-capable worker nodes ready in OpenShift
no unexplained Portworx node or pool degradation
no VM disk attach or mount issues
no evidence that backend path redundancy has been reduced
If a node shows storage-side symptoms, coordinate with the SAN and FlashArray teams to confirm:
zoning has not changed unexpectedly
target ports remain active
host WWPN visibility is unchanged
no fabric event has reduced available paths
iSCSI Path Validation Focus
In iSCSI-backed environments, the daily goal is to confirm that sessions, interfaces, and expected data paths remain intact between the worker nodes and the FlashArray backend.
A healthy iSCSI environment should show:
worker nodes ready and stable
no login or session-related symptoms
no unexplained Portworx degradation
no PVC provisioning or VM disk attachment delays tied to backend access
If a node shows storage-side symptoms, coordinate with the network and storage teams to confirm:
target reachability remains intact
no VLAN, routing, or MTU change has affected connectivity
iSCSI session continuity is intact
NVMe/TCP Path Validation Focus
In NVMe/TCP-backed environments, the daily goal is to confirm that worker nodes retain healthy subsystem connectivity to the FlashArray backend and that namespace access remains stable.
A healthy NVMe/TCP environment should show:
worker nodes ready and stable
no unexplained Portworx node or pool degradation
no volume attach, mount, or path-related anomalies
no evidence that NVMe/TCP connectivity loss is affecting workloads
If a node shows storage-side symptoms, coordinate with the network and storage teams to confirm:
NVMe/TCP target reachability remains intact
no routing, MTU, VLAN, or interface change has affected connectivity
expected subsystem and namespace visibility is unchanged
host-to-array NVMe/TCP sessions remain stable
Validating Backend Connectivity from the OpenShift Side
From the OpenShift operations perspective, backend connectivity is considered healthy when:
Storage-capable worker nodes remain ready
Portworx nodes and pools remain healthy
No workload-facing storage symptoms are visible
No node-specific storage anomaly appears in the console
Path redundancy or native transport health is believed intact based on host and storage validation
In other words, the OpenShift team should not rely only on node readiness. A node can remain Ready while path redundancy is already degraded.
For that reason, FlashArray path validation should be treated as a correlation check across:
Node readiness
Portworx health
Workload storage behavior
Recent infrastructure changes
Transport-level backend validation when symptoms appear