Fortinet Document Library

Version:

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 failover IP set so the failover between master and primary slave can occur smoothly. If you do not want the failover to happen, you 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 failover, 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 failover IP set so the failover between master and primary slave can occur smoothly. If you do not want the failover to happen, you 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 failover, then change the role back after the unit boots up.