
KB 2448: UPDATE YOUR OLFEO DEVICE
An update is available on my Olfeo device. How do I proceed? What precautions should I take?
BACKGROUND
When a new Olfeo update is available, here are a few things to check to ensure that the update goes smoothly.
STEPS
First and foremost, it is essential to read the release notes for this update, which are available on the documentation page of our Olfeo website.
You should install the update promptly in the following cases:
- Security vulnerability fixed.
- Publication of a correction concerning you.
- New feature for you.
Updating the device is not urgent in the following cases:
- There are no malfunctions in the installed version, and the proposed update is only a minor version with fixes that do not affect you.
- New features offered by this version do not apply to you.
Precaution/Best practice:
Back up your configurations by taking a snapshot of the VM.
Perform the update if no alerts are reported:
The v7 procedure.
Frequently asked questions:
How long will the update take?
It all depends on your Internet speed. For your information, on average, one version is about 150 MB.
Should we expect a service interruption?
All Olfeo services are shut down during an update, so you should expect a service interruption lasting several minutes.
Do all members of an Olfeo domain update at the same time?
Each member of the Olfeo domain must be updated individually.
Which machine should I update first in an Olfeo domain?
You must always start by updating the Olfeo domain master machine, and then proceed to update the slaves.
How can I avoid service interruptions?
To do this, you need to use high availability mechanisms (cluster or proxy.pac). Since each member of the Olfeo domain is capable of replacing another, you just need to ensure that the node used by users is not the one being updated (for example: vIP failover or proxy.pac HA behavior).
How can I track the progress of the update?
The best method is still the command line:
#> tail -f /opt/olfeo/data/log/software_update/software_update.log
If the update does not start, contact your Technical Support representative.
VALIDATION
Items to check once the update is complete:
- The services have been started correctly.
- Filtering is functional (AV, URL, Proxy, etc.).
If a feature does not appear to be operational, verify that this is not related to a change in the configuration mode using the online documentation.
- A stability issue occurs after the update: contact yourTechnical Support representative.