- All versions of Clustered ONTAP prior to 9.5P4
Data OnTap provides three ALUA states for filer paths:
- Active/optimized (to the node that owns the lun)
- Active/non-optimized (to any node that does not own the lun)
The transitioning state should only be seen briefly during a takeover or giveback as the path transitions from one active state to another.
In some situations the paths become stuck in "transitioning" and the host is unable to use them. Windows may report the path state as "transitioning" in DSM. ESX will report IO errors and
sense data returned as 0x2 0x4 0xa.