Fortinet black logo

Upgrading a FortiSOAR Enterprise Instance

Copy Link
Copy Doc ID 193de878-ba1f-11ec-9fd1-fa163e15d75b:332067
Download PDF

Upgrading a FortiSOAR Enterprise Instance

To upgrade your system to FortiSOAR from 7.0.0, 7.0.1, or 7.0.2 to 7.2.0, perform the following steps:

  1. Users who have root access must run the upgrade installer.
  2. ssh to the VM that you want to upgrade.
  3. Check that you are connected to a screen session. A screen session is needed for situations where network connectivity is less than favorable. You can check your screen session using the following command:
    # screen -ls
    This command returns an output such as the following example:
    There is a screen on:
    12081.upgrade(Detached)

    Log back into the SSH console and run the following command to reattach the screen session:
    screen -r 12081.upgrade
    OR
    screen -r upgrade
  4. Run the following command to download the upgrade installer:
    # wget https://repo.fortisoar.fortinet.com/7.2.0/upgrade-fortisoar-7.2.0.bin
    Note: If your instance can connect to "repo.fortisoar.fortinet.com" only by using a proxy, then ensure that the proxy is set in the /etc/wgetrc file. For example,
    use_proxy=yes
    http_proxy=<proxy_server_ip:port>
    https_proxy=<proxy_server_ip:port>
    You can also set the proxy while running the FortiSOAR Configuration Wizard or by using the csadm network command.
  5. Run the upgrade installer using the following command:
    # sh upgrade-fortisoar-7.2.0.bin
    OR
    # chmod +x upgrade-fortisoar-7.2.0.bin
    # ./upgrade-fortisoar-7.2.0.bin
    Notes: The FortiSOAR upgrade installer checks for the following:
    • The space available in /tmp or /var/temp (if exist in /etc/fstab), which must be at least 500MB. If the space available in /tmp or /var/temp is less than 500MB, then the upgrade installer exits after displaying an appropriate error message. If you want to skip this space validation check, you can use the --skip-tmp-validation option while running the upgrade script:
      # ./upgrade-fortisoar-7.2.0.bin --skip-tmp-validation
    • The disk space available in /boot, and if the /boot has insufficient space, then the upgrade installer exits after displaying an appropriate error message. Steps for cleaning up /boot are present in the Clean up /boot article present in the Fortinet Knowledge Base.
    • The disk space available in /var/lib/pgsql to ensure that you have sufficient disk space for pgsql. If you do not have sufficient disk space for pgsql, in this case also the upgrade installer exits. In these cases, you must increase the partition size for /var/lib/pgsql. For the procedure to increase the partition size, see the 'Issues occurring in FortiSOAR due to insufficient space' section in the Deployment Troubleshooting chapter in the "Deployment Guide" for more information.
    Once you complete cleaning up /boot and/or increasing disk space and space in /tmp (as per the messages provided by the upgrade installer) and you have sufficient space for upgrading FortiSOAR, you must re-run the upgrade installer to continue the process of upgrading FortiSOAR.
    Important: To upgrade a high availability cluster in FortiSOAR, you require to upgrade each node individually, one after the other. For more information, see the Upgrading a FortiSOAR High Availability Cluster section. For information on how to upgrade a FortiSOAR distributed multi-tenant configuration to 7.2.0, see the Upgrading a FortiSOAR Distributed Multi-Tenancy Configuration section.
    Note: When you upgrade your FortiSOAR enterprise instance, High Availability (HA) cluster, or a distributed multi-tenant configuration, the FortiSOAR appliance hostkey also gets changed.
  6. Once your FortiSOAR instance is upgraded, you must log out from the FortiSOAR UI and log back into FortiSOAR.

Upgrading a FortiSOAR Enterprise Instance

To upgrade your system to FortiSOAR from 7.0.0, 7.0.1, or 7.0.2 to 7.2.0, perform the following steps:

  1. Users who have root access must run the upgrade installer.
  2. ssh to the VM that you want to upgrade.
  3. Check that you are connected to a screen session. A screen session is needed for situations where network connectivity is less than favorable. You can check your screen session using the following command:
    # screen -ls
    This command returns an output such as the following example:
    There is a screen on:
    12081.upgrade(Detached)

    Log back into the SSH console and run the following command to reattach the screen session:
    screen -r 12081.upgrade
    OR
    screen -r upgrade
  4. Run the following command to download the upgrade installer:
    # wget https://repo.fortisoar.fortinet.com/7.2.0/upgrade-fortisoar-7.2.0.bin
    Note: If your instance can connect to "repo.fortisoar.fortinet.com" only by using a proxy, then ensure that the proxy is set in the /etc/wgetrc file. For example,
    use_proxy=yes
    http_proxy=<proxy_server_ip:port>
    https_proxy=<proxy_server_ip:port>
    You can also set the proxy while running the FortiSOAR Configuration Wizard or by using the csadm network command.
  5. Run the upgrade installer using the following command:
    # sh upgrade-fortisoar-7.2.0.bin
    OR
    # chmod +x upgrade-fortisoar-7.2.0.bin
    # ./upgrade-fortisoar-7.2.0.bin
    Notes: The FortiSOAR upgrade installer checks for the following:
    • The space available in /tmp or /var/temp (if exist in /etc/fstab), which must be at least 500MB. If the space available in /tmp or /var/temp is less than 500MB, then the upgrade installer exits after displaying an appropriate error message. If you want to skip this space validation check, you can use the --skip-tmp-validation option while running the upgrade script:
      # ./upgrade-fortisoar-7.2.0.bin --skip-tmp-validation
    • The disk space available in /boot, and if the /boot has insufficient space, then the upgrade installer exits after displaying an appropriate error message. Steps for cleaning up /boot are present in the Clean up /boot article present in the Fortinet Knowledge Base.
    • The disk space available in /var/lib/pgsql to ensure that you have sufficient disk space for pgsql. If you do not have sufficient disk space for pgsql, in this case also the upgrade installer exits. In these cases, you must increase the partition size for /var/lib/pgsql. For the procedure to increase the partition size, see the 'Issues occurring in FortiSOAR due to insufficient space' section in the Deployment Troubleshooting chapter in the "Deployment Guide" for more information.
    Once you complete cleaning up /boot and/or increasing disk space and space in /tmp (as per the messages provided by the upgrade installer) and you have sufficient space for upgrading FortiSOAR, you must re-run the upgrade installer to continue the process of upgrading FortiSOAR.
    Important: To upgrade a high availability cluster in FortiSOAR, you require to upgrade each node individually, one after the other. For more information, see the Upgrading a FortiSOAR High Availability Cluster section. For information on how to upgrade a FortiSOAR distributed multi-tenant configuration to 7.2.0, see the Upgrading a FortiSOAR Distributed Multi-Tenancy Configuration section.
    Note: When you upgrade your FortiSOAR enterprise instance, High Availability (HA) cluster, or a distributed multi-tenant configuration, the FortiSOAR appliance hostkey also gets changed.
  6. Once your FortiSOAR instance is upgraded, you must log out from the FortiSOAR UI and log back into FortiSOAR.