SonicOS 7.1 High Availability Administration Guide

Set up an Active/Standby High Availability Configuration Using Azure

SonicWall NSv series brings industry-leading NGFW capabilities, such as application intelligence and control, real-time monitoring, IPS, TLS/SSL decryption and inspection, advanced threat protection, VPN, and Network segmentation capabilities, to protect your Azure environment. The following scenario will show how to deploy a high-availability environment using two Sonicwall NSv in Microsoft Azure's cloud platform.

Azure lets you add cloud capabilities to your existing network through its platform as a service (PaaS) model or entrust Microsoft with all your computing and network needs with Infrastructure as a Service (IaaS).

Product Matrix Table

Product Models NSv 270 NSv 470 NSv 870
Maximum Cores 2 4 8
Minimum Total Cores 2 2 2
Management Cores 1 1 1
Maximum Data Plane Cores 1 3 7
Minimum Data Plane Cores 1 1 1

HA requires a minimum of three interfaces for High-Availability Exchange Messages. Hence, the VM size should be selected as Standard D3_V2 for GEN 7 template deployment. By default, the SonicWall custom template already sets the value Standard_D3_v2.

For example, the following IP addresses are used in this guide.

GEN7NSvHA-01
Vnet 192.168.0.0/16
Resource Group High Availability Standby
WAN IP X1 192.168.1.4/24
LAN IP X0 192.168.2.4/24
HA IP X2 192.168.3.4/24
GEN7NSvHA-02
Vnet 192.168.0.0/16
Resource Group High Availability Standby
WAN IP X1 192.168.1.5/24
LAN IP X0 192.168.2.5/24
HA IP X2 192.168.3.5/24

For the HA interface, use only /24 subnet. There is no such limitation for other interfaces like X0 or X1.

Topology

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