Chat now with support
Chat with Support

syslog-ng Store Box 5.0.3 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Troubleshooting SSB Security checklist for configuring SSB About us Third-party contributions

Upgrade checklist

The following list applies to all configurations:

  • You have created a configuration backup of SSB.

    For detailed instructions, refer to Exporting the configuration of SSB.

  • You have a valid support portal account.

    To download the required firmware files and the license, you need a valid support portal account. Note that the registration is not automatic, and might require up to two working days to process.

  • 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.

  • You have read the Release Notes of the firmware(s) before updating. The Release Notes might include additional instructions specific to the firmware version.

    The Release Notes are available here 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.

Upgrading SSB (single node)

Steps:
  1. Update the core firmware of SSB using the web interface.

    Figure 58: Basic Settings > System > Core firmwares — Managing the firmwares

    1. Navigate to Basic Settings > System > Core firmwares.

    2. Upload the new core firmware.

    3. When the upload is finished, select the After reboot option for the new firmware.

      Do not reboot SSB yet.

    4. To read the Upgrade Notes of the uploaded firmware, click the icon. The Upgrade Notes are displayed in a pop-up window.

  2. Upload the boot firmware of SSB using the web interface.

    1. Navigate to Basic Settings > System > Boot firmwares.

    2. Upload the new boot firmware.

    3. When the upload is finished, select the After reboot option for the new firmware.

    4. To read the Upgrade Notes of the uploaded firmware, click the icon. The Upgrade Notes are displayed in a pop-up window.

  3. 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.

  4. Login 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.

Upgrading an SSB cluster

Steps:
  1. Update the core firmware of SSB using the web interface.

    1. Navigate to Basic Settings > System > Core firmwares.

    2. Upload the new core firmware.

    3. When the upload is finished, select the After reboot option for the new firmware.

      Do not reboot SSB yet.

    4. To read the Upgrade Notes of the uploaded firmware, click the icon. The Upgrade Notes are displayed in a pop-up window.

  2. Upload the boot firmware of SSB using the web interface.

    1. Navigate to Basic Settings > System > Boot firmwares.

    2. Upload the new boot firmware.

    3. When the upload is finished, select the After reboot option for the new firmware.

      Do not reboot SSB yet.

    4. To read the Upgrade Notes of the uploaded firmware, click the icon. The Upgrade Notes are displayed in a pop-up window.

  3. 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.

  4. Navigate to Basic Settings > High availability, and verify that the new firmware is displayed for the slave node. This might take a few minutes.

    Note that at this stage, the slave node is not using the new firmware yet.

  5. Go to Basic Settings > System > High availability > Other node and click Shutdown.

  6. Restart the master node: click This node > Reboot.

    SSB attempts to boot with the new firmware. Wait for the process to complete.

  7. Log in to the SSB web interface to verify that the master node 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.

  8. Use the IPMI interface to reboot the slave node.

    The slave node attempts to boot with the new firmware, and reconnects to the master node to sync data. During the sync process, certain services (including Heartbeat) are not available. Wait for the process to finish, and the slave node to boot fully.

  9. Navigate to Basic Settings > System > High availability & Nodes and verify that the slave node is connected, and has the same firmware versions as the master node.

    NOTE:

    When upgrading an SSB cluster, the upgrade process on the slave node will only be completed once a takeover has been performed.

Troubleshooting

If you experience any strange behavior of the web interface, first try to reload the page by holding the SHIFT key while clicking the Reload button of your browser to remove any cached version of the page.

In the unlikely case that SSB encounters a problem during the upgrade process and cannot revert to its original state, SSB performs the following actions:

  • Initializes the network interfaces using the already configured IP addresses.

  • Enables SSH-access to SSB, unless SSB is running in sealed mode. That way it is possible to access the logs of the upgrade process that helps the our Support Team to diagnose and solve the problem. Note that SSH access will be enabled on every active interface, even if management access has not been enabled for the interface.

In case the web interface is not available within 30 minutes of rebooting SSB, check the information displayed on the local console and contact our Support Team.

Related Documents