Version 3.1.1 On-Premises

September 2025

Important

• Refer to the knowledge base article, How to Upgrade SonicCore and NSM in Closed Network for detailed instructions on upgrading NSM in closed network environment.
• Refer to the knowledge base article, Upgrade using management console for detailed instructions on a system upgrade. Prior to update, you need to create a system backup of the NSM on-premises system in case you need to roll back to the prior version. Refer to Backup and Restore an NSM On-Prem System for detailed instructions.

• Refer to knowledge base article, How to Upgrade On-Prem Network Security Manager firmware for detailed instructions on upgrading NSM firmware using SWI files.

Compatibility and Installation Notes

• Most popular browsers are supported, but Google Chrome is preferred for the real-time graphics display on the Dashboard.
• A MySonicWall account is required.

• Capacity Requirements: The capacity requirements for an NSM On-Premises deployment have changed:

  Supported Platforms

  Platform	Platform Details
  VMware	Supported versions: ESXi 7.0, 8.0
  Hyper-V	Windows 2019, 2022
  KVM	Linux Kernel 5.15 LTS
  Azure	Standard_D4_v2 Standard_D5_v2 Standard_D16as_v5 Standard_D8as_v5

  Management Only

  Number of Firewalls	CPU (Cores)
  100	4
  150	4
  250	8
  500	8
  750	8
  1000	8
  1000+	16

  Management Only

  Number of Firewalls	CPU (Cores)	RAM (GB)
  100	4	16
  150	4	16
  250	8	16
  500	8	16
  750	8	16
  1000	8	16
  1000+	16	32

  Management, Reporting and Analytics

  Number of Firewalls	CPU (Cores)	RAM (GB)
  100	4	24
  150	4	24
  250	8	24
  500	8	32
  750	8	32
  1000	8	32
  1000+	16	64

  Reporting Disk Space Requirements (Data Storage + Cache)/SSD

  Number of Firewalls	Data Retention 7 days	Data Retention 365 days
  50	600 GB	750 GB
  100	1.2 TB	1.5 TB
  150	1.7 TB	2.3 TB
  250	2.8 TB	4 TB

  Distributed Deployments Sizing Guideline

  Number of Firewalls	NSM Nodes
  ≤ 250	NSM Controller Node / Single Node Deployment
  > 250	Controller Node + 1 Reporting Agent per 250 firewall
  Reporting Agent resource requirements (CPU and RAM ) is the same as the controller node.

• Upgrade Instructions:

   

  • We strongly recommend using the system update method to upgrade NSM using steps captured in the Upgrade using management console.
  • Minimum 50% of the free disk space is required to upgrade.

  Current Build	Upgrade Path to 3.1.1 On-Prem
  NSM 2.6.0 HF1	NSM 2.6.0 HF1 > NSM 3.0.0 > NSM 3.1.1
  NSM 3.0.0	NSM 3.0.0 > NSM 3.1.1
  NSM 3.1.0	NSM 3.1.0 > NSM 3.1.1

Resolved Issues

Issue ID	Description
NSM-29792	Alert & notifications > History: Alert notifications for web categories get removed from user interface after refresh.
NSM-31602	In Hyper-V environment, the external storage/reporting disk is not mounting the full size; causes reporting issues.
NSM-31670	Commit/Deploy Fetch Status icon does not update after the commit is deployed.
NSM-31701	Device status shows incorrectly in device details following a local firewall configuration change.
NSM-31836	Migrating from On-Prem to SaaS using Zero Touch fails to update the Zero Touch URL and does not acquire properly.

Known Issues

Issue ID	Description
NSM-31946	Aggregated scheduled reports fail to run on-demand.
NSM-32231	Secondary HA firewalls are getting added to the Inventory when Secondary is active.
NSM-32409	When navigating to Firewall View | Device > Time, an error message appears: Cannot read properties of null.

Additional References

NSM-32379, NSM-31979, NSM-31927, NSM-31896, NSM-31668, NSM-31667,NSM-31301, NSM-31252, NSM-31251