Home > Storage > PowerMax and VMAX > Storage Admin > Dell PowerMax: Data Mobility Best Practices and Operational Guide > Appendix F: NDM with ESXi virtualized cluster environment
This section describes a known procedure/timing in the VMware ESXi virtualized cluster environment:
NDM: Create > Discover V3/PowerMax Paths > Cancel > Create
This is the issue where we see the host/multipath assume that re-discovered V3 paths are still registered from before the cancel.
In the Microsoft virtualized cluster environment, this results in the symptom NTFS event 57 and unexpected cluster resource failover.
To Mitigate this issue Recommendation is to cleanup stale/dead host paths after a Cancel issued.
NDM: Create > Discover V3 Paths > Create > Cutover > Cancel –revert (immediate)
This is the issue where we introduce two NDM changes before all participating hosts have had change to recognize the first change (cutover).
We observe cases where a write can be rejected by both V2 and V3 and devices get marked PDL (permanent device loss) by VMware.
To mitigate this issue, Dell Technologies recommends that all participating hosts have realized the cutover change before running a cancel -revert.