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

    • CLI Reference

    Home FortiWeb 6.3.17 CLI Reference
    6.3.17
    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.10
    7.2.9
    7.2.8
    7.2.7
    7.2.6
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.0.9
    7.0.8
    7.0.7
    7.0.6
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.4.3
    6.4.2
    6.4.1
    6.4.0
    6.3.23
    6.3.19
    6.3.18
    6.3.17
    6.3.16
    6.3.15
    6.3.14
    6.3.13
    6.3.11
    6.3.10
    6.3.9
    6.3.7
    6.3.6
    6.3.5
    6.3.4
    6.3.3
    6.3.2
    6.3.1
    6.3.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.2
    6.1.1
    5.7.0
    5.6.1
    5.6.0

    ha synchronize

    ha synchronize

    Use this command to manually control the synchronization of configuration files and FortiGuard service-related packages from the active HA appliance to the standby appliance.

    Typically, most HA synchronization happens automatically, whenever changes are made. However, in some cases, you may want to use this command to manually initiate full or partial HA synchronization, including to

    • Delay synchronization to a more convenient time if you are planning to make large batch changes, and therefore delayed synchronization is preferable for network performance reasons
    • Manually force synchronization of files that are not automatically synchronized
    • Trigger automatic synchronization if it has been interrupted due to HA link failure, daemon crashes, etc.

    To use this command, your administrator account’s access control profile must have either w or rw permission to the sysgrp area. For details, see Permissions.

    Syntax

    execute ha synchronize {all | avupd | cli | geodb | sys}

    Variable Description Default

    synchronize {all | avupd | cli | geodb | sys}

    Select which part of the configuration and/or FortiGuard service-related packages to synchronize.

    • all—Entire configuration, including CLI configuration, system files, and signature databases.

    • avupd—Only the FortiGuard Antivirus service package, including the virus signatures, scan engine, and proxy.

    • cli—Only the core CLI configuration file (fwb_system.conf). You can use the show command to view the contents of the configuration file.

    • geodb—Only the geography-to-IP address mappings. Similar to firmware, these can be downloaded from the Fortinet Customer Service & Support website:

      https://support.fortinet.com

    • sys—Only the IP Reputation Database (IRDB) and system files such as X.509 certificates.

    Note: This command has no effect if you use the command execute ha synchronize stop to pause it manually.

    		 No default.

    Example

    This example shows how to manually synchronize the virus signature and engine package to the standby appliance.

    FortiWeb # execute ha synchronize avupd

    starting synchronize with HA master...

    Related topics

    Previous
    Next

    ha synchronize

    ha synchronize

    Use this command to manually control the synchronization of configuration files and FortiGuard service-related packages from the active HA appliance to the standby appliance.

    Typically, most HA synchronization happens automatically, whenever changes are made. However, in some cases, you may want to use this command to manually initiate full or partial HA synchronization, including to

    • Delay synchronization to a more convenient time if you are planning to make large batch changes, and therefore delayed synchronization is preferable for network performance reasons
    • Manually force synchronization of files that are not automatically synchronized
    • Trigger automatic synchronization if it has been interrupted due to HA link failure, daemon crashes, etc.

    To use this command, your administrator account’s access control profile must have either w or rw permission to the sysgrp area. For details, see Permissions.

    Syntax

    execute ha synchronize {all | avupd | cli | geodb | sys}

    Variable Description Default

    synchronize {all | avupd | cli | geodb | sys}

    Select which part of the configuration and/or FortiGuard service-related packages to synchronize.

    • all—Entire configuration, including CLI configuration, system files, and signature databases.

    • avupd—Only the FortiGuard Antivirus service package, including the virus signatures, scan engine, and proxy.

    • cli—Only the core CLI configuration file (fwb_system.conf). You can use the show command to view the contents of the configuration file.

    • geodb—Only the geography-to-IP address mappings. Similar to firmware, these can be downloaded from the Fortinet Customer Service & Support website:

      https://support.fortinet.com

    • sys—Only the IP Reputation Database (IRDB) and system files such as X.509 certificates.

    Note: This command has no effect if you use the command execute ha synchronize stop to pause it manually.

    		 No default.

    Example

    This example shows how to manually synchronize the virus signature and engine package to the standby appliance.

    FortiWeb # execute ha synchronize avupd

    starting synchronize with HA master...

    Related topics

    Previous
    Next