8. Procedure for upgrading from V102 to V103

8.1. Prerequisites

To deploy the V2.5.3.103 update:

  • The GCenter will need to be version V2.5.3.102-HF3 or higher

  • The GCap will need to be version V2.5.4.0 or higher

  • If you have any questions about these items, please contact the Gatewatcher Technical Support

    Important

    It is highly recommended to have an iDRAC type connection in order to be able to connect post-upgrade if a problem occurs during the process. Otherwise, you'll need a physical access to the equipment (screen, keyboard).

    Important

    Before proceeding with the update, it is strongly recommended to backup the GCenter configuration in the `Administrators > Backup / Restore > Operations` menu and to back up the file on an external server in a directory indicating the current version of the GCenter (example: 2.5.3.102-XXXX-HFX).

8.2. Retained data

The set of the GCenter configuration and data is retained.
Metadata and alerts present on the GCenter before the migration to version 2.5.3.103 will only be viewable in the `Discover` menu of the `Hunting` interface.

8.3. Procedure to install

  1. Make sure the GCap probes are version V2.5.4.0 or higher, otherwise refer to the following update procedure: https://releases.gatewatcher.com/fr/gcap/2.5.4/V0/8_upgrade_procedure.html

  2. Download the newly available version of the GCenter and the associated sha256 on the https://update.gatewatcher.com/upgrade/ platform (directory 2.5.3.103).

Important

For the update to V2.5.3.103, it is recommended to use the latest package.

  1. Check the image with the associated sha256.

  2. Connect to the GCenter WebUI and go to the `Admin > GUM > Software update` menu.

  3. In the `Uploading a new software update` section, click on the `Choose a file` button, select the new GCenter version previously uploaded and then click on `Submit`.

  4. Connect to the GCap with the SSH account setup.

  5. Shut down the monitoring engine with the following command: `monitoring-engine stop`.

  6. Change the compatibility mode with the following command: `set compatibility-mode 2.5.3.103`.

  7. Start the monitoring engine with the following command: `monitoring-engine start`.

  8. To keep the data already being processed at the GCenter, check in the `Hunting > Metadata` menu that there is no further processing.

  9. In the `Saved package list` section, at the location of the previously sent update, click on the `Apply` button.

  10. Once the operation is complete, restart the GCenter by connecting via SSH with the setup account and then going to the `Restart` menu.

  11. Once the GCenter is restarted, connect to the WebUI and check whether new events appear in the `Hunting` section.