Upgrade prerequisites

Before you start upgrading your ASMS system:

  • read through the Mandatory and Recommended Prerequisites below to determine that the system is ready for the upgrade
  • verify that your system nodes are available and connected as shown in the ASMS system architecture page

Mandatory upgrade prerequisites

The following prerequisites are required before upgrading.

Increased system requirements in ASMS A30.10

System optimizations in version A30.10 require additional CPU and memory specifications.

We highly recommend increasing your system specifications to match the updated requirements, if needed. Systems that remain with legacy minimum specifications may have unexpected results.

For more details, see Hardware minimum requirements.

Note: If your system specifications are already larger than the updated requirements, your system specifications can stay as they are. In such cases, there is no need to resize your entire system.

Tip: If you have a distributed architecture, make sure that you have the required system specifications on all distributed nodes to prevent errors during upgrades.

Minimum version required for upgrades

AlgoSec's upgrade process is supported only from two versions backwards. Therefore, upgrading your system to ASMS version 30.10 is supported only from 2018.2.

If you have an ASMS version earlier than 2018.2, you must first perform any upgrades required to get to 2018.2. For details, see the upgrade procedure in the Installation and Setup Guide for 2018.2 or any other version you are upgrading to. These guides are available from the AlgoSec portal.

Note: Prerequisites and upgrade procedures will differ, depending on your system version.

Example: If you are upgrading from 6.11 to 30.10, perform the following upgrades:

  1. First, upgrade from 6.11 to 2018.2. Use the procedure in the 2018.2 Installation and Setup Guide.
  2. Then, upgrade again from 2018.2 to 30.10. For more details, see Upgrade your system.

Downtime requirements for upgrades

Downtime will be required while all of the servers in your system are upgraded. The downtime will differ depending on the number and types of servers you have. Schedule your upgrade at a time where you can afford this downtime.

Tip: Start the upgrade process to view the runtime estimation. If you're not ready to continue, enter n at the relevant prompt.

Once ASMS begins to upgrade your system, CTRL+C is not supported. Upgrades cannot be aborted.

Disk space requirements for upgrades

5 GB of disk space is required per partition (OS and data) on all appliances:

  • If less than 5 GB of disk space is found, the upgrade process aborts.

  • If there is less than 10 GB of disk space found, the upgrade process presents a warning and enables you to choose whether to continue or not.

    To cancel and run the upgrade later, enter n at the confirmation prompt.

Back to top

Recommended upgrade prerequisites

The following prerequisites are not mandatory, but are recommended:

Backup your system before upgrading

If you have ASMS deployed on virtual machines, we recommend generating a fresh backup before upgrading. This isn't relevant for physical appliances, as restoring or rolling back upgrades on physical appliances is not supported.

For more details, see Backup/Restore.

VisualFlow recommendations for upgrades

Upgrading VisualFlow overwrites any un‐applied workflow drafts, and discards all un‐applied changes.

If you have un‐applied workflow changes in VisualFlow, we recommend that you apply them before upgrading so that you don't lose any work.

HA cluster recommendations for upgrades

If you are upgrading AFA on HA clusters, and also have FireFlow configured, we highly recommend that you upgrade FireFlow as well.

This is not required for DR clusters.

Service recommendations for upgrades

We recommend ensuring that the following services are running when you perform the upgrade:

  • psql
  • metro (apache-tomcat)
  • mongod

If these services are not running, the upgrade process requests that you confirm whether you would like to continue. We recommend contacting AlgoSec customer support to start these services before continuing.

Back to top

 

â See also: