Fortinet Document Library

Version:

Version:


Table of Contents

Download PDF
Copy Link

Upgrading a FortiSOAR High Availability Cluster

This section describes the procedure to upgrade a FortiSOAR High Availability (HA) cluster. This section considers that the HA setup has a Reverse Proxy or Load Balancer such as "HAProxy" configured.

Tooltip

Refer to the Preparing to Upgrade FortiSOAR section and ensure that all the prerequisites mentioned in that section are met. The upgrade installer will handle all FortiSOAR services management.

Upgrading an Active-Active HA Cluster

For the purpose of the following procedure, Node1 is considered as the Active Primary node, Node2 is considered as the Active Secondary node. Both the nodes are fronted by a Reverse Proxy or Load Balancer such as "HAProxy".

Note

Approximately 30 minutes of downtime is required for the upgrade.

To upgrade your active-active HA cluster to FortiSOAR 6.4.4, perform the following steps:

  1. Configure the Reverse Proxy to pass requests only to Node1.
    This ensures that FortiSOAR requests are passed only to Node1, and Node2 can be upgraded.
  2. Use the #csadm ha command as a root user and run the leave-cluster command on Node2.
    This makes Node2 a standalone system.
  3. Upgrade Node2 using upgrade-fortisoar-x.x.x.bin.
    Once the upgrade of Node2 is completed successfully, you can now upgrade Node1.
    Important: Upgrade of Node1 will incur downtime.
  4. Once both the nodes are upgraded then run the join-cluster command from Node2.
  5. Configure the Reverse Proxy again to handle requests from both Node1 and Node2.

Upgrading an Active-Passive HA Cluster

For the purpose of the following procedure, Node1 is considered as the Active Primary node, Node2 is considered as the Passive Secondary node. Both the nodes are fronted by a Reverse Proxy or Load Balancer such as "HAProxy".

Note

Approximately 30 minutes of downtime is required for the upgrade.

To upgrade your active-passive HA cluster to FortiSOAR 6.4.4, perform the following steps:

  1. Reverse Proxy is configured to have Node2 as backup system. Therefore, you require to comment out that part from Reverse Proxy configuration.
  2. Use the #csadm ha command as a root user and run the leave-cluster command on Node2.
    This makes Node2 a standalone system.
  3. Upgrade Node2 using upgrade-fortisoar-x.x.x.bin.
    Once the upgrade of Node2 is completed successfully, you can now upgrade Node1.
    Important: Upgrade of Node1 will incur downtime.
  4. Once both the nodes are upgraded then run the join-cluster command from Node2.
  5. Configure the Reverse Proxy again to set Node2 as the backup server.

Upgrading a FortiSOAR High Availability Cluster

This section describes the procedure to upgrade a FortiSOAR High Availability (HA) cluster. This section considers that the HA setup has a Reverse Proxy or Load Balancer such as "HAProxy" configured.

Tooltip

Refer to the Preparing to Upgrade FortiSOAR section and ensure that all the prerequisites mentioned in that section are met. The upgrade installer will handle all FortiSOAR services management.

Upgrading an Active-Active HA Cluster

For the purpose of the following procedure, Node1 is considered as the Active Primary node, Node2 is considered as the Active Secondary node. Both the nodes are fronted by a Reverse Proxy or Load Balancer such as "HAProxy".

Note

Approximately 30 minutes of downtime is required for the upgrade.

To upgrade your active-active HA cluster to FortiSOAR 6.4.4, perform the following steps:

  1. Configure the Reverse Proxy to pass requests only to Node1.
    This ensures that FortiSOAR requests are passed only to Node1, and Node2 can be upgraded.
  2. Use the #csadm ha command as a root user and run the leave-cluster command on Node2.
    This makes Node2 a standalone system.
  3. Upgrade Node2 using upgrade-fortisoar-x.x.x.bin.
    Once the upgrade of Node2 is completed successfully, you can now upgrade Node1.
    Important: Upgrade of Node1 will incur downtime.
  4. Once both the nodes are upgraded then run the join-cluster command from Node2.
  5. Configure the Reverse Proxy again to handle requests from both Node1 and Node2.

Upgrading an Active-Passive HA Cluster

For the purpose of the following procedure, Node1 is considered as the Active Primary node, Node2 is considered as the Passive Secondary node. Both the nodes are fronted by a Reverse Proxy or Load Balancer such as "HAProxy".

Note

Approximately 30 minutes of downtime is required for the upgrade.

To upgrade your active-passive HA cluster to FortiSOAR 6.4.4, perform the following steps:

  1. Reverse Proxy is configured to have Node2 as backup system. Therefore, you require to comment out that part from Reverse Proxy configuration.
  2. Use the #csadm ha command as a root user and run the leave-cluster command on Node2.
    This makes Node2 a standalone system.
  3. Upgrade Node2 using upgrade-fortisoar-x.x.x.bin.
    Once the upgrade of Node2 is completed successfully, you can now upgrade Node1.
    Important: Upgrade of Node1 will incur downtime.
  4. Once both the nodes are upgraded then run the join-cluster command from Node2.
  5. Configure the Reverse Proxy again to set Node2 as the backup server.