SupportProduct Notifications

End of Support (EOS) Notification for NSM On-Prem version 4.0.0 and Below

1785773219

Summary

  • Notification: End of Support
  • Products: NSM on-prem version 4.0.0 and below
  • Effective: Oct 30, 2026
  • Regions Affected: Worldwide
  • Segments: All

Overview

SonicWall is announcing the End of Support (EOS) for NSM On-Prem version 4.0.0 and earlier across all supported platforms (VMware, Hyper-V, Azure, and KVM). As part of our ongoing effort to deliver improved capabilities, NSM On-Prem 4.1.0 introduces several important enhancements to the Zero-Touch API. The existing Zero-Touch functionality in NSM On-Prem 4.0.0 will be deprecated.

Customers must upgrade their NSM On-Prem deployment to version 4.1.0 or later using the supported upgrade path to continue using Zero-Touch features without interruption and have full product support. Customers running NSM 4.1.0 or later will continue to receive technical support and access the latest features and enhancements.

Additionally, NSM On-Prem 4.3.0 is now available and includes the latest features, enhancements, performance improvements, and security updates. Customers are encouraged to upgrade to the latest release to take full advantage of these improvements.

End of Support (EOS) means SonicWall will no longer provide technical support, software updates, upgrades, or replacement materials for the older versions. Any remaining product-specific resources and inventory associated with these releases will also become unavailable.

Customers currently running NSM On-prem 4.0.0 or earlier are strongly encouraged to plan and complete their upgrade to NSM On-prem 4.1.0 or later before the EOS date to ensure uninterrupted access to support services and Zero-Touch functionality.

When will these changes take effect?

End-of-support for the NSM on-prem version 4.0.0 and below will take effect on Oct 30, 2026.

Frequently Asked Questions (FAQ) 

  • When will NSM 4.0.0 reach End of Support (EOS)?
    NSM 4.0.0 will reach End of Support (EOS) on 30 October 2026. After this date, no further product updates, bug fixes, security patches, or technical support will be provided for NSM 4.0.0 & below versions. Customers are encouraged to plan and complete their upgrade to a supported version before the EOS date to ensure continued support and security.
  • Are there any changes required in the firewall, for example, a firmware upgrade or settings, after the upgrade to NSM on-prem 4.1?
    No changes are required on the firewall after the NSM 4.1 upgrade. Customers should upgrade their NSM deployment from version 4.0.0 to NSM 4.1.0 or a later supported release to continue receiving support, updates, and new features. Existing firewall SonicOS versions are not affected by this EOS announcement.
  • What is the replacement product for NSM 4.0.0 and below versions?
    Customers should upgrade their existing deployment to NSM On-Prem 4.1.0 or later to continue receiving technical support and maintain access to Zero-Touch functionality. SonicWall recommends upgrading to the latest available release, NSM On-Prem 4.3.0, to benefit from the newest features, enhancements, security updates, and ongoing product support.
  • Are there any changes to the supported firewall models and versions after upgrading to NSM on-prem 4.1.0 and above?
    There are no changes to the supported firewall models and versions supported in NSM 4.1.0 and later compared to earlier versions of NSM, and users can continue to manage all actively supported firewall models and versions.
  • Do we have an upgrade path that we can use?
    The following table shows the upgrade path for NSM On-Prem 4.3.0

    Current Build

    Upgrade Path to NSM On-Prem 4.3.0

    NSM 4.1.0

    NSM 4.1.0 > NSM 4.3.0

    NSM 4.0.0

    NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.5.0

    NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.2.1

    NSM 3.2.1 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.2.0

    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.2.0 must be a fresh deployment. The user can't upgrade to 3.2 from the previous versions
    Note: Only Backup restore from NSM 3.1.1-HF1 is supported

    NSM 3.1.1-HF1

    Create a backup of 3.1.1-HF1 & Store in external disk.
    Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.1.1

    NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.1.0

    NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.0.1

    NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 3.0.0

    NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.6.0-HF1

    NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.5.0-HF1

    NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.5.0

    NSM 2.5.0 > NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.4.4-R7

    NSM 2.4.4-R7 > NSM 2.5.0 > NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.4.0-R32

    NSM 2.4.0-R32  > NSM 2.4.4-R7 > NSM 2.5.0 > NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.3.5-1-R30

    NSM 2.3.5-1-R30 > NSM 2.4.0-R32  > NSM 2.4.4-R7 > NSM 2.5.0 > NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

    NSM 2.3.4-6-R17

    NSM 2.3.4-6-R17  > NSM 2.3.5-1-R30 > NSM 2.4.0-R32  > NSM 2.4.4-R7 > NSM 2.5.0 > NSM 2.5.0-HF1 > NSM 2.6.0-HF1 > NSM 3.0.0 > NSM 3.0.1 > NSM 3.1.0 > NSM 3.1.1 > NSM 3.1.1-HF1
    - Create Backup of 3.1.1-HF1 & Store in external disk.
    - Fresh deployment of NSM 3.2.0 and restore backup.
    NSM 3.2.0 > NSM 3.5.0 > NSM 4.0.0 > NSM 4.2.0 > NSM 4.3.0

For more information about Product Lifecycle phases, please visit Product Lifecycle

  • Previous Alert
    End of Support Notification of TZ 400, TZ 400W, TZ 600, TZ 600P and NSa 3650
    Read More
Chat