Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Administration Guide

    Home FortiSandbox 3.1.0 Administration Guide
    3.1.0
    5.0.0
    4.4.6
    4.4.5
    4.4.4
    4.4.3
    4.4.2
    4.4.1
    4.4.0
    4.2.7
    4.2.6
    4.2.5
    4.2.4
    4.2.3
    4.2.2
    4.2.1
    4.2.0
    4.0.5
    4.0.4
    4.0.3
    4.0.2
    4.0.1
    4.0.0
    3.2.4
    3.2.3
    3.2.2
    3.2.1
    3.2.0
    3.1.5
    3.1.4
    3.1.3
    3.1.2
    3.1.1
    3.1.0
    3.0.7
    3.0.6

    Upgrading or rebooting a Cluster

    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.

    Previous
    Next

    Upgrading or rebooting a Cluster

    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.

    Previous
    Next