User Guide

Upgrade from 4.16 to 4.17

This guide will lead you through the steps specific for upgrading from a NetEye Single Node installation from version 4.16 to 4.17.

Warning

Remember that you must upgrade sequentially without skipping versions, therefore an update to 4.17 is possible only from 4.16; if you have a 4.15 you must first upgrade to 4.16, then to 4.17.

Before starting an upgrade, you should very carefully read the the release notes on NetEye’s blog and check the feature changes and deprecations specific to the version being upgraded. You can check also the Additional steps to verify if there are changes that might significantly impact your NetEye installation.

Update Procedure

Ensure that you have already updated your operating system by following the CentOS and NetEye Update procedures.

Note

The update procedure must be completed successfully before starting the upgrade.

Verify eligibility to upgrade

In order to verify if your installation can be upgraded, run from the command line the command:

# nohup neteye upgrade

The neteye upgrade command will run a number of checks to make sure that:

  • The version on NetEye installed is eligible for upgrade, that is, it checks which is the installed version (i.e., 4.xx) and that the last upgrade was finalized, i.e., the neteye_finalize_installation script was carried out successfully.

  • NetEye is fully updated and there are no minor (bugfix) updates to be installed.

Warning

The neteye upgrade command may take a long time before it completes successfully, so please do not interrupt it until it exits.

If any of these tasks is unsuccessful, a message will explain where the command failed, allowing you to manually fix the corresponding step. For example, if the exit message is similar to the following one, you need to manually install the latest updates.

"Found updates not installed"
"Example: icingacli, version 2.8.2_neteye1.82.1"

Then, if needed, the command will:

  1. Update all the NetEye repositories to the newer version (i.e., 4.yy, which is the next version to which it is possible to upgrade)

  2. Install all the RPMs of the newer version (i.e., 4.yy)

  3. Upgrade the NetEye’s yum groups

If the command is successful, a message will inform you that it is possible to continue the upgrade procedure, by checking if there are some manual migrations to carry out: if there are, they will be listed in the next section.

Additional steps

In this upgrade, no additional manual step is required.

Migration of RPM Configuration

At this point, before continuing, please first remember to check for any .rpmnew and .rpmsave files (see the RPM configuration migration page).

Finalization Procedure

If all the steps in the previous steps were successful, you can now follow the Finalize the NetEye Upgrade guide in order to complete the upgrade process, otherwise please refer to the next section for troubleshooting options.

Troubleshooting: Failing health checks, migration of modules

After the finalization procedure has successfully ended, you might notice in the Problems View that some health check fails and is in state WARNING. The reason is that you are using some module that needs to be migrated, because some breaking change has been introduced in the release.

Hence, you should go to the Problems View and check which health check is failing. There you will also find instructions for the correct migration of the module, which is in almost all cases amounts to enabling an option: the actual migration will then be executed manually.