Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Upgrading or rebooting a Cluster

Upgrading or rebooting a Cluster has to be done by logging into each device or through the Master unit's central management interface by going into each device's dashboard page. You must upgrade the cluster in the following order:

  1. Slave devices
  2. Primary Slave
  3. Master

It is highly recommended to setup cluster level fail-over IP set so the fail-over between Master and Primary Slave can occur smoothly. If the user does not want the fail-over to happen, the user can change the Primary Slave unit role to Regular Slave. You can either do this through the UI dashboard or the CLI prior to the fail-over, then change the role back after the unit boots up.

Upgrading or rebooting a Cluster

Upgrading or rebooting a Cluster has to be done by logging into each device or through the Master unit's central management interface by going into each device's dashboard page. You must upgrade the cluster in the following order:

  1. Slave devices
  2. Primary Slave
  3. Master

It is highly recommended to setup cluster level fail-over IP set so the fail-over between Master and Primary Slave can occur smoothly. If the user does not want the fail-over to happen, the user can change the Primary Slave unit role to Regular Slave. You can either do this through the UI dashboard or the CLI prior to the fail-over, then change the role back after the unit boots up.