Initiator

Uses third-party multipath software

This parameter is displayed only after an initiator has been added to the host.

If LUNs have been mapped to the host before you enable or disable this parameter, restart the host after you configure this parameter.

You do not need to enable this parameter for a host with UltraPath.

Enabled

Switchover Mode

Path switchover mode

The system supports the following modes:

• early-version ALUA: default value of Switchover Mode for an upgrade from an earlier version to the current version. Detailed requirements are as follows:
  • The storage system must be upgraded from V300R003C10 and earlier to V300R003C20 or V300R006C00SPC100 and later; from V300R005 to V300R006C00SPC100 and later; from Dorado V300R001C00 to Dorado V300R001C01SPC100 and later.
  • Before the upgrade, the storage system has enabled ALUA.
• common ALUA: Detailed requirements are as follows:
  • The storage system version must be V500R007C00 and later, V300R003C20 and later, V300R006C00SPC100 and later, or Dorado V300R001C01SPC100 and later.
  • The OS of the host that connects to the storage system must be SUSE, Red Hat 6.X, Windows Server 2012 (using Emulex HBAs), Windows Server 2008 (using Emulex HBAs), or HP-UX 11i V3.
• ALUA not used: does not support ALUA or HyperMetro. This mode is used when a host such as HP-UX 11i V2 does not support ALUA or ALUA is not needed.
• Special mode: This is used when the OS of the host supports ALUA, but is not included in common ALUA mode. Detailed requirements are as follows:
  • The storage system version must be V500R007C00 and later, V300R003C20 and later, V300R006C00SPC100 and later, or Dorado V300R001C01SPC100 and later.
  • The OS of the host that connects to the storage system must be VMware, AIX, Red Hat 7.X, Windows Server 2012 (using QLogic HBAs), or Windows Server 2008 (using QLogic HBAs).

common ALUA

Special mode type

Determines which Special mode is used for path switchover. All special modes support ALUA. Detailed requirements are as follows:

• Mode 0:
  • The host and storage system must be connected using a Fibre Channel network.
  • The OS of the host that connects to the storage system must be Red Hat 7.X, Windows Server 2012 (using QLogic HBAs), or Windows Server 2008 (using QLogic HBAs).
• Mode 1:
  • The OS of the host that connects to the storage system must be AIX or VMware.
  • If HyperMetro is deployed, HyperMetro must work in load balancing mode.
• Mode 2:
  • The OS of the host that connects to the storage system must be AIX or VMware.
  • If HyperMetro is deployed, HyperMetro must work in local preferred mode.

Mode 0

Path Type

In HyperMetro scenarios, the value can be either Optimal Path or Non-Optimal Path.

• When HyperMetro works in load balancing mode, set the Path Type for the initiators of both the local and remote storage arrays to Optimal Path. Enable ALUA on both the host and storage arrays. If the host uses the round-robin multipathing policy, it delivers I/Os to both storage arrays in round-robin mode.
• When HyperMetro works in local preferred mode, set the Path Type for the initiator of the local storage array to Optimal Path, and that of the remote storage array to Non-Optimal Path. Enable ALUA on both the host and storage arrays. The host preferentially delivers I/Os to the local storage array.

In non-HyperMetro scenarios, the value is Optimal Path.

Optimal Path