I am running ONTap 8.1. I have a Windows Server 2003 machine running DSM 3.5. We are using FCP. ALUA is enabled on the igroup.
On a Windows Server 2008 host, I see the paths for all virtual disks listed with an Operational State of Active/Optimized or Active/Non-Optimized. The Optimized paths are preferred and the Non-Optimized paths are not preferred. This is what I expected to see.
However, I also have a Windows Server 2003 host that shows its paths as Active/Optimized and Active. All of the paths, both Active/Optimized and those listed as Active, are listed as preferred. This is not what I expected to see. This host, however, has some disk partitions that are mounted to folders versus being assign a drive letter. With partitions mounted to folders, is it expected to see Active and Active/Optimized paths as opposed to Active/Optimized and Active/Non-Optimized paths?
"Data ONTAP DSM 3.4 introduces support for ALUA which provides a standards-based mechanism to determine the path priorities for each LUN. The MMC snap-in will display the detected path priority as Active/Optimized or Active/Unoptimized. ALUA must first be enabled on the storage controller by setting the ALUA attribute of the initiator groups. The Data ONTAP command to enable ALUA on an igroup is as follows: 'igroup set <igroup name> alua yes'. For Data ONTAP DSM 3.4, when ALUA is not enabled, all the path priorities will be Active/Unoptimized. For Data ONTAP DSM 3.5, when ALUA is not enabled, all path priorities will be Active/Optimized. For either version, not using ALUA to determine correct path priorities for accessing LUNs via FCP will result in FCP Partner Path Misconfigured warnings on the storage controllers."