/
Appendix E - Snare Central Update from the Administration Menu

Appendix E - Snare Central Update from the Administration Menu

This guide outlines the steps required to perform a Snare Central update when there is no access to the web based UI or simply because the user prefers to use this method.

NOTE: The process described here only applies to Full-updates and is not suited for applying hot-fixes nor Patch-updates, these types of updates can only be applied from the web UI.

Updates will be released to:

  • Add features to Snare Central

  • Fix issues that have been reported

  • Update operating system components in response to security issues that specifically affect Snare, or tangentially affect the operating system on which Snare relies.

  • Update virus checker signatures.

The full update is available for download from the customer portal, SLDM for customers with a current support and maintenance agreement. A Full update will include all updates since the last major version (eg: patching version 8.0.0 to version 8.7.0)

The update will be made available in the form of a GPG signed compressed archive, for example SnareServer-FullUpdate-v8.0.1-41-g0e0d242.tar.gz.gpg.

Full Update files are likely to grow to a significant size over time, as security and functionality updates to the operating system are included within the update.

Update Requirements

To successfully apply an update from the Administration Menu, the only requirement is that the update file to be used, must be previously uploaded to the Snare Central server via the secure-shell 'scp' application. The file must be transferred directly into /home/snare/SnareUpdate directory.

Once the update file has been successfully transferred, to start the update process:

  1. Log in to the server (v8.6.3 or higher) as the snare user, via SSH.

  2. After a successful login the Snare Central Administration Menu will be presented, Choose the Update option in the menu.

    001Update.png

  3. The Update process will detect if the update file is present or not. Please read this summary carefully.

    002Update.png

  4. From within the Update you will be asked first to provide the password of the local snare user.

    003Update.png

  5. Depending on the size of the update file, this process can take between 15 to 30 minutes to finish.

    004Update.png

  6. The process will provide a detailed log of all the steps involved and any error encountered during the update process. Please bear in mind that depending on the type of error, most of the times an error not necessarily means that the update process has failed. The status of the update will be presented at the end

    005Update.png

  7. Once finish the update process asks for the server to be rebooted. This can be done from the same Administration Menu in the Reboot option.

006Update.png