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 FortiManager 7.4.1 Administration Guide
    7.4.1
    7.6.1
    7.6.0
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.8
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.13
    7.0.12
    7.0.11
    7.0.10
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.15
    6.4.14
    6.4.13
    6.4.12
    6.4.11
    6.4.10
    6.4.9
    6.4.8
    6.4.7
    6.4.6
    6.4.5
    6.4.4
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.2.13
    6.2.12
    6.2.11
    6.2.10
    6.2.9
    6.2.8
    6.2.7
    6.2.6
    6.2.6
    6.2.5
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.0.12
    6.0.11
    6.0.10
    6.0.9
    6.0.8
    6.0.7
    6.0.6
    6.0.5
    6.0.4
    6.0.3
    6.0.2
    6.0.1
    6.0.0
    5.6.11
    5.6.10
    5.6.9
    5.6.8
    5.6.7
    5.6.6
    5.6.5
    5.6.4
    5.6.3
    5.6.2
    5.6.1
    5.6.0
    5.4.7
    5.4.6
    5.4.5
    5.4.4
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.2.10
    5.2.7
    5.2.6
    5.2.4
    5.2.3
    5.2.2
    5.2.1
    5.2.0
    5.0.12
    5.0.11
    5.0.10
    5.0.9
    5.0.8
    5.0.7
    5.0.6
    5.0.5
    5.0.4
    5.0.3
    5.0.2
    4.3.8
    4.3.7
    4.3.6
    4.3.5
    4.3.4
    4.3.3
    4.3.2
    4.3.1
    4.3.0
    4.2.9
    4.2.8
    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.1.0
    4.0.3
    4.0.2
    4.0.1
    4.0.0

    ADOM versions

    ADOM versions

    Each ADOM is associated with a specific firmware version, based on the firmware version of the devices that are in that ADOM. This version is selected when creating a new ADOM. See Creating ADOMs.

    ADOM version N can manage devices with firmware version N. For example, ADOM version 6.4 can manage devices with firmware version 6.4.

    When upgrading firmware for managed devices, ADOM version N can tolerate to manage devices with firmware version N+1. This is sometimes called mixed mode or migration mode. For example, ADOM version 7.0 can manage devices with firmware 7.0 and 7.2. This allows you to continue to manage an ADOM as normal while upgrading the devices within that ADOM. Generally, you should upgrade the ADOM version from N to N+1 after all of the devices within the ADOM have been updated to firmware version N+1.

    Tooltip

    You can upgrade some ADOM versions without first updating all FortiGates in the ADOM. For more information, see Using mixed versions in ADOMs.

    When adding a new FortiGate unit to an ADOM, the FortiGate unit should have the same FortiOS version as the ADOM.

    You can use this feature to facilitate upgrading managed devices to new firmware. It is not recommended to permanently leave the ADOM with devices that contain a mix of firmware versions because of restrictions.

    For example, you cannot use features from the higher firmware version, such as templates that reference syntax from the higher version. You also cannot import policies from devices that are running higher firmware versions than the ADOM version.

    However installation to devices running higher firmware versions is supported.

    For a complete list of supported devices and firmware versions, see the FortiManager Release Notes.

    The general steps for upgrading an ADOM containing multiple devices running FortiOS 7.0 from 7.0 to 7.2 are as follows:

    1. In the ADOM, upgrade one of the FortiGate units to FortiOS 7.2, and then resynchronize the device.

      All of the ADOM objects, including Policy Packages, remain as 7.0 objects.

    2. Upgrade the rest of the FortiGate units in the ADOM to FortiOS 7.2.
    3. Upgrade the ADOM to 7.2. See Upgrading an ADOM for more information.

      All of the database objects will be converted to 7.2 format, and the GUI content for the ADOM will change to reflect 7.2 features and behavior.

    Previous
    Next

    ADOM versions

    ADOM versions

    Each ADOM is associated with a specific firmware version, based on the firmware version of the devices that are in that ADOM. This version is selected when creating a new ADOM. See Creating ADOMs.

    ADOM version N can manage devices with firmware version N. For example, ADOM version 6.4 can manage devices with firmware version 6.4.

    When upgrading firmware for managed devices, ADOM version N can tolerate to manage devices with firmware version N+1. This is sometimes called mixed mode or migration mode. For example, ADOM version 7.0 can manage devices with firmware 7.0 and 7.2. This allows you to continue to manage an ADOM as normal while upgrading the devices within that ADOM. Generally, you should upgrade the ADOM version from N to N+1 after all of the devices within the ADOM have been updated to firmware version N+1.

    Tooltip

    You can upgrade some ADOM versions without first updating all FortiGates in the ADOM. For more information, see Using mixed versions in ADOMs.

    When adding a new FortiGate unit to an ADOM, the FortiGate unit should have the same FortiOS version as the ADOM.

    You can use this feature to facilitate upgrading managed devices to new firmware. It is not recommended to permanently leave the ADOM with devices that contain a mix of firmware versions because of restrictions.

    For example, you cannot use features from the higher firmware version, such as templates that reference syntax from the higher version. You also cannot import policies from devices that are running higher firmware versions than the ADOM version.

    However installation to devices running higher firmware versions is supported.

    For a complete list of supported devices and firmware versions, see the FortiManager Release Notes.

    The general steps for upgrading an ADOM containing multiple devices running FortiOS 7.0 from 7.0 to 7.2 are as follows:

    1. In the ADOM, upgrade one of the FortiGate units to FortiOS 7.2, and then resynchronize the device.

      All of the ADOM objects, including Policy Packages, remain as 7.0 objects.

    2. Upgrade the rest of the FortiGate units in the ADOM to FortiOS 7.2.
    3. Upgrade the ADOM to 7.2. See Upgrading an ADOM for more information.

      All of the database objects will be converted to 7.2 format, and the GUI content for the ADOM will change to reflect 7.2 features and behavior.

    Previous
    Next