Host modes and HMOs for VSP G1x00 and VSP F1500

Virtual Storage Platform Family Host Attachment Guide
Version
A3-02-2x
Audience
anonymous
Part Number
MK-90RD7037-32

Host modes for VSP G1000, VSP G1500, and VSP F1500

Host mode When to select this host mode
00 [Standard] When registering Red Hat Linux server hosts or IRIX server hosts in the host group.

HMOs specific to this host mode: 68, 88, 91

HMOs available to this host mode: 2, 7, 13, 22, 39, 51, 68, 71, 78, 80, 88, 91, 96, 113
01 [(Deprecated) VMware] Do not select this host mode. Select host mode 21 VMware Extension instead.

HMOs specific to this host mode: 54, 63, 68, 88, 114
03 [HP] When registering HP-UX server hosts in the host group.
08 [HP] When registering HP-UX server hosts in the host group.
09 [Solaris] When registering Solaris server hosts in the host group.
0C [(Deprecated) Windows] Do not select this host mode. Select host mode 2C Windows Extension instead.

HMOs specific to this host mode: 6, 25, 40, 73, 88, 105

HMOs available to this host mode: 2, 6, 7, 13, 22, 25, 39, 40, 51, 71, 73, 78, 80, 88, 96, 105, 113
0F [AIX] When registering AIX ® server hosts in the host group.

When host mode 0F AIX ® is set, NACA ( Normal Auto Contingent Allegiance) is enabled automatically. To ensure that the host responds correctly to a port with host mode 0F AIX enabled:

  1. Shut down the host to be connected to the port.
  2. Set the host mode on the port to 0F AIX, and enable the desired HMOs.
  3. Connect the cables from the host to the port.
  4. Boot the host.

Caution: If the host mode of a port is changed to 0F AIX and the host had already recognized the Inquiry response for an LDEV on the port before host mode 0F AIX was set, the host might experience loss of device access (LDEV or LU). The host must be rebooted after the host mode is changed to 0F AIX to recognize the change in the response to the standard inquiry.

21 [VMware Extension] When registering VMware server hosts in the host group.*

HMOs specific to this host mode: 54, 63, 68, 82, 83, 88, 114

HMOs available to this host mode: 2, 7, 13, 22, 39, 51, 54, 63, 68, 71, 78, 80, 82, 83, 88, 96, 113, 114
2C [Windows Extension] When registering Windows server hosts in the host group.*

HMOs specific to this host mode: 6, 25, 40, 73, 88, 105

HMOs available to this host mode: 2, 6, 7, 13, 22, 25, 39, 40, 51, 71, 73, 78, 80, 88, 96, 105, 113
*Use host mode 21 only for VMware server hosts (Hypervisor host accessing VMFS formatted data stores, not Raw Device Mapping (RDM) disks. But when the (Linux-based OS or Windows) Virtual Machine host directly recognizes and manages the I/O stack on LUs by RDM (Raw Device Mapping), then the disk should only be assigned a host mode that is the same as the operating system of the virtual machine, even when running on VMware Hypervisor.

Unreliable access, errors, and performance problems will result if vCenter maps an RDM disk to a virtual machine that is part of a VMware host group with VMware host mode configured. This is because Windows and Linux use SCSI-3 version protocol and VMware uses SCSI-4 version protocol.

Linux-based OS (such as Red Hat Linux) or Windows Virtual Machine (VM) server hosts that use virtual disks and not RDM do not need any host group mapping because they are dependent on the VMware Hypervisor host for creating a virtual disk (VMDK file) from the VMFS file system residing on a Hypervisor-only data stores, because the VM disk files are ultimately VMware VMFS file system files and not actual disks.

To add VMware Hypervisor (not virtual machine) hosts to one host group, you must set this host mode and these HMOs for the host group:

  • Host mode: 21 VMware Extension
  • Host mode options: 2, 22, 25, 54, 63, 68, and 110 (for details, contact customer support)

Restrictions for VMware server hosts added to the host group:

Do not attempt to set Windows or Linux HMO functions on a VMware Hypervisor, they cannot be used by VMware:

  • Thin Provisioning
  • Offloaded Data Transfer (ODX)

The above functions are handled by the HMO 54 and 63 in the VMware host group instead.

Host mode options for VSP G1000, VSP G1500, and VSP F1500

HMO Function Host mode Description
2 VERITAS Database Edition/Advanced Cluster Any Use this HMO when any of the following conditions is met:
  • Windows Server Failover Clustering (WSFC) is used.
  • Microsoft Failover Cluster (MSFC) is used.
  • Linux with cluster configuration is used.
  • Symantec Cluster Server (previously known as Veritas Cluster Server (VCS)) is used.
  • The response for SPC-3 (Good Status) is required.
6 TPRLO 0C [(Deprecated) Windows] or 2C [Windows Extension] Purpose: By default, PRLO is returned for TPRLO, however, LOGO might be expected under the following conditions.

When this HMO is enabled, the storage system will switch the TPRLO response to LOGO from PRLO.

Use this HMO when all these conditions are satisfied:

  • An Emulex host bus adapter is used in a Windows environment.
  • The mini-port driver is used.
  • TPRLO=2 is specified for the mini-port driver parameter of the host bus adapter.
7 Automatic recognition function of LUN Any Use this HMO when you want the Unit Attention (UA) response to be returned at SCSI path change (sense code: REPORTED LUNS DATA HAS CHANGED).

Notes:

  1. If the UA response occurs frequently and the host load becomes high, the data transfer cannot be started on the host side and timeout might occur.
  2. When both HMO 07 and HMO 69 are enabled, the UA of HMO 69 is returned to the host.
12 No display for ghost LUN 03 [HP] Use this HMO when you want to suppress creation of device files for devices to which paths are not defined.
13 SIM report at link failure Any Use this HMO when you want SIMs (service information messages) to be issued if the number of link failures detected between the ports exceeds the threshold.

Note: Enable HMO 13 only when requested to do so. HMO 13 is enabled for each port. Set HMO 13 for the host group 00 of the target port.
15 HACMP 0F [AIX] Use this HMO when HACMP* or PowerHA® is used.

* HACMP 4.5 version 4.5.0.13 or later, HACMP 5.1 version 5.1.0.4 or later, or HACMP 5.2 or later.

22 Improves MODE SENSE command response for a reserved volume Any

Use this HMO when any of these conditions is satisfied:

  • Veritas Cluster Server is used.
  • An OS or middleware that supports SPC-4 is used.
  • A single-site or GAD dual-site Clustered VMDK configuration is used.

Notes:

  1. By applying HMO 22, the volume status (reserved / non-reserved) will be checked more frequently.
  2. By applying HMO 22, the host OS will not be receiving warning messages when the MODE SENSE command is being issued to a reserved volume.
25 Support SPC-3 behavior on Persistent Reservation Any Use this HMO when one of these conditions is satisfied:
  • Windows Server Failover Clustering (WSFC) is used.
  • Microsoft Failover Cluster (MSFC) is used.
  • Symantec Cluster Server (previously known as Veritas Cluster Server (VCS)) is used.
  • There is no registered key to be deleted when running the PERSISTENT RESERVE OUT command.
39 Change the nexus specified in the SCSI Target Reset Any Use this HMO when you want to enable the host to set these ranges on all initiators in the host group, not only the initiator that issues the job resetting when receiving Target Reset, such as in the IBM SVC connection environment:
  • Range of job resetting.
  • Range of UAs (Unit Attentions) defined.
40 V-VOL expansion 0C [(Deprecated) Windows] or 2C [Windows Extension] Use this HMO when you want to automate recognition of the V-VOL capacity after increasing the V-VOL capacity.

When a VMware, Linux, or Windows server is added to a host group, select VMware Extension for the host mode and then set the option to ON.
43 Queue Full Response 03 [HP] Use this HMO when the command queue is full in your storage system connected to an HP-UX host, and you want to respond Queue Full (instead of Busy) from the storage system to the host.
51 Round Trip Set Up Option Any Use this HMO if you want to adjust the response time of the host I/O, for example when the distance between the primary and secondary storage systems in the TrueCopy or global-active device pair is long (approximately 100 km) and point-to-point topology is used.

For further information, see the section below this table.
54 (VAAI) Support Option for the EXTENDED COPY command 01 [(Deprecated) VMware] or 21 [VMware Extension] Use this HMO when the VAAI (vStorage API for Array Integration) function of VMware ESX/ESXi 4.1 or later is used.

Note: After setting this HMO, perform the operation, such as the server reboot that reissues the INQUIRY command on the host side.

60 LUN0 Change Guard 03 [HP] Use this HMO when HP-UX 11.31 is used, and you want to suppress the addition or deletion of LUN 0.
63 (VAAI) Support Option for the EXTENDED COPY command 01 [(Deprecated) VMware] or 21 [VMware Extension] Use this HMO when you connect the storage system to VMware ESXi 5.0 or later and use the VAAI function for iSCSI T10. Use a combination of this HMO and HMO 54.

Note: After setting this HMO, perform the operation, such as the server reboot that reissues the INQUIRY command on the host side.

68 Support Page Reclamation for Linux 00 [Standard], 01 [(Deprecated) VMware], or 21 [VMware Extension] Use this HMO when using the Page Reclamation function with a Linux host.

Note: After setting this HMO, perform the operation, such as the server reboot that reissues the INQUIRY command on the host side.

71 Change the Unit Attention for Blocked Pool-VOLs Any Use this HMO when you want to change the unit attention (UA) from NOT READY to MEDIUM ERROR while a DP pool is blocked.
72 AIX GPFS Support   Use this HMO if either of the following conditions is met:
  • General Parallel File System (GPFS) is used in the storage system connecting to the AIX® host.
  • A single-site or GAD dual-site Clustered VMDK configuration is used.
73 Support Option for WS2012 0C [(Deprecated) Windows] or 2C [Windows Extension] Use this HMO if all the following functions provided by Windows Server 2012 (WS2012) or later are used with a Windows host running WS2012 or later:
  • Thin Provisioning function
  • Offloaded Data Transfer (ODX) function

Use a combination of this HMO and HMO 114 when a VXIO driver with Veritas InfoScale 8.0 or later is used on the Windows OS host.

Note: After setting HMO 73 to ON, perform an operation (such as a server reboot) that reissues the INQUIRY command on the host side.

78 The non-preferred path option Any Use this HMO when all these conditions are satisfied:
  • Global-active device is used in the configuration with the data centers (Metro configuration).
  • Hitachi Dynamic Link Manager (HDLM) is used as the alternative path software.
  • The host group is on the non-optimized path of HDLM.
  • The performance deterioration of I/O responses can be avoided without I/O using the non-optimized path of HDLM.

Caution:

If this HMO is set on the wrong host group, load balance of HDLM with the option cannot be performed intended operations, which might cause a performance issue.
80 Multi Text OFF Mode Any By using the iSCSI interface, if the storage system connects with the host of which OS is not supported of the Multi Text function. For instance, connecting the storage system and the host of RHEL5.0 which does not support the Multi Text-function.
82 Discovery CHAP Mode 21 [VMware Extension] Select this option when the CHAP authentication is performed at the time of the discovery login in the iSCSI connection environment.

For instance: When the CHAP authentication is performed at the time of the discovery login in the iSCSI environment of the VMware host and storage system

83 Report iSCSI Full Portal List Mode 21 [VMware Extension] Use this HMO when all these conditions are met:
  • Configuring redundant paths between the VMware host and storage system.
  • Waiting for replying of the target information from the ports other than ports of discovery login.

Notes:

  • When this HMO is enabled, the same iSCSI target name and the same target number as the iSCSI target that receives the Send Target request are reported as the targets. For the target information that requires a portal list report, make sure that the iSCSI target name and the target number match with those of the iSCSI target under the port that receives the Send Target request.
  • Set this HMO on all targets that require reporting.
88 Port consolidation 00 [Linux], 01 [(Deprecated) VMware], 03 [HP], 09 [Solaris], 0C [(Deprecated) Windows], 0F [AIX], 21 [VMware extension], 2C [Windows extension] Use this HMO when converging multiple host-target ports used in the migration source storage system on one host group of the migration target storage system by enabling path definition from the host group to LDEVs of multiple virtual storage machines.
  • Enabled: LUN path definition is enabled.
  • Disabled: LUN path definition is disabled.

This HMO setting is not supported when the HDLM or VxVM DMP multipath software is used.

Notes:

  1. Apply this HMO when all the following conditions are met:
    • You are using the GAD function to migrate volumes in multiple migration source storage systems that use the same server.
    • You need to converge target ports used on the migration target storage system.
    • Host mode 00, 01 03, 09, 0C, 0F, 21, or 2C is used.
  2. Do not apply this HMO to host groups without the specified host modes enabled. Applying this HMO to host groups with other host modes can cause the following problems:
    • Path addition from the server to the migration target storage system might fail.
    • Display of devices that the server recognizes might be invalid.
  3. When using VMware NMP, use the same LUN# for the migration source and migration target.
  4. If a LUN path is defined from the host group to an LDEV defined in a virtual storage machine different from the one to which the host group belongs, this HMO cannot be set to OFF.
91 Disable I/O wait for OpenStack Option 00 [Standard] Use this HMO when manually creating host groups or iSCSI targets that are used as the I/O data paths for OpenStack.
96 Change the nexus specified in the SCSI Logical Unit Reset Any Use this HMO when you want to enable the host to set these ranges on all initiators in the host group, not only the initiator that issues the job resetting when receiving an LU Reset, such as in the IBM SVC connection environment:
  • Range of job resetting.
  • Range of UAs (Unit Attentions) defined.
97 Proprietary ANCHOR command support 00 [Standard] Do not enable HMO 97 when connecting with Hitachi NAS Platform (HNAS). This setting does not enable any HNAS functionality at this time.

Note: This HMO was intended to be used only for NAS but was never implemented in NAS software, and therefore it is currently not supported by NAS and should not be used.

105 Task Set Full response in the event of I/O overload 0C [(Deprecated) Windows] or 2C [Windows Extension] Use this HMO when you want to return Task Set Full response from the storage system to the host when an overload of I/Os occurs on the storage system.
113 iSCSI CHAP Authentication Log Any Use this HMO when the result of the CHAP authentication is output to the audit log (DKC).

Notes:

  1. When you use this HMO, set this HMO on the host group 0.
  2. The setting of this HMO applies to all iSCSI targets on the port. Therefore, set this HMO only in iSCSI target 00 of the port.
114 The automatic asynchronous reclamation on ESXi 6.5 or later 01 [(Deprecated) [VMware] ,21 [VMware Extension], 0C [(Deprecated) Windows], or 2C [Windows Extension] If either of the following conditions is met:
  • Use a combination of this HMO and HMO 63 when connecting to VMware ESXi 6.5 or later, and when using the zero data page reclamation function, which is performed automatically if files on the VMFS (Virtual Machine File System) are deleted.
  • Use a combination of this HMO and HMO 73 when a VXIO driver with Veritas InfoScale 8.0 or later is used on the Windows OS host.

Note: After setting this HMO, perform the operation, such as the server reboot, that reissues the INQUIRY command on the host side.

HMO 51 details

  • When the HMO 51 setting is changed to ON or OFF, a link-down and link-up occur on the target port, and an SSB log of link down is output on MCU (M-DKC) and RCU (R-DKC).
  • This HMO can work only when the micro-program supporting this function is installed on both MCU (M-DKC) and RCU (R-DKC).
  • The HMO setting is only applied to Initiator-Port and RCU Target-Port. This function is only applicable when the 16FC8 PCB/8FC16 PCB/16FE10 PCB is used on RCU/MCU.
  • When removing 16FC8 PCB/8FC16 PCB/16FE10 PCB , the operation must be executed after setting HMO 51 to OFF.
  • If this option is used, Point to Point setting is necessary.
  • If HMO 51 is set to ON while SOM 769 is ON, path creation might fail after automatic port switching.
  • Make sure to set HMO 51 from OFF to ON or from ON to OFF after the pair is suspended or when the load is low.
  • The RCU Target, which is connected with the MCU where this option is set to ON, cannot be used for Universal Replicator.
  • When HMO 51 is set to ON using RAID600 as MCU and RAID800 as RCU, the micro-program of RAID600 must be 60-07-63-00/00 or later (within 60-07-6x range) or 60-08-06-00/00 or later. Also, make sure that the setting of this HMO is the same on both MCU and RCU. (Different settings on MCU and RCU lead to path blockage.)
  • Path attribute change (Initiator Port - RCU-Target Port, RCU-Target Port - Initiator Port) accompanied with Hyperswap is enabled after setting HMO 51 to ON. If HMO 51 is already set to ON on the both paths, HMO 51 continues to be applied on the paths even after execution of Hyperswap.
  • This function is available in the following configuration.

    Supported configuration: Point to Point setting with HMO 49 and HMO 50 set to ON (In the case of 8FC16/16FE10, setting HM O49 and HMO 50 is not necessary as they do not support the options) while the path distance between MCU and RCU meets requirements of each program product.

  • This function is prepared for long distance data transfer. Therefore, if HMO 51 is set to ON with distance of less than 1 km, a data transfer error might occur on RCU side and the performance improvement cannot reach the expected level.
  • When MPB installation/removal is performed on a storage system that has the Initiator port with HMO 51 set to ON, as resource distribution to the MPB takes place, re-login works on the Initiator port. The re-login might affect hosts depending on customer environments. To avoid it, delete the TC path connected to the Initiator port, install/remove the MPB, and then create the TC path again.
  • Support versions for PCBs are as follows:
    • 16FC8 PCB: All versions
    • 8FC16 PCB: 80-02-22-00/00 and later (*1)
    • 16FE10 PCB: 80-02-22-00/00 and later
    • 16FC16 PCB: 80-03-0x-00/00 and later (*1)
    If the support version of the program product being used is one of the following versions or later, the support version of the program product is prioritized over the versions of *1. For support versions, refer to the user guide of each program product.
    • VSP G1x00 and VSP F1500
    • VSP G1x00 and VSP F1500
  • The option cannot be applied to a port connected with multiple MCUs.