Creating Hosts in a Batch

Context

• A host with mapped volumes cannot be added to a host group.
• A host can be added to only one host group.
• After creating hosts in batches, you need to manually add initiators for these hosts.
• 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 choose Batch Create.

   The Create Host page is displayed.

4. Set basic information for the hosts.

   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 (_).
   Quantity	Number of hosts to be created in a batch. NOTE: A maximum of 1000 hosts can be created at a time. A maximum of 1024 hosts can be created in a cluster.
   Start No.	Start number from which the system incrementally adds a suffix number to the name of each host for distinction. [Value range] 0 to (10000 – Number of hosts created in a batch) NOTE: This parameter is displayed only when Quantity is greater than 1. For example, if you want to create 300 hosts, the value range of the start number is 0 to 9700.
   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.
   Switchover Mode	Set Switchover Mode. Possible options are Disable ALUA and Enable ALUA. NOTE: 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. Specify Name, Quantity, and Start No..
   

   • 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 (_).

6. Set OS. Possible values are Linux, Windows, Oracle, VMware, and XenServer.
   

   The selected operating system type must be the same as that of the host connected to the storage system.

7. Set Switchover Mode. Possible options are Disable ALUA and Enable ALUA.
   

   • 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.

8. Click OK.
9. Confirm your operation as prompted.