Ports By Host - IBM Storwize V5010 Manual

By default, hosts within a host cluster inherit all shared volume mappings from that host
cluster, as if those volumes were mapped to each host in the host cluster individually. Hosts in
a host cluster can also have their own private volume mappings that are not shared with other
hosts in the host cluster. With shared mapping, volumes are mapped on a host cluster basis.
The volumes are shared by all of the hosts in the host cluster, if there are no Small Computer
System Interface (SCSI) LUN conflicts among the hosts.
Volumes that contain data that is needed by other hosts are examples of a shared mapping. If
a SCSI LUN conflict occurs, a shared mapping is not created. SCSI LUN conflicts can occur if
multiple volumes are mapped with the same SCSI LUN ID or if same volume is mapped to
multiple SCSI LUN IDs. The system does not allow a volume to be mapped more than once to
the same host. With private mapping, individual volumes are directly mapped to individual
hosts.
These volumes are not shared with any other hosts in the host cluster. A host can maintain
the private mapping of some volumes and share other volumes with hosts in the host cluster.
The SAN boot volume for a host would typically be a private mapping.

3.6.3 Ports by host

Click Ports by Hosts to open the pane that is shown in Figure 3-63. This pane lists the Fibre
Channel and iSCSI ports that are assigned to a particular host.
Figure 3-63 Ports by Host window
This overview shows hosts with active, inactive, or degraded ports. You can delete or add a
port, or modify its characteristics. Also, in this pane, you can create a new host or rename the
existing one.
Chapter 3. Graphical user interface overview
117