To specify the preferred I/O path by using Edit Asymmetric Access States in a cross‑path configuration, you must enable ALUA mode on the volume. You can configure ALUA mode before creating a GAD pair or on a volume that already belongs to an existing GAD pair.
Enabling ALUA mode on the primary volume before GAD pair creation automatically enables ALUA mode on the secondary volume when the pair is created.
Note:
- It is not necessary to set the ALUA mode if a cross-path configuration is not used.
- If the target volume belongs to an existing GAD pair, suspend the GAD pair before changing the ALUA mode.
Verify that the following conditions are met:
- The volume is not classified as a system volume or namespace volume.
- If the host server already recognizes the volume, shut down the host.
- If the volume belongs to an existing GAD pair, suspend the pair before changing the ALUA mode. Before suspending a pair, confirm that the quorum disk is healthy to prevent the GAD environment from entering a blocked state if a failure occur.
- If the target volume belongs to an existing GAD pair, resynchronize the GAD pair after changing the ALUA mode, and then restart the host server to apply the new ALUA settings.
- If the ALUA mode is set before creating a GAD pair, resynchronization is not required.