SonicOS 8 NSv Getting Started Guide for Azure

Technical Documentation>  Installing SonicOS on the NSv Series>  Installing NSv on Azure>  Installing NSv from Azure Template
Table of Contents

Installing NSv from Azure Template

Templates are a means to deploy virtual machines in Azure while also creating/modifying exiting resources. There are a few different types of templates: Quick, Solution and Simple. The following is an example of a Simple template that creates resources and defines their interconnections.

  • Virtual Machine

  • Storage Group

  • Public IP

  • 2 x Network Interfaces

  • Virtual Network

  • Network Security Policy

To install NSv from Azure Template

  1. Log in to Azure.

  2. Navigate to https://github.com/sonicwall/sonicwall-nsv-azure-templates

  3. Under the Deploying heading, click Deploy to Azure.

    4. The Custom deployment page appears.

  4. On the Basics tab, enter the following information to define the custom deployment:
    1. Project details:

      • Subscription – Select the Azure subscription on which to deploy the resources for this NSv instance\

      • Resource Group: The user-defined friendly name for a group of resources.

        If you are deploying on a Azure for the first time, use "Create new," however, if you already have a network configured, and some virtual machines then you might wish to use an existing resource group. If you are deploying for test purposes, we suggest you create a new resource group so you can easily delete the resources later if needed.

    2. Instance details:

      • Region: The Azure geographic region where the resource will be deployed.

      • Location: The deployment location derived from the selected resource group or region.
      • Storage Account: A new or existing storage account (we recommend you create a new storage account).
      • Storage Account Type: The type of storage account you wish to use or create. Currently only “Standard_LRS” is recommended.
      • Storage Account New or Existing: Whether you wish to create or use an existing stage account.
      • Existing Storage Account RG: The resource group that contains the existing Azure storage account used by the deployment.
      • VM Name: Name of the SonicWall-NSv VM in the Azure portal.
      • SSH User Name: The user name required to SSH into the NSv virtual machine.

        • This is not the NSv administrator’s user name, but rather a username created as part of an NSv deployment.

      • Authentication Type: Select either "password" or "sshPublicKey" as the authentication method.
      • SSH Password: The password for the previously mentioned SSH user.

        • Password must contain one non alpha-numeric character (such as !@#$%^&*()_+}{"|: >?<), one uppercase alphanumeric character and one numeric character.

      • SSH Key: Enter the SSH RSA public key file as a string.
      • Image Sku: The name of the Azure product to load.
      • Image Version: The version of the loaded NSv image.
      • Management Access IP Source: Public IP address allowed access SonicWallNSv HTTPS & SSH management.
      • VM Size: The size of the virtual machine.
      • Virtual Network New Or Existing: Determines whether or not a new virtual network should be provisioned.
      • Virtual Network Name: The name of the virtual network the NSv is deployed on.

        • If you have an existing network on Azure, and would like to install the NSv on this network then this field should be populated with the network name. For example, 192.168.0.0/26.

      • Virtual Network Address Prefix: The virtual network address CIDR or "Address space."
      • Virtual Network Resource Group Name: Name of the resource group for the existing virtual network.
      • Subnet WAN Name: The name of the WAN subnet.

        • If you have an existing network on Azure, you might want to change the default value or it can remain at the default.

      • Subnet LAN Name: The name of the LAN subnet.

        • If you have an existing network on Azure you might want to change the default value else it can remain at default.

      • Subnet WAN Prefix: A sub-network of the previous "Virtual Network Address Prefix" defined for WAN traffic, such as 192.168.2.0/24.
      • Subnet LAN Prefix: A sub-network of the previous "Virtual Network Address Prefix" defined for LAN traffic, such as 192.168.2.0/24.
      • Public IP New Or Existing: Determines whether or not a new public ip should be provisioned.
      • Public IP Name: Name of the public IP address.
      • Public IP DNS: DNS of the public IP address for the virtual machine.
      • Public IP Resource Group Name: Name of the resource group for the public IP address.
      • Public IP Allocation Method: Allocation method for the public IP address.
      • Public IP SKU: Name of the resource group for the public ip address.
  5. Click Next.
  6. On the Review + create tab, review the deployment details and then click Create.

It may take some time to deploy the respective NSv resources. To view the progress, click the Notifications icon.

After the deployment completes successfully,

  1. In the left menu, click Virtual Machines, and then select the appropriate virtual machine.
  2. In the Overview section, locate the Public IP address.
  3. Point your browser to the IP address and sign in using the default credentials: admin/sonicwall.

To unlock full system functionality, you must register your NSv virtual machine on MySonicWall. For more information, refer to Registering the NSv Virtual Machine in SonicOS.

Chat