If the server can see the storage, potential issues are not occurring, such as:
-
Network connectivity issues between the server and storage
-
Proper FC zoning
-
Driver installation for FC HBAs
-
iSCSI initiator configuration is connected to the FlashArray because there is a Host Record with the Host Port IQN and a connected Pure Volume added to the Host
PowerShell
-
Test your setup quickly with the Everpure PowerShell Toolkit:
Install-module PureStoragePowerShellToolkit -requiredversion 3.0.1 Test-Pfa2WindowsBestPractices #the image below is the output
FlashArray GUI
In the FlashArray GUI check Connections under Health to see if MPIO is misconfigured. It could be missing a connection, unbalanced, only connected to 1 FlashArray controller, or in a redundant state.
In the below image the Host Connections are visible showing the connection protocol, the path status, and which ports on the controllers the host is connected to.
Host 2022core is not connected to the FlashArray and shows None under paths. It shows 0 for all three Host port protocols which means none is configured in the Host.
Host 2022prev is unbalanced, where the iSCSI initiator is connected to both iSCSI targets on CT0, but to only 1 of the 2 iSCSI targets in CT1.
Host Azstackhci23h2 is only connected to 1 of the 2 iSCSI targets on CT0, and an alert is fired because there are no connections to CT1 which is a single point of failure. If CT0 is unavailable, the FlashArray will failover to CT1 in moments and this host will have no connectivity to the FlashArray.
Host e08-01 is Redundant and the only Green status under Paths. It is using Fibre Channel, showing 2 WWNs, and it is utilizing all available Fibre Channel targets in this FlashArray.