Network Security Manager Saas Getting Started Guide
- Network Security Manager (On-Premises) On-Premises
- Overview
- Before Starting
- Installing NSM on ESXi Server
- Installing NSM on Hyper-V
- Installing NSM on KVM
- Installing NSM on Azure
- NSM Settings and Registration
- Console Operations
- Using NSM
- Integrate On-Prem Analytics with NSM
- Upgrade Instructions
- SonicWall Support
System Requirements
Your security infrastructure must meet certain minimum requirements for the following:
- Browsers Levels
- MySonicWall Account
- Firewall Types and Firmware
- Minimum System Configuration for NSM On-prem
Browsers Levels
NSM is a cloud service that can be accessed over the internet by using one of these supported browsers:
Browser Supported | Notes |
---|---|
Google Chrome |
Latest version This is the preferred browser for the real-time graphics display on the Dashboard. |
Apple Safari | Latest version |
Microsoft Edge | Latest version |
Mozilla Firefox | Latest version |
MySonicWall Account
To login into the Network Security Manager and access licensing information, you must have an active MySonicWall account. Go to www.mysonicwall.com to set up an account if you don't already have one. Refer to Creating MSW Account for details.
Firewall Types and Firmware
The following firewall models can be managed by the Network Security Manager services.
Firewall Categories | Management |
---|---|
Entry Level Firewalls |
SOHO W TZ Series NSv 10-100 |
Mid Range Firewalls |
NSa 2500-6600 NSa 2650-6650 NSv 200-400 |
High-End Firewalls |
SuperMassive 9000 12K Series NSa 9250-9650 NSv 800-1600 |
Zero Touch Deployment |
SOHO-W with firmware 6.5.2 or later TZ Series, NSA Series, NSa Series with firmware 6.5.1.1 or later Not supported for SOHO, NSv Series or SuperMassive Series |
Minimum System Configuration for NSM On-prem
Platform | Version | Configuration |
---|---|---|
VMware |
ESXi 6.5 ESXi 6.7 ESXi 7.0 |
RAM: 16 GB, CPU: 4 cores |
Hyper-V | Windows 2016 | RAM: 16 GB, CPU: 4 cores |
Additional requirements include:
- The firewalls in the configuration must be a part of a tenant.
- Each firewall must have HTTPS management enabled.
For manually added firewalls: if a firewall is behind a NAT device, the HTTPS management port must be opened for the cloud services to communicate with the firewall. This does not apply to firewalls that use Zero Touch Deployment.
Was This Article Helpful?
Help us to improve our support portal