Determine the NetMon Version and Upgrade Path

This guide helps you determine which version of NetMon you are currently using, and the upgrade path(s) you can take to get to newer versions.

Determine the NetMon Version

To determine the version of NetMon you’re using:

Log into NetMon using your browser.
At the top-right of the main page, click the question mark.
In the menu, click About NetMon. The System Details screen appears. The application version is shown in the red box.

Upgrading to NetMon 5.0.0 from Any Version

NetMon 5.0.0 includes major updates to the operating system, migrating from CentOS to Rocky Linux 9.4, along with major updates to underlying dependencies which require a reinstallation of the operating system using the NetMon ISO/USB utility; therefore, upgrading from a previous version to 5.0.0 is not possible without a new install of the NetMon software. Existing NetMon customers are encouraged to backup any customizations such as dashboards, DPA rules, and third-party integrations so they can be re-applied after the upgrade is complete. For more information, review the Backup NetMon Components guide.

NetMon Upgrade Path

Use the table below to find your NetMon upgrade path.

Find your current version (determined in the section above) in the left column of the table.
To find the version you need to go to next, browse the Upgrade Path column in the NetMon table.
For older versions, you may need to perform a hop2 upgrade to a version before being able to proceed to the next/latest version.

NetMon Version	Upgrade Path	Description
Versions earlier than 2.6.1	Not supported	An upgrade path for versions earlier than 2.6.1 is not recommended. To upgrade, perform a new installation with version 4.0.3.
Versions 2.6.1 to 2.8.1	Upgrade to 2.8.2	A CentOS dependency requires you to upgrade to 2.8.2 before continuing the upgrade process.
Versions 2.8.2 to 3.2.1	Upgrade to 3.2.2	A CentOS 7.2 upgrade requires you to upgrade to 3.2.2 before continuing the upgrade process.
Version 3.2.2	Upgrade to 3.2.3	A user interface change requires to upgrade to 3.2.3 before continuing the upgrade process.
Version 3.2.3	Upgrade to 3.6.1	In previous versions of NetMon, upgrading to the newest version could reset your custom engine configuration settings to the NetMon defaults. Starting in NetMon 3.6.1 and in all future releases, upgrades will not change your custom settings back to the default values NetMon 3.6.2 was a critical security update, and all users running older versions of NetMon should upgrade to 3.6.2 or later as soon as possible.
Versions 3.6.1 to 3.9.3	Upgrade to 4.0.1	If upgrading from a pre-3.9.1 release, a new security certificate is included with the install. In this case, the upgrade page does not automatically refresh after the system reboots. The upgrade usually takes about 15 minutes, after which you must manually refresh your browser and log in to NetMon again, The upgrade to NetMon 4.0.1 is a best-effort migration of existing Elasticsearch 1.7 data into Elasticsearch 7.2. Re-indexing Elasticsearch 1.7 data to Elasticsearch 7.2 takes significant time up to several hours per 10 GB of metadata, depending on the size of the indices.
Versions 4.0.1 to 4.0.4	Upgrade to 4.0.5	If you are upgrading from NetMon 3.6.1 - 3.9.3 and performed the intermediate upgrade step to NetMon 4.0.1, you must wait until the 4.0.1 nm-reindexer process finishes before upgrading to 4.0.5. The 4.0.1 nm-reindexer process migrates the previous Elasticsearch 1.7 indices to the Elasticsearch 7.2 index format.
Version 4.0.5 to 4.06	Upgrade to 4.0.7	If you are running version 4.0.1 - 4.0.4, upgrade directly to 4.0.5 before upgrading to 4.0.7. If you are running NetMon 3.6.1 - 3.9.3, you must first upgrade to version 4.0.1 before continuing the upgrade to 4.0.5, then upgrade to 4.0.7.
Any version	NetMon 5.0.0	Upgrading to NetMon 5.0.0 requires a full reimage of your appliance/machine. Due to major underlying changes in the operating system and dependent packages there is no supported inline upgrade path; the product must be fully reinstalled.