Port Target, Initiator, And Peer Modes; Active And Inactive Hosts; Adding And Removing Hosts - HP 3PAR StoreServ 7200 2-node Manual

For information about controller nodes, see
For more information about physical port and HBA locations, see the Physical Planning Manual
for your system model.

Port Target, Initiator, and Peer Modes

The system controller node ports operate in different modes. Depending on the type of port, the
port may operate in target, initiator, or peer mode.
Fibre Channel ports use the following firmware mode settings:
Target mode for ports that connect to hosts and receive commands from those hosts.
Initiator mode for ports that connect to the system physical disks and send commands to those
disks.
Initiator mode for Remote Copy over FC (RCFC).
iSCSI ports use the following firmware mode settings:
Target mode for ports that connect to hosts and receive commands from those hosts.
Gigabit Ethernet ports use the following firmware mode setting:
Peer mode for Ethernet ports, used for Remote Copy over IP (RCIP).
Fibre Channel over Ethernet (FCoE) ports use the following firmware mode settings:
Target mode for ports that connect to hosts and receive commands from those hosts.
Use the HP 3PAR CLI or the HP 3PAR Management Console to view or change the current port
mode settings. For instructions on viewing or changing mode settings, see the HP 3PAR Command
Line Interface Administrator's Manual and HP 3PAR Management Console Online Help.

Active and Inactive Hosts

An active host is a host that is connected to a system port and recognized by the HP 3PAR OS.
Under normal operation, an active host may have a number of volumes exported to it and therefore
the host has access to those volumes.
An inactive host is a host that is known to the HP 3PAR OS but is not recognized as being connected
to any system port at the moment. This may be because the host is currently disconnected from the
system port, or due to an error condition such as link failure or because the host is offline.
When a host on a system port becomes inactive for any reason, the following happens:
1. The HP 3PAR OS recognizes that the host is missing on the port and changes the state of the
host from active to inactive.
2. The VLUN becomes a template again until the host returns.
3. If and when the host reappears on the same port, The VLUNs are converted from a template
to active again. They do not remain in an active state while the host is unavailable.

Adding and Removing Hosts

The HP 3PAR OS administration tools allow you to create, modify, and remove Fibre Channel and
iSCSI host paths and their properties. When creating a new host, you can either create a host with
or without assigning WWNs or iSCSI Names. A virtual volume that is exported to a host is exported
to all the WWNs that make up the host. If you need to export virtual volumes to particular host
computer WWNs or iSCSI Names, you can create separate hosts on the system and assign each
WWN or iSCSI Name to its own host. Use the HP 3PAR CLI or the HP 3PAR Management Console
to create, modify, and remove hosts.
Hosts can be grouped into autonomic groups that can be managed as one host. If you have a
group of hosts that require the same administrative procedures, it is easier to group those hosts
into an autonomic group and mange them together. For instructions on creating, modifying, and
"HP 3PAR Storage System Hardware" (page
Port Target, Initiator, and Peer Modes
61).
29