Which Purity command can be used to validate I/O is balanced across initiators?

To validate that I/O traffic is correctly distributed across a host's initiators (Fibre Channel WWNs or iSCSI IQNs), the correct command ispurehost monitor --balance.

Ensuring "multipathing balance" is a critical post-installation check. If a host is configured correctly with Multipath I/O (MPIO) software (like DM-Multipath on Linux or MPIO on Windows), read/write requests should be distributed relatively evenly across all active paths to the storage array.

Command Function:The purehost monitor command provides real-time performance statistics for hosts. Adding the --balance flag switches the view to a granular breakdown of IOPS and Bandwidthper initiatorfor the specified host.

Interpretation:An Implementation Engineer looks for initiators showing 0 IOPS or significantly lower traffic than others, which would indicate a path failure, zoning issue, or incorrect MPIO policy (e.g., Failover Only instead of Round Robin). Options A and B are incorrect syntax; purehost list shows configuration (not real-time stats), and iobalance is not a valid Purity command argument.