You can configure Fibre Channel, Fibre Channel over Ethernet (FCoE), SAS, or iSCSI-attached hosts to a clustered system.
SAN fabric function is available only if a Fibre Channel option is installed. Otherwise, this information does not apply.
If you are configuring a host object on a Fibre Channel fabric-attached host or a Fibre Channel over Ethernet (FCoE) attached host, ensure that you complete all zone and switch configuration. If you are configuring a directly attached Fibre Channel host, there must be connections to both nodes in each I/O group that has volumes that are mapped to that host. Also, test the configuration to ensure that zoning was created correctly.
If you are configuring a host object on the system that uses iSCSI connections, ensure that you complete the necessary host-system configurations and configure the system for iSCSI connections.
If you are configuring a host, such as hosts that are running the VMware operating system, define each host in the system as a separate host object. Do not combine multiple worldwide port names (WWPNs) from multiple hosts as one host object.
To create host objects by using the CLI, see the information about configuring host objects by using the CLI. To delete an existing host object, use the rmhost command.
To configure a host cluster, issue the mkhostcluster command. You can specify one or more hosts from which to create the initial shared volume mappings of the host cluster. You can also create an "empty" host cluster that does not contain any volume mappings and add hosts to it later. The traditional methods of managing mappings between a volume and a host by using the mkvdiskhostmap and rmvdiskhostmap commands do not work on shared mappings.
When you specify one or more hosts on the mkhostcluster command, the process is called seeding. A new host cluster is created and the hosts that you specified are added to the host cluster. By default, all of the private volume mappings for the hosts become the shared mappings of the host cluster. However, you can also exclude specific volumes from being shared. The private volume mappings are not shared with any other host in the host cluster.
To add a host to a host cluster, enter the addhostclustermember command. When added, the new host shares the volume mappings of the hosts that are specified on the mkhostcluster command. If no SCSI LUN conflicts are detected, the volume mappings on the new host are also shared with other hosts in the host cluster. However, the mkhostcluster command failed SCSI LUN conflicts are detected between the shared mappings in the host cluster and the private mappings of the host.
To display all of the hosts that are members of a specific host cluster, enter the lshostclustermember command. A host can be a member of only one host cluster
When you remove a host from a host cluster, you can keep or remove any volume mappings that were obtained when it was part of the host cluster. If you keep the volume mappings, the volumes become private mappings of the host. If you remove the volume mappings, the host does not maintain any of the shared volume mappings from the host cluster. For more information, see the rmhostclustermember command.