Update Procedure¶

This guide will lead you through the steps of updating NetEye.

Prerequisites¶

NetEye must be up and running in a healthy state.
Disk Space required:
- 3GB for / and /var
- 150MB for /boot

Update NetEye Single Instance¶

Run the update command:
```
neteye# nohup neteye update
```
After the command was executed, the output will inform if the update was successful or not:
- In case of successful update you might need to restart NetEye to properly apply the updates. If the reboot is not needed, please skip the next step.
- In case the command fails refer to the troubleshooting section.
Reboot the node to apply the updates correctly if required:
```
neteye# neteye node reboot
```
Finally, to ensure that any potentially stopped and/or newly installed NetEye services are running, use the command
```
neteye# neteye start
```

Update NetEye Cluster¶

Updating a cluster will take a nontrivial amount of time, however no downtime needs to be planned. During the update, individual nodes will be put into standby mode. Thus, overall performance will be degraded until the upgrade is completed and all nodes are revoked from standby mode. Granted the environment connectivity is seamless, the update procedure may take up to 15 minutes per node.

1. Run the Update¶

The Cluster Update is carried out by running the following command:

cluster# (nohup neteye update &) && tail --retry -f nohup.out

Warning

If the SIEM feature module is installed and a new version of Elasticsearch is available, please note that the procedure will update one node at the time and wait for the Elasticsearch cluster health status to turn green before proceeding with the next node. For more information, please consult the dedicated section.

After the command was executed, the output will inform if the update was successful or not:

In case of successful update you might need to restart the nodes to properly apply the updates. If the reboot is not needed, please skip the next step.
In case the command fails refer to the troubleshooting section.

2. Reboot Nodes¶

Restart each node, one at a time, to apply the updates correctly.

Run the reboot command
cluster-node-N# neteye node reboot
In case of a standard NetEye node, put it back online once the reboot is finished
cluster-node-N# pcs node unstandby --wait=300

You can now reboot the next node.

3. Cluster Reactivation¶

At this point you can proceed to restore the cluster to high availability operation.

Bring all cluster nodes back out of standby with this command on the last standard node
cluster# pcs node unstandby --all --wait=300 cluster# echo $?
0
If the exit code is different from 0, some nodes have not been reactivated, so please make sure that all nodes are active before proceeding.
Run the checks in the section Checking that the Cluster Status is Normal. If any of the above checks fail, please call our service and support team before proceeding.
Re-enable fencing on the last standard node, if it was enabled prior to the update:
```
cluster# pcs property set stonith-enabled=true
```

NetEye Satellites¶

Prerequisites¶

To update a Satellite it is required to have the configuration archive located in /root/satellite-setup/config/<neteye_release>/satellite-config.tar.gz.

1. Run the Update¶

To automatically download the latest update you can run the following command on the Satellite:

sat# neteye satellite update

After the command was executed, the output will inform if the update was successful or not:

In case of successful upgrade you might need to restart NetEye to properly apply the updates. If the reboot is not needed, please skip the next step.
In case the command fails refer to the troubleshooting section.

2. Reboot¶

Restart NetEye to apply the updates correctly.

sat# neteye node reboot

3. Setup¶

Execute the command below to setup the Satellite with the new updates:

sat# neteye satellite setup

DPO Machine¶

It is possible to update the Docker image used on the DPO machine, by running, on a NetEye Master node, the following command:

neteye# neteye dpo setup

The command updates the container image at every execution, ensuring you are using the latest available image matching your NetEye version, and restarts the already configured containers with the updated image.