Upgrading to 4.0.5 from 4.0.x

NetMon 4.0.5 includes a process to upgrade from versions 4.0.1, 4.0.2, 4.0.3, or 4.0.4. 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. This upgrade may include several additional configuration steps to ensure that existing dashboards and data are not lost. Please follow the instructions in the Upgrade NetMon section of the LogRhythm Documentation site.

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.

If the upgrade to 4.0.5 fails, either wait 24 hours before attempting the upgrade again or run the following command via SSH to verify that the reindexer step is complete:

systemctl status nm-reindexer

If the process is complete, the following message appears, indicating that it is safe to proceed with the upgrade to 4.0.5:

Unit nm-reindexer.service could not be found.

More information about the migration’s progress is available in /var/log/probe/nm-reindexer.log.

Upgrading to 4.0.5 from 3.6.x or Earlier

To upgrade from a version of NetMon prior to 3.6.1, or if you have other questions about the upgrade process, please contact LogRhythm Support.

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.

Potential Need to Re-Apply Enterprise License

When upgrading from 4.0.1, 4.0.2, or 4.0.3 to 4.0.4 or 4.0.5, the Cassandra database is upgraded from 1.1.11 to 3.11, and Enterprise licenses are transferred. If an error occurs in reading and saving the license from Cassandra 1.1.11, then the license will need to be reapplied following the upgrade to 4.0.5.

After completing the upgrade to 4.0.5, log in to NetMon. If prompted to apply a license, reapply your existing license.

Freemium Licenses are not Transferred

Following the upgrade to 4.0.5, a new Freemium license needs to be applied. Prompts for applying the license automatically appear on first login following the upgrade.

New Self-Signed NGINX Certificate and Key Files

New self-signed NGINX certificate and key files are being shipped with 4.0.5 to replace the expired certificate and key. This can cause some issues with browsers. For example, Chrome requires the user type "thisisunsafe" to proceed to NetMon UI.

On upgrade, the UI continues to indicate a system reboot indefinitely. When the UI indicates the upgrade has completed and the system is rebooting, close the browser window, reopen a new browser window, and enter "thisisunsafe" to reload the UI.