The A10-vThunder-3NIC-2VM-PUBVIP template is used to create two Thunder virtual machines with three network interface cards each and configure the data-in network interface card with Public IP on VIP.
Before deploying this template, it is recommended to review the Prerequisites.
vThunder instances should have the same versions; otherwise, traffic flow will be disrupted.
There are two ways to deploy this template:
To deploy the A10-vThunder-3NIC-2VM-PUBVIP template using Azure Portal Console, perform the following steps:
Download A10-vThunder-3NIC-2VM-PUBVIP template.
From the Azure Portal > Azure services, click Deploy a custom template.
Figure 56 : Azure services
Under the Custom deployment window > Select a template tab, click Build your own template in the editor.
Figure 57 : Custom deployment window
From the Edit template window, perform either of the following step:
Figure 58 : Edit template window
Click Save.
The Custom deployment window is displayed with the template parameters and default values.
Select an existing or create a new Resource group under which you want to deploy the custom template resources.
NOTE: | Hover i for description of each corresponding parameter. |
Update the default values and provide the values in the empty fields as appropriate in the Instance details section shown in Figure 59.
NOTE: | Use a suitable VM size that supports at least three NICs. For VM sizes, see Supported VM Sizes. |
Click Review+create.
The validation appears.
Click Create.
NOTE: | It may take the system several minutes to display your resources. |
Verify if all the above listed resources are created under Home > Azure services > Resource Groups > <resource_group_name>.
Figure 60 : Resource listing under resource group
To deploy the A10-vThunder-3NIC-2VM-PUBVIP template using Azure CLI commands, perform the following steps:
Download A10-vThunder-3NIC-2VM-PUBVIP template.
NOTE: | This template contains pre-populated default values that can be modified as required and it does not create new virtual network, network security group, subnets, and Public IP. |
Configure the following parameters as appropriate:
Resource Name |
Description |
|||
---|---|---|---|---|
Virtual Machines |
Specify a virtual machine name for each of the two vThunder instances. "Virtual Machine1 Name": { "value": "vth-inst1" }, "Virtual Machine2 Name": { "value": "vth-inst2" } |
|||
Virtual Machine Zones |
Specify an availability zone in which to deploy your virtual machine. If you have an existing Public IP, then it should be available in the same availability zone as the virtual machine. "Virtual Machine1 Zone": { "value": "1" }, |
|||
Size |
Specify a suitable size for the vThunder instance.
|
|||
Image |
Specify the desired vThunder Image name and Product name from the Azure Marketplace.
"Publisher": { "value": "a10networks" },
|
|||
Resource Group |
Specify the name of an existing resource group under which the virtual network, network security group, and subnets are already created. "ResourceGroup": { "value": "<existing VN NSG ResourceGroupName>" }, |
|||
Virtual Network |
Specify an existing virtual network name for vThunder.
|
|||
Management Subnet |
Specify an existing subnet name that is available within the selected virtual network for inbound management traffic. "SubnetManagement": { "value": "<existing subnet-mgmt name>" }, |
|||
Data Subnet |
Specify an existing subnet name that is available within a selected virtual network for inbound and outbound data traffic. "SubnetDataIn": { "value": "<existing subnet-data-in name>" }, "SubnetDataOut": { "value": "<existing subnet-data-out name>" }, |
|||
Network Interface Cards
|
Specify a unique network interface card for management, datain, and dataout traffic. "NIC Management VM1": { "value": "vth-inst1-mgmt-nic" }, "NIC DataIn VM1": { "value": "vth-inst1-datain-nic" }, "NIC DataOut VM1": { "value": "vth-inst1-dataout-nic" }, |
|||
Public IP address |
Specify the existing Public IP addresses for management traffic. "Public IP Name VM1": { "value": "<existing Public IP Name VM1>" }, |
|||
Network Security Groups |
Specify an existing network security group name for all the NICs. "Network Security Group VM1": { "value": "<existing Network Security Group VM1 Name>" }, |
|||
Enable Accelerated Networking |
Specify 'true' to enable low latency and high throughput on the NICs. For more information, see Accelerated Networking. "Enable Accelerated Networking": { "value": false },
|
|||
Enable IP Forwarding |
Specify 'true' to allow the virtual machine to forward the network traffic between networks in order to improve the network performance. This high-performance forwarded path bypasses the host from the usual data path, thus, reducing latency, jitter, and CPU utilization when using the most demanding network workloads on the supported VM types. For more information, see IP Forwarding. "Enable IP Forwarding": { "value": false }
|
Run the following command to create an Azure resource group:
PS C:\Users\TestUser\Templates> az group create --name <resource_group_name> --location "<location_name>"
Example:
PS C:\Users\TestUser\Templates> az group create --name vth-rg1 --location "south central us"
{ "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/vth-rg1", "location": "southcentralus", "managedBy": null, "name": "vth-rg1", "properties": { "provisioningState": "Succeeded" }, "tags": null, "type": "Microsoft.Resources/resourceGroups" }
Run the following command to create an Azure deployment group.
PS C:\Users\TestUser\Templates> az deployment group create -g <resource_group_name> --template-file <template_name> --parameters <param_template_name>
Example:
PS C:\Users\TestUser\Templates> az deployment group create -g vth-rg1 --template-file ARM_TMPL_3NIC_2VM_PUBVIP.json --parameters ARM_TMPL_3NIC_2VM_PUBVIP_PARAM.json
Here, vth-rg1
resource group is created.
NOTE: | The resource group of the deployed vThunder instance and it’s resources can be same or different from the resource group of virtual network, NSG, and public IP. |
Figure 61 : Resource listing under resource group