Secure Mobile Access 12.4 Getting Started Guide for Azure

Installing SMA 8200v-Standalone and CMS on Azure

This section explains how to deploy the SonicWall SMA 8200v-standalone and CMS in your Azure environment.

Installation of SMA 8200v-standalone and CMS on Azure is supported only from the SMA 12.4 and above firmware versions.

Deployment Guidelines

For details on deployment guidelines, refer SMA 8200v Azure/AWS Deployment Guidelines | SonicWall

To install the SMA 8200v-standalone and CMS for Azure

  1. Log into your Azure account at https://portal.azure.com.
  2. In the Azure Marketplace, search for and select the SonicWall SMA 8200v listing, then click Get It Now.

    The SonicWall SMA 8200v Virtual Appliance page displays.

  3. In the SonicWall SMA 8200v Virtual Appliance page, click Create.

    The Basics page displays.

  4. By default, the Subscription field is selected based on your currently active Azure subscription. Based on your subscription type, SMA1000 deployment will be created in and billed. If you have multiple subscriptions, you can select a different one in the drop-down menu.

  5. In the Resource group field, select the existing resource group from the drop-down or click Create new to create a new resource group. This is the resource group your SMA 8200v-standalone deployment will be created in.

  6. In the Region field, select the location for these virtual appliance(s).

  7. In the Admin Password and Confirm Admin Password fields, enter the password.

  8. In the SSH public key source field, select the following options from the drop-down.

    • Generate new key pair - If you don't have an existing SSH public key for your Azure account, you can create new key and select the key pair name in the Key pair name field.

    • Use existing key stored in Azure - If you have an existing stored SSH key for your Azure account, under Stored Keys field, select a key from the drop-down.

    • Use existing public key - If you have an existing SSH public key for your Azure account, enter the text of your existing key into the SSH public key field.

  9. Click Next: Central Management >.

    The Central Management page displays.

  10. In the Deploy CMS?, select the following options based on your requirement.

    Select Yes - To deploy CMS on Azure.

    Select No - Not to deploy CMS on Azure.

    In the Size field, the default memory size displays in the above field. If you wish to select a different configuration, click Change size and select the memory size based on your requirements.

    The minimum recommended memory size for CMS is 1x Standard D2 v3.

  11. Click Next: VPN Appliances >.

    The VPN Appliances page displays.

  12. In the Count field, enter the number of SMA 8200v-standalone appliances you need to deploy. If you do not need to deploy SMA 8200v-standalone appliance on Azure, then enter the count as 0 in the count field.

  13. In the Size field, the default memory size displays based on the SMA 8200v-standalone count entered in the above field. If you wish to select a different configuration, click Change size and select the memory size based on your requirements.

    The minimum recommended memory size is 2 vcpus and 8 GB RAM.

    The following recommendations are intended as guidelines to instance type selection, derived from extensive lab-based testing and analysis. It is extremely important to keep in mind that inherent differences in deployment-specific usage patterns may necessitate use of larger, or smaller, instance types than these general-purpose recommendations.

    Expected User Count Recommended Instance Type Specification
    Up to 500 F2 2 core, 4GB RAM
    Up to 2000 F4s_v2 4 core, 8GB RAM
    Up to 5000 F8s_v2 8 core, 16GB RAM

  14. Click Next: Networking.

    The Networking page displays.

  15. In the Networking page, configure the virtual network based on your requirements.

    1. In the Virtual Network field, select an existing virtual network from the drop-down or click Create new to create a new virtual network.
    2. In the Subnet field, select a subnet from the drop-down.
    3. By default, the VPN Access CIDR field is set to 0.0.0.0/0 which allows you to access VPN from any place. If you want to limit VPN access to a trusted IP range, enter that IP range in this field.
    4. By default, the Admin CIDR field is set to 0.0.0.0/0 which allows you to access AMC and SSH from any place. If you want to limit AMC and SSH access to a trusted IP range, enter that IP range in this field.

      For details on how to configure static IP pools for VPN tunnels in Azure, see SMA 8200v Azure/AWS Deployment Guidelines | SonicWall

  16. Click Next: Review + create >.

    The Review + create > page displays.

  17. Verify the instance details shown in the screen and click Create.

    The SMA 8200v-standalone and CMS for Azure is automatically started at the end of the installation process.

    A pop up screen with deployment status displays.

  18. Once the deployment is complete, the following screen displays.

  19. Click Go to resource group and select the virtual machine that you want to manage.

    After the SMA 8200v-standalone and CMS instance is launched, you can access the appliance from a browser. See Connecting to the Web Interface for details.

    Console access is available via the ssh command with the username 'admin' and the SSH key you specified during deployment. See Connecting to the Command Line Interface for details.

You are now ready to begin using your SMA 8200v-standalone and CMS appliance. See:

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

  • Hidden
  • Hidden

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.
  • Hidden
  • Hidden