Fortinet Document Library

Version:

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 primary unit's central management interface by going into each device's dashboard page. You must upgrade the cluster in the following order:

  1. Worker (slave) devices
  2. Secondary (primary slave)
  3. Primary (master)

It is highly recommended to setup cluster level failover IP set so the failover between primary and secondary can occur smoothly. If the user does not want the failover to happen, the user can change the secondary unit role to worker. 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 primary unit's central management interface by going into each device's dashboard page. You must upgrade the cluster in the following order:

  1. Worker (slave) devices
  2. Secondary (primary slave)
  3. Primary (master)

It is highly recommended to setup cluster level failover IP set so the failover between primary and secondary can occur smoothly. If the user does not want the failover to happen, the user can change the secondary unit role to worker. 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.