Welcome to syslog-ng Store Box (SSB) version 5 LTS and thank you for choosing our product. This document describes the process to upgrade existing SSB installations to SSB 5 LTS. The main aim of this paper is to aid system administrators in planning the migration to the new version of SSB.
Read the entire document thoroughly before starting the upgrade.
Upgrading to SSB 5 LTS is not supported if you have SSB deployed on any of the following Pyramid hardware: SSB N1000, SSB N1000d, SSB N5000, SSB N10000. For details, see Prerequisites and Notes.
As of June 2011, the following release policy applies to syslog-ng Store Box:
Long Term Supported or LTS releases (for example, SSB 4 LTS) are supported for 3 years after their original publication date and for 1 year after the next LTS release is published (whichever date is later). The second digit of the revisions of such releases is 0 (for example, SSB 4.0.1). Maintenance releases to LTS releases contain only bugfixes and security updates.
Feature releases (for example, SSB 4 F1) are supported for 6 months after their original publication date and for 2 months after succeeding Feature or LTS Release is published (whichever date is later). Feature releases contain enhancements and new features, presumably 1-3 new features per release. Only the last of the feature releases is supported (for example, when a new feature release comes out, the last one becomes unsupported).
Downgrading from a feature release to an earlier (and thus unsupported) feature release, or to the previous LTS release is not supported.
Upgrading to SSB 5 LTS is tested and supported using the following upgrade path:
The latest SSB 4 LTS maintenance version (for example, 4.0.7) -> SSB 5 LTS
Always upgrade to the latest available maintenance version of SSB 4 LTS before upgrading to SSB 5 LTS.
The latest maintenance version of the previous feature release (in this case, SSB 4 F9) -> SSB 5 LTS
From older releases, upgrade to 4 LTS first. For details, see How to upgrade to syslog-ng Store Box 4 LTS.
SSB 5 LTS is not supported on the following hardware: SSB N1000, SSB N1000d, SSB N5000, SSB N10000.
In case you have SSB deployed on other, newer hardware or you have SSB 4 LTS, those will not be affected in any way. The version policy applies to those. For details, open the SSB product page on the Support Portal and navigate to Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.
If you wish to take advantage of new features and remain supported beyond the end date of the Extended Support phase, you need to upgrade your hardware. For assistance with your hardware upgrade, contact our Sales Team. For further inquiries, contact our Support Team.
If you do not know the type of your hardware or when it was purchased, complete the following steps:
Log in to SSB.
Navigate to Basic Settings > Troubleshooting > System debug, click COLLECT AND SAVE CURRENT SYSTEM STATE INFO, and save the file.
Log in to the support portal and submit a ticket.
In the Summary field, enter Determining hardware type.
Upload the file you downloaded from SSB in Step 2.
We will check the type of your hardware and notify you.
The MD5 authentication method and the DES encryption method are no longer available as SNMP trap settings, when configuring SSB to:
Send alerts to a central monitoring server via SNMP v3.
Forward log messages to an SNMP destination using the SNMP v3 protocol.
Due to the removal of support for these authentication and encryption methods, certain configuration changes automatically take effect when you upgrade your SSB to version 5 LTS from 4.0. They are as follows:
MD5 authentication method:
If you have Basic Settings > Management > SNMP trap settings > SNMP v3 > Authentication method set to MD5, that will automatically be set to SHA1.
If you have Log > Destinations > SNMP destination > SNMP trap settings > SNMP v3 > Authentication method set to MD5, that will automatically be set to SHA1.
DES encryption method:
If you have Basic Settings > Management > SNMP trap settings > SNMP v3 > Encryption method set to DES, that will automatically be set to AES.
If you have Log > Destinations > SNMP destination > SNMP trap settings > SNMP v3 > Encryption method set to DES, that will automatically be set to AES.
Note that these automatic changes may require you to reset the relevant configuration options at your end, following an upgrade to version 5 LTS from 4.0.
The following changes have been introduced in SSB 4 F8 regarding the prevention of disk space fill-up:
The default value of Basic Settings > Management > Disk space fill up prevention > Disconnect clients when disks are has changed from 0 to 90.
If you had 0 specified, then following the upgrade, it will change to 90. This means that disk fillup prevention will be turned on by default, with clients getting disconnected once disk utilization exceeds 90%.
Another change concerns the value 100. Starting from version 4 F8, you are only allowed to set values between 1-99. This means that if you had 100 specified before the upgrade, then that will change to 99 following the upgrade.
For more information on preventing disk space from filling up, see "Preventing disk space fill up" in the Administration Guide.
The following changes have been introduced regarding the SNMP trap that is sent when disk utilization exceeds a pre-configured value:
In the dismanEventMIB trap, the value of dskDevice has changed from rootfs to none. This only concerns the disk with index 1.
In case you had some filters or alerts set on the value rootfs, then those will not work anymore.
The dismanEventMIB trap sends out path information in a new field called dskPath.
The following list applies to all configurations:
You have backed up your configuration and your data.
For more information on creating configuration and data backups, see "Data and configuration backups" in the Administration Guide.
For added safety, you have also exported the current configuration of SSB.
For detailed instructions, refer to "Exporting the configuration of SSB" in the Administration Guide.
You have a valid support portal account.
To download the required firmware files, you need a valid support portal account. To create an account, navigate to the support portal and follow the instructions on screen (you will need to enter your product's asset number, which is the license number or serial number you have been provided previously).
You have downloaded the new 5 LTS license file from support portal. As license files are specific to each long term release, upgrading to SSB 5 LTS removes any earlier license.
SSB now strictly checks if you have a High Availability license when running SSB in High Availability mode. You cannot upgrade to 5 LTS or later when using a single-node license in a HA environment. After upgrading to 5 LTS or later, an SSB node can be converted to HA only if a valid HA license is installed. HA licenses include the following line:
To buy a valid HA license, contact your sales representative or contact our Sales Team.
You have downloaded the latest SSB core firmware and boot firmware from the Downloads page.
For a detailed description of the different firmwares, see "Firmware in SSB" in the Administration Guide.
You have read the Release Notes (changelog) of the firmware(s) before updating. The Release Notes might include additional instructions specific to the firmware version.
The Release Notes are available on the Downloads page.
If you have a high availability cluster:
You have IPMI access to the slave node. You can find detailed information on using the IPMI interface in the following documents:
You have verified on the Basic Settings > High Availability page that the HA status is not degraded.
If you have a high availability cluster with geoclustering enabled:
Perform the firmware upload steps an hour before the actual upgrade. Geoclustering can introduce delays in master-slave synchronization, and the slave node might not be able to sync the new firmware from the master node on time.
If you are upgrading SSB in a virtual environment:
You have created a snapshot of the virtual machine before starting the upgrade process.
You have configured and enabled console redirection (if the virtual environment allows it).
During the upgrade, SSB displays information about the progress of the upgrade and any possible problems to the console, which you can monitor with IPMI (ILOM) or console access.
We recommend that you test the upgrade process in a non-productive (virtual, etc.) environment first.
Upgrading SSB requires a reboot. We strongly suggest that you perform the upgrade on the productive appliance during maintenance hours only, to avoid any potential data loss.
If you want to upgrade a SSB cluster, see Upgrading an SSB cluster. To upgrade a standalone SSB node to version 5 LTS, complete the following steps.
Read the following warnings before starting the upgrade process.
Update the core firmware of SSB using the web interface.
Navigate to Basic Settings > System > Core firmwares.
Upload the new core firmware.
When the upload is finished, select the After reboot option for the new firmware.
Do not reboot SSB yet.
Upload the boot firmware of SSB using the web interface.
Navigate to Basic Settings > System > Boot firmwares.
Upload the new boot firmware.
When the upload is finished, select the After reboot option for the new firmware.
Recommended step. To help troubleshoot potential issues following the upgrade, collect and save system information (create a debug bundle) now.
Navigate to Basic Settings > Troubleshooting > System debug and choose Collect and save current system state info.
Navigate to Basic Settings > System > System Control > This node, and choose Reboot.
SSB attempts to boot with the new firmware. Wait for the process to complete.
Log in to the SSB web interface to verify that the upgrade was successful.
Navigate to Basic Settings > System > Version details and check the version numbers of SSB. In case you encounter problems, you can find common troubleshooting steps in Troubleshooting.
Upload the new license file. For details, see Updating the SSB license.