SonicWall · Firewalls
SonicWall NSv S
Two-core virtual firewall for branches and growing environments, running on compatible hypervisors and public clouds.
Overview
Virtual firewall option for growing environments. Final selection must consider the environment, configuration, licensing and the controls to be enabled.
Key features
- VMware ESXi, Microsoft Hyper-V, KVM Ubuntu/CentOS and ProxmoxVMware ESXi, Microsoft Hyper-V, KVM Ubuntu/CentOS and Proxmox
- AWS and Microsoft Azure; US government clouds depending on the regionAWS and Microsoft Azure; US government clouds depending on the region
- VPN, SD-WAN, segmentation and BGP/OSPF/RIP routingVPN, SD-WAN, segmentation and BGP/OSPF/RIP routing
- Application inspection, IPS, web/DNS filtering and Capture ATP/RTDMI depending on the subscriptionApplication inspection, IPS, web/DNS filtering and Capture ATP/RTDMI depending on the subscription
- Centralised management with NSM/Unified ManagementCentralised management with NSM/Unified Management
- Cloud Secure Edge connector in Global/Classic mode, depending on the licenceCloud Secure Edge connector in Global/Classic mode, depending on the licence
- Active/passive HA on ESXi, Hyper-V, KVM, Proxmox and Azure, subject to platform requirementsActive/passive HA on ESXi, Hyper-V, KVM, Proxmox and Azure, subject to platform requirements
- Design conditionAn active subscription is required to operate
- Design conditionAWS: BYOL or PAYG; Azure: BYOL; confirm available image and region
- Design conditionSubscription package and protection services depend on the SKU and contract
- Design conditionThe licence cannot be migrated directly between BYOL and PAYG
- Design conditionA closed network requires a compatible annual subscription, manual activation and access to MySonicWall through another connected system
- Design conditionPAYG is available only on AWS; government clouds support BYOL only
- Design conditionJumbo Frames and VLAN are not supported on AWS/Azure
- Design conditionDHCP server and relay are available in private clouds, not in public clouds
- Design conditionHA is not supported on AWS; HA on Azure requires an instance type with three or more interfaces
- Design conditionAzure Backup is not supported
- Design conditionNSv S HA on Azure uses a D3v2 VM, according to the datasheet
- Design conditionMSSP programme: 25 GVC clients included, instead of the 50 included with the standard licence
- Design conditionRegional availability, SKU, accessories and licences must be confirmed in the proposal
Technical specifications
| Firewall inspection | 6 Gb/s |
|---|---|
| Minimum storage | 60 GB |
| Supported vCPUs | 2 |
| RAM without Jumbo Frames | 4 GB |
| RAM with Jumbo Frames | 6 GB; Jumbo Frames unavailable on AWS/Azure |
| Virtual interfaces by platform | 8 on ESXi, Hyper-V, KVM and Proxmox; 2 on AWS and Azure according to the datasheet |
| Physical Ethernet ports | Not applicable to the virtual appliance |
| Physical USB | Not applicable to the virtual appliance |
| Physical console port | Not applicable to the virtual appliance |
| Physical management port | Not applicable to the virtual appliance |
| Physical SFP | Not applicable to the virtual appliance |
| WWAN via USB modem | Not applicable to the virtual appliance |
| Wi-Fi radio | Not applicable to the virtual appliance |
| PoE | Not applicable to the virtual appliance |
| Physical TPM | Not applicable to the virtual appliance |
| Threat prevention | 1.6 Gb/s |
| IPS | 4 Gb/s |
| TLS/SSL inspection | 800 Mb/s |
| IPsec VPN | 1.4 Gb/s |
| New connections per second | 13760 |
| Maximum SPI connections | 225000 |
| Maximum DPI connections | 125000 |
| Maximum TLS/SSL DPI connections | 8000 |
| Site-to-site VPN policies | 75 |
| Site-to-site VPN tunnels | 1500 |
| Included IPsec clients | 50 with the standard licence; 25 in the MSSP programme |
| Maximum IPsec clients | 1000 |
| Included SSL VPN clients | 2 |
| Maximum SSL VPN clients | 100 |
| Maximum SSO users | 500 |
| Local database users | 250 |
| Private-cloud virtual interfaces | 8 |
| AWS/Azure virtual interfaces | 2 |
| Maximum logical VLAN/tunnel interfaces | 128; VLAN not supported on AWS/Azure |
| Management/data-plane cores | 1/1 |
| Supported nodes/IPs | Unlimited |
| Compatible AWS instances | c5.large, c5n.large, c5d.large, m5.large, m5n.large |
| Compatible Azure instances | Standard_D2v4, Standard_D2ds_v4, Standard_D2s_v4 |
| Dimensions | Not applicable: virtual appliance |
| Power supply | Not applicable: uses host or cloud instance resources |
| Deployment resource 1 | 2 vCPU |
| Deployment resource 2 | RAM: 4 GB without Jumbo Frames; 6 GB with Jumbo Frames on compatible platforms |
| Deployment resource 3 | Minimum disk capacity of 60 GB |
| Deployment resource 4 | Reserved host resources and instance type must be sized for actual traffic |
| Deployment resource 5 | Supported IPs/nodes: unlimited |
Figures published by the manufacturer. Final sizing depends on the environment, enabled services and traffic profile.