The following table lists the host modes you can set on your storage system. Carefully review and determine which host modes you will set when configuring your storage system, and observe all cautions and restrictions for the host modes. The host mode and host mode options (HMOs) must be set on a port before the host is connected to that port. If you change the host mode or HMOs after the host is connected, you must reboot the host (server) for the new settings to be recognized.
The following table lists the host modes and host mode options (HMOs) you can set on your storage system host-facing ports. Carefully review and determine which host modes you will set when configuring your storage system, and observe all cautions and restrictions for the host modes. The host mode and host mode options must be set on the host-facing port before the host is connected to that port. If you change the host mode or HMOs after the host is connected, you must reboot the host (server) for the new settings to be recognized.
| 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, 122, 131 HMOs available to this host mode: 2, 7, 13, 22, 25, 39, 68, 71, 78, 80, 88, 91, 96, 97, 113, 122, 131 HMO best practice: 2, 22, 25, 68 |
| 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, 110, 114, 122 HMOs available to this host mode: 2, 7, 13, 22, 25, 39, 54, 63, 68, 71, 78, 80, 88, 96, 97, 110, 113, 114, 122 HMO best practice: See host mode 21 [VMware Extension] in this table. |
| 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. HMOs specific to this host mode: 12, 33, 43, 60, 88 HMOs available to this host mode: 2, 7, 12, 13, 22, 25, 33, 39, 43, 60, 71, 78, 80, 88, 96, 97, 113 HMO best practice: 2, 12, 22, 25, 60 |
| 03 [HP] | When registering HP-UX server hosts in the host group. |
| 05 [OpenVMS] | When registering OpenVMS server hosts in the host group. HMOs specific to this host mode: 33 HMOs available to this host mode: 2, 7, 13, 22, 25, 33, 39, 71, 78, 80, 96, 97, 113 HMO best practice: 2, 22, 25 |
| 07 [Tru64] | When registering Tru64 server hosts in the host group. HMOs available to this host mode: 2, 7, 13, 14, 22, 25, 39, 71, 78, 80, 96, 97, 113 HMO best practice: 2, 22, 25 |
| 08 [HP] | When registering HP-UX server hosts in the host group. HMOs specific to this host mode: 12, 43, 60, 88 HMOs available to this host mode: 2, 7, 12, 13, 22, 25, 39, 43, 60, 71, 78, 80, 88, 96, 113 HMO best practice recommendations: 2, 12, 22, 25, 60 |
| 08 [HP] | When registering HP-UX server hosts in the host group. |
| 09 [Solaris] | When registering Solaris server hosts in the host group. HMO specific to this host mode: 88 HMOs available to this host mode: 2, 7, 13, 22, 25, 39, 71, 78, 80, 88, 96, 97, 98, 113 HMO best practice: 2, 22, 25 |
| 09 [Solaris] | When registering Solaris server hosts in the host group. |
| 0A [NetWare] | When registering NetWare server hosts in the host group. HMOs available to this host mode: 2, 7, 13, 22, 25, 39, 71, 78, 80, 96, 97, 113 HMO best practice: 2, 22, 25 |
| 0C [(Deprecated) Windows] | Do not select this host mode. Select host mode 2C Windows Extension instead. HMOs specific to this host mode: 6, 40, 73, 88, 105, 110, 114, 122 HMOs available to this host mode: 2, 6, 7, 13, 22, 25, 39, 40, 71, 73, 78, 80, 88, 96, 97, 105, 110, 113, 114, 122 HMO best practice: See host mode 2C [Windows Extension] in this table. |
| 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. HMOs specific to this host mode: 15, 88 HMOs available to this host mode: 2, 7, 13, 15, 22, 25, 39, 71, 78, 80, 88, 96, 97, 113, 124 HMO best practice: 2, 15, 22, 25 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:
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. |
| 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:
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, 110, 114, 122 HMOs available to this host mode: 2, 7, 13, 22, 25, 39, 54, 63, 68, 71, 78, 80, 82, 83, 88, 96, 97, 110, 113, 114, 122 HMO best practice: 2, 22, 25, 54, 63, 68, 110 |
| 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, 40, 73, 88, 105, 110, 114, 122 HMOs available to this host mode: 2, 6, 7, 13, 22, 25, 39, 40, 71, 73, 78, 80, 88, 96, 97, 105, 110, 113, 114, 122 HMO best practice: 2, 22, 25, 40, 110 |
| 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:
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:
The above functions are handled by the HMO 54 and 63 in the VMware host group instead. |
|