Configuring a storage cluster

Virtual Storage Platform One SDS Cloud for Microsoft Azure Setup and Configuration
Version
1.18.x
Audience
anonymous
Part Number
MK-24VSP1SDS010-02

Configure a storage cluster of the cloud model for Microsoft Azure of VSP One SDS Block from Microsoft Azure Marketplace.

CAUTION:

Note the following, as it may be impossible to change the configuration or delete a storage cluster, or a resource added to a resource group may be deleted unintentionally.

  • Be sure to check that the resource group you specify is empty and that no other resources exist.
  • Never add any resources to a resource group for a storage cluster other than those created in the construction of the storage cluster.
Note:

  • When you configure a storage cluster, a trial license is registered in this storage cluster as a base license of VSP One SDS Block. The trial license is valid for 60 days. You need to register another type of base license for continued use of VSP One SDS Block after the trial license expires. For details about how to install a license, see the .

  • For details about the license, see License management overview (Cloud) in the .

  • When using the Universal Replicator function, set the MTU value for the MTU size of the compute network according to your environment. For details, see the VSP One SDS Block and SDS Cloud Universal Replicator.

  1. A user with "subscription owner" or "contributor and user access administrator" permissions accesses the Hitachi Virtual Storage Platform One SDS Block product page in the Microsoft Azure Marketplace.
  2. Select Get It Now, then select Continue if you agree to the terms of use.
  3. Set up Subscription and Plan, then select Create.
  4. In the Basics window, set the project details and instance details, and then select Next.

    Values to be entered are as follows:

    • Project details

      Item

      Setting description

      Subscription

      Select a subscription that manages resources and costs.

      Resource group

      Select or create a new resource group for the storage cluster.

    • Instance details

      Item

      Setting description

      Region

      Select a region in which the storage cluster is to be configured.
  5. In the Base setting window, set the following, and then select Next.

    Values to be entered are as follows:

    Item

    Setting description

    clusterName

    Set the VSP One SDS Block storage cluster name.

    Setting requirements are as follows:

    • The specifiable number of characters is 1 to 30.

    • Alphanumerics and "-" can be used. The first character must be alphabetical and the last must be alphanumeric.

    clusterStructure

    Select the user data protection method.

    Setting requirements are as follows:

    • Single-AZ: Mirroring Duplication

    • Single-AZ: HPEC 4D+2P

    • Multi-AZ: Mirroring Duplication

    timeZone

    Select a time zone to be applied to VSP One SDS Block.

    Set a time zone that the OS can set. ("Asia/Tokyo", "America/Los_Angeles", and others.)

    The time zone is used for contacting customer support in the event of a failure.

    storageAccountName

    Set a storage account for the storage cluster.

    The storage account configured here will be created automatically.

    If the name conflicts with an existing storage account, the creation will fail. Set a unique name.

    Setting requirements are as follows:

    • The specifiable number of characters is 3 to 24.

    • Only lower case alphabetical characters and numbers can be used.

    billingCode

    Set a cost monitoring tag to be assigned to each resource.
  6. In the Cluster configuration window, set the following, and then select Next.

    Values to be entered are as follows:

    Item

    Setting description

    zones

    Select the number of the zone in which the storage cluster is to be configured.

    Setting requirements are as follows:

    • For Single-AZ: "1", "2", "3"

    • For Multi-AZ: "1,2,3", "2,3,1", "3,1,2"

    storageNodeVmSize

    Select the VM size for storage nodes.

    Setting requirements are as follows:

    • Specify either "Standard_E32s_v5" or "Standard_D32s_v5."

    numberOfNodes

    Select the number of storage nodes for the storage cluster.

    Setting requirements are as follows:

    • When Single-AZ configuration and HPEC 4D+2P are used: 6, 12, 18

    • When Single-AZ configuration and Mirroring are used: 3, 6, 9, 12, 15, 18

    • When Multi-AZ configuration and Mirroring are used: 2, 4, 6, 8, 10, 12, 14, 16, 18

    numberOfDrives

    Set the number of user data drives per node.

    Setting requirements are as follows:

    • This number must be from 6 to 24.

    driveSize

    Select the user data drive size (GiB).

    Setting requirements are as follows:

    • For HPEC 4D+2P: 1480, 2661, 3843, 5025, 6650

    • For Mirroring Duplication: 1579, 3155, 4730, 6405, 8473
  7. In the Networking window, set the following, and then select Next.

    Values to be entered are as follows:

    Item

    Setting description

    virtualNetworkResourceGroupName

    Set the name of the resource group created in Creating virtual network resource groups.

    virtualNetworkName

    Set the name of the virtual network created in Creating a virtual network.

    controlSubnetName

    Set the name of the control network subnet created in Creating subnets.

    internodeSubnetName

    Set the name of the internode network subnet created in Creating subnets.

    computeSubnetName

    Set the name of the compute network subnet created in Creating subnets.

    computeIPv6Enable

    Select whether to set an IPv6 address in the compute network.

    Setting requirements are as follows:

    • When you use IPv6 addresses: Select the checkbox.

    • When you do not use IPv6 addresses: Do not select the checkbox.

    computePortProtocol

    Set a network protocol to be used by the compute port.

    Setting requirements are as follows:

    • Specify either "iSCSI" or "NVMe/TCP."
    Note:

    • The character string set for clusterName is used as a prefix of each resource name.

      Example: If you set vsponesdsblock for clusterName, the storage node name is vsponesdsblock-SNXX (where XX is a number such as 01,02...).

    • Some of the IPv4 addresses available for each subnet that you specified are automatically allocated to the storage nodes or load balancer.

      Note that, if you selected "true" for computeIPv6Enable (the case in which IPv6 is also used for compute network), IPv4 and IPv6 addresses are automatically allocated.

    • Some resources, such as protection domains and storage pools, are created with fixed resource names.

      The applicable resources and their resource names are as follows.

      Resource

      Name

      Protection domain

      ProtectionDomain01

      Storage pool

      StoragePool01
  8. In the Advanced window, set the following, and then select Next.

    Values to be entered are as follows:

    Item

    Setting description

    controlNetworkAllowedIpv4AddCidrBlocks

    When the VSP One SDS Block control port is accessed from outside of the virtual network, set a CIDR block of the IPv4 address for which access is to be allowed. The configured values are reflected in the network security group settings. This setting is optional.

    Setting requirements are as follows:

    • When you set IP addresses: Specify IP addresses in the CIDR block format by connecting the addresses with a comma ",".

    computeNetworkAllowedIpv4AddCidrBlocks

    When the VSP One SDS Block compute port is accessed from outside of the compute subnet, set a CIDR block of the IPv4 address for which access is to be allowed. The configured values are reflected in the network security group settings. This setting is optional.

    Setting requirements are as follows:

    • When you set IP addresses: Specify IP addresses in the CIDR block format by connecting the addresses with a comma ",".

    computeNetworkAllowedIpv6AddCidrBlocks

    When the VSP One SDS Block compute port is accessed from outside of the compute subnet, set a CIDR block of the IPv6 address for which access is to be allowed. The configured values are reflected in the network security group settings. This setting is optional.

    Setting requirements are as follows:

    • When you set IP addresses: Specify IP addresses in the CIDR block format by connecting the addresses with a comma ",".

    diskEncryptionSetId

    When you perform managed disk encryption by using an Microsoft Azure customer-managed key, set the resource ID of the disk encryption set.

    Setting requirements are as follows:

    • For disk encryption by using a customer-managed key, enter the ID.

    • For encryption by using a platform-managed key, leave this blank.

    controlMtuSize

    Set the MTU size for the control network.

    Note that this value cannot be changed after storage cluster setup is complete.

    Setting requirements are as follows:

    • This number must be from 1500 to 3900.

    internodeMtuSize

    Set the MTU size for the internode network.

    Note that this value cannot be changed after storage cluster setup is complete.

    Setting requirements are as follows:

    • This number must be from 1500 to 3900.

    computeMtuSize

    Set the MTU size for the compute network.

    When using the Universal Replicator function, set the MTU value according to your environment.

    Note that this value cannot be changed after storage cluster setup is complete.

    Setting requirements are as follows:

    • This number must be from 1500 to 3900.
    Note:

    • The character string set for clusterName is used as a prefix of each resource name.

      Example: If you set vsponesdsblock for clusterName, the storage node name is vsponesdsblock-SNXX (where XX is a number such as 01,02...).

    • Some of the IPv4 addresses available for each subnet that you specified are automatically allocated to the storage nodes or load balancer.

      Note that, if you selected "true" for computeIPv6Enable (the case in which IPv6 is also used for compute network), IPv4 and IPv6 addresses are automatically allocated.

    • Some resources, such as protection domains and storage pools, are created with fixed resource names.

      The applicable resources and their resource names are as follows.

      Resource

      Name

      Protection domain

      ProtectionDomain01

      Storage pool

      StoragePool01

    • To change parameters after configuring a storage cluster, see Changing storage cluster setting values.

      • controlNetworkAllowedIpv4AddCidrBlocks

      • computeNetworkAllowedIpv4AddCidrBlocks

      • computeNetworkAllowedIpv6AddCidrBlocks

      • billingCode

  9. In the Review + create window, confirm the settings you made, and then select Create.
  10. Verify the execution results.

    In the Azure portal, go to the Deployments window of storage cluster resource group to verify that deployment was successful.

  11. Confirm the installation status.

    When the deployment was successful, "InstallationStatus" deployment is automatically added after a while.

    If the "InstallationStatus" value (that is output in "InstallationStatus") is "InProgress", installation is in progress. Wait until "installationStatus" becomes "Completed."

    When "InstallationStatus" is "Completed", storage cluster creation is complete.

    Note:

    • If any of the following conditions exist, a problem has occurred. In such a case, see Action to be taken for a failure that occurred when configuring a storage cluster (Cloud for Microsoft Azure) in the VSP One SDS Block and SDS Cloud Troubleshooting Reference.

      • The deployment results in failure.

      • After 30 minutes have passed, "installationStatus" is not displayed.

      • After 180 minutes have passed, the "installationStatus" value remains "InProgress."

      • The "installationStatus" value is "Failed."

      • The "configuration" value that is displayed in "Outputs" of the initially created deployment is "Configuration Error."

    • If the deployment results in failure, creation of the storage cluster might have resulted in unnecessary resources. Delete such unnecessary resources, verify that there is no problem with the parameter files and others, and then reperform deployment. For details about how to delete unnecessary resources, see Deleting storage clusters (Cloud for Microsoft Azure) in the VSP One SDS Block and SDS Cloud System Administration.

    Tip:

    The approximate time required until storage cluster creation processing completes might differ depending on the storage node configuration. It takes approximately 30 minutes in a configuration of three or six storage nodes.

  12. Verify the Azure Virtual Machines constituting the storage cluster.

    Verify that the Azure Virtual Machines names and Availability Zone you specified for the parameters are correct. Azure Virtual Machines names are shown in the form of "<clusterName>-snXX" and consist of clusterName specified in step 5 and numberOfNodes (XX value) specified in step 6.

  13. Verify that the serial console is functioning properly.

    Select the created Azure Virtual Machine named <clusterName>-SN01. From the service menu, select Help > Serial console to verify you can connect to the serial console. If "Login:" is displayed, there is no issue.

    Note:

    If "Login:" is not displayed, press "Ctrl" + "U" on the serial console, then press the Enter key to confirm "Login:" appears.

  14. Confirm the network service load balancing.

    Select the created load balancer, and then go to Load-balancing rules. Select View details under Health status, and then verify the health status of the load-balancing rule. If there is only one resource whose State is UP, this is normal.

    Also, the number of resources differs depending on the selected user data protection method.

    • Mirroring Duplication: 3

    • HPEC 4D+2P: 5

    The load balancer name is shown in the form of "<clusterName>-LB" and consists of clusterName of the VMConfigurationFile.parameters.json file.

    CAUTION:

    To uninstall a storage cluster, see Removing the storage software in the VSP One SDS Block and SDS Cloud System Administration.

    Note:

    The load balancer status may not be updated automatically. If you do not see any change in the status, perform a manual update using the reload operation and check the status again.

  15. Refer to the load balancer's frontend IP configuration to verify the IP address.

    The load balancer's IP address is used as the destination for accessing the storage cluster via VSP One SDS Block Administrator, the CLI, or the REST API.

    This completes configuration of the storage cluster.