Creating a virtual network

Create a virtual network for setting up VSP One SDS Block.

Note:

If you have already created a virtual network with a sufficient IP address range to create the following resources, you can use it to set up VSP One SDS Block without the need to create a new virtual network.
- Storage node: uses 3 IP addresses per node (one for the control network, one for the internode network, and one for the compute network)
- (Multi-AZ configuration)Tiebreaker node: uses 2 IP addresses per node (one for the control network and one for the internode network)
- Compute node: uses 2 IP addresses per node (one for the control network and one for the compute network)
  
  The following can be selected for using a compute network subnet by each storage cluster.
  - IPv4 addresses (single stack)
  - IPv4/IPv6 addresses (dual stack)
- Controller node: uses 1 IP addresses per node (for the control network)
- Load balancer: Uses 1 IP addresses per storage cluster
Creating a virtual network according to the procedures enables Azure virtual network encryption. If you use the created virtual network and Azure virtual network encryption is required, enable the encryption setting. For details about how to enable the encryption setting, see the Microsoft Azure documentation.

Log in to the Azure portal.
Connect to any environment in which Azure CLI execution is available (Example: Cloud Shell).

The subsequent procedures use Cloud Shell.
To set the desired subscription, use the following command. If you do not want to set a subscription, go to the next step.
```
az account set --subscription <Subscription ID>
```
Place the template file in any directory in which you want to run the Azure CLI command, and then unzip it.
Two methods are available for obtaining the file: 1) through Azure Blob Storage, or 2) upload it from Manage files on Cloud Shell.

If you want to obtain the file from Azure Blob Storage, use the following Azure CLI command. (To obtain the file from Azure Blob Storage, you need to upload the file to a container beforehand.)
```
az storage blob download \
--account-name <account-name> \
--container-name <container-name> \
--name <Blob-name> \
--file <path-of-file-to-be output>
```
Among the extracted template files, edit VNetConfigurationFile.parameters.json.
Parameter
- virtualNetworkName: Any virtual network name (The valid number of characters for this value is 2 to 64. Only alphanumerics, underscore, dot, and hyphen can be used. This value must start with an alphanumeric and end with an underscore or alphanumeric.)
- vNetIPv4CidrBlock: CIDR block for IPv4 addresses
- vNetIPv6CidrBlock: CIDR block for IPv6 addresses
- billingCode: Cost management tag
Note:
- For the virtual network name, follow the Microsoft Azure naming conventions in the Microsoft Azure user guide.
- If you do not use IPv6 addresses, you can skip entering vNetIPv6CidrBlock.
- The range of IPv4 addresses for vNetIPv4CidrBlock and vNetIPv6CidrBlock should be in the form of CIDR block (Example: 10.160.0.0/16). The size of the CIDR block should be between /16 and /28. In addition, the size of the CIDR block should be large enough to create storage nodes, tiebreaker nodes, controller nodes, compute nodes, and load balancers.
- Note that IP addresses (reserved by Microsoft Azure) for the subnet created in Creating subnets cannot be used for VSP One SDS Block resources.

Run the following command.

az deployment group create \
--name mainTemplate \
--resource-group <any-virtual-network-resource-group-name> \
--template-file VNetConfigurationFile.json \
--parameters VNetConfigurationFile.parameters.json

Verify the execution results.

Verify that the CLI execution was successful. Alternatively, in the Azure portal, go to the Deployments window of virtual network resource group to verify that deployment was successful.