To allow Windows and Linux to access separate LUNs from the same SVM, what configuration is required to ensure proper alignment?

To allow Windows and Linux to access separate LUNs from the same SVM, what configuration is required to ensure proper alignment?

• A. Add both hosts to the same igroup and set the OS type to 'mixed.'
• B. Create separate igroups with the correct OS type defined for each host.
• C. Use a single igroup but set protocol to 'unrestricted.'
• D. Manually align block sizes on the client side.

Answer: (B)

LUN alignment in ONTAP is guided by the OS type configured on an initiator group. When Windows and Linux hosts share the same SVM, each OS has its own alignment and I/O expectations, so the correct approach is to create separate initiator groups for each operating system, and set the appropriate OS type for each group. This ensures that the LUNs are presented with the proper alignment and access characteristics for each host, avoiding misalignment and performance issues. By keeping separate igroups, you can map the Windows-host LUNs to its igroup and the Linux-host LUNs to its own, while both igroups can reside under the same SVM. Mixing OS types in a single igroup or relying on a non-specific setting doesn’t provide the OS-specific alignment NetApp optimizes for, and client-side alignment alone isn’t a reliable or scalable solution.

LUN alignment in ONTAP is guided by the OS type configured on an initiator group. When Windows and Linux hosts share the same SVM, each OS has its own alignment and I/O expectations, so the correct approach is to create separate initiator groups for each operating system, and set the appropriate OS type for each group. This ensures that the LUNs are presented with the proper alignment and access characteristics for each host, avoiding misalignment and performance issues.

By keeping separate igroups, you can map the Windows-host LUNs to its igroup and the Linux-host LUNs to its own, while both igroups can reside under the same SVM. Mixing OS types in a single igroup or relying on a non-specific setting doesn’t provide the OS-specific alignment NetApp optimizes for, and client-side alignment alone isn’t a reliable or scalable solution.