Creating a Single Host

Context

• A host with mapped volumes cannot be added to a host group.
• A host can be added to only one host group.
• When creating a host, you can select an initiator for it.
• Each host must be associated with initiators.

Prerequisite

Initiators have been configured.

Procedure

1. Choose Resources > Access > Host > Host.
2. Select the desired account from the Account drop-down list in the upper left corner.
3. Click Create and select Single Create.

   The Create Host page is displayed.

4. Set basic information for the host.

   Table 1 describes related parameters.

   Table 1 Host parameters

   Parameter	Description
   Name	Indicates the name of a host. [Value range] The name must be unique. The name contains 1 to 31 characters. The name can contain only letters, digits, underscores (_), hyphens (-), periods (.), and colons (:), and must start with a letter, digit, or underscore (_).
   IP Address	Indicates the IP address of a host. NOTE: If a host is connected over iSCSI links, enter the service IP address of the host for easy management.
   OS	Indicates the type of the operating system running on a host. [Value range] Possible values are Linux, Windows, Oracle, VMware, and XenServer. NOTE: The selected operating system type must be the same as that of the host connected to the storage system.
   Initiator	Add an initiator for the host. NOTE: You can click Add to select multiple initiators. Do not add initiators of different application servers to the same host. You are advised to map a volume to a host using initiators of the same type.
   Switchover Mode	Set Switchover Mode. Possible options are Disable ALUA and Enable ALUA. NOTE: Asymmetric Logical Unit Access (ALUA) is a model that supports access to multiple target ports. In the multipathing state, the ALUA mode presents active/passive volumes to the host and provides a port access status switchover interface to switch over the working controllers for volumes. For example, when a controller fails, the status of the controller port is set to Unavailable. After the host multipathing software that supports ALUA detects the status, it switches subsequent I/Os from the failed controller to the peer controller. In non-HyperMetro scenarios, it is advised to set Switchover Mode to Disable ALUA. This is because the storage system is in active/active mode in non-HyperMetro scenarios and enabling ALUA is meaningless. In HyperMetro scenarios, if both sites provide services at the same time, you are advised to set Switchover Mode to Disable ALUA. In HyperMetro scenarios, if only one site provides services, it is advised to set this parameter to Enable ALUA at the site that provides services.

5. Click OK.
6. Confirm your operation as prompted.