Highlights

An overview of the most impactful changes in this release.

ZFS pool compatibility when rolling back from N2OS 26.5.0

Starting with Nozomi Networks Operating System (N2OS) v26.5.0, N2OS includes newer versions of FreeBSD and OpenZFS. Any Zettabyte File System (ZFS) data_pool that you create or recreate while the system is running N2OS v26.5.0 can enable ZFS features that are not available in earlier N2OS versions.

If you:

  • Upgrade a Guardian from N2OS v26.4.0 (or earlier) to N2OS v26.5.0, and then
  • Create or recreate the data_pool on N2OS v26.5.0 (for example by running n2os-datafactoryreset or by performing other operations that recreate the pool), and then
  • Roll back the system to N2OS v26.4.0 (or earlier)

The data_pool might no longer be importable in read-write mode on N2OS v26.4.0 (or earlier). In this situation, zpool import reports that the pool uses features that the older ZFS version does not support. You can import the pool only in read-only mode. As a result, the system does not mount /data, /data/log, and /data/tmp.

This behavior is expected. ZFS guarantees that newer ZFS versions can import pools created on older versions (backward compatibility), but not the opposite (forward compatibility). A pool created or recreated on N2OS v26.5.0 might use new features that ZFS on N2OS v26.4.0 (or earlier) does not support.

Important:
Avoid running n2os-datafactoryreset or otherwise recreating the data_pool while the system is on N2OS v26.5.0 if you might need to roll back to N2OS v26.4.0 (or earlier).

If n2os-datafactoryreset has already been run on N2OS v26.5.0 and a rollback to N2OS v26.4.0 (or earlier) is then performed, the recreated data_pool cannot be used directly on the older version. In this scenario, our Customer Support team can:

  • Help you import the pool in read-only mode on N2OS v26.4.0 (or earlier) to inspect or extract specific files where possible, and/or
  • Guide you through clearing the ZFS metadata so that N2OS v26.4.0 (or earlier) can recreate a new empty data_pool and you can restore from backup

Plan upgrades, data factory resets, and potential rollbacks together. Before you run n2os-datafactoryreset on N2OS v26.5.0, contact our Customer Support team if you might need to roll back. The team will review the upgrade and rollback strategy and confirm that a valid backup and recovery path is in place.

Alert deduplication

N2OS v26.5.0 enables alert deduplication by default for all deployments. This new default applies to both new installations and existing installations that have not explicitly configured alert deduplication. This change reflects Nozomi Networks' confidence in the feature's stability and its impact on reducing alert noise and improving operator focus.

  • New and existing installations of N2OS v26.5.0, or later, have alert deduplication turned on by default.
  • The feature remains fully configurable and can be toggled from N2OS or Vantage, depending on the deployment.
  • Existing deployments upgrading to N2OS v26.5.0 keep their explicit configuration for alert deduplication:
    • If you explicitly enabled or disabled deduplication, N2OS preserves that choice across the upgrade.
    • If you left the configuration at its default state, your deployment adopts the version default: disabled by default in N2OS v26.3.0 and v26.4.0, and enabled by default starting with v26.5.0.
Important:
When alert deduplication is enabled, incidents will no longer be generated.

Before you enable alert deduplication, review whether incidents are still required in your environment. If incidents are critical to your operations, do not enable alert deduplication at this time.

If you rely on incidents, open a support ticket and describe how you use them today. Include any key workflows, configurations, reports, or integrations. This feedback will help Nozomi Networks evaluate future incident use cases that can work alongside alert deduplication.

Receiving updated alerts through data integrations

When the alert deduplication feature is enabled, the data integrations will only receive the first event of each alert. This standard behavior helps reduce the number of alerts in the corresponding tool. In some environments, it can also reduce the visibility of security events. To avoid this, data integrations now support a configuration to send alert updates. With this configuration turned on, the alerts are sent again when a new event is recorded.

Minimum ESXi version requirement

Starting with N2OS v26.5.0, the lowest compatible version of ESXi is 9.0. This is due to N2OS's adoption of FreeBSD 15.x, which VMware does not list as a supported and compatible version of FreeBSD for ESXi versions lower than 9.0.

Nozomi Networks cannot support virtual deployments unless they use the correct ESXi and Nozomi Networks version combination, for both new deployments and upgrades of existing deployments:
  • N2OS v26.5.0, or higher (leveraging FreeBSD 15.x), Host ESXi v9.0, and virtual hardware version 22, or higher
  • N2OS between v26.4.0 and v24.5.1 (leveraging FreeBSD 14.x), Host ESXi between v9.0 and v8.0, and virtual hardware between version 22 and version 20

For more information on ESXi virtual hardware version and FreeBSD compatibility, see VMware's OS Compatibility Guide.