Skip to main content
louvrosa
Staff
louvrosa
Staff
January 26, 2026

Troubleshooting Tip: Entitlement status not replicated to secondary FortiManager

  • January 26, 2026
  • 0 replies
  • 139 views
Description This article describes the issue where entitlement status is not replicated to secondary FortiManager devices in a High Availability cluster. It explains the cause of the issue and provides a solution to ensure that entitlement files are synchronized across all cluster members.
Scope FortiManager.
Solution

Entitlement files are not synced across FortiManager High Availability cluster members by default. The FortiGuard module is configured on each cluster member separately, and the entitlement file needs to be uploaded to each device individually.

To resolve the issue of entitlement status not being replicated to secondary FortiManager devices, follow these steps:

  1. Make sure that each FortiManager device in the High Availability cluster has the entitlement file uploaded separately.
  2. Go to System -> FortiGuard -> Service Status and verify that the entitlement status is updated on each device. The command diagnose fmupdate dbcontract may also be used to review whether the entitlement file upload was successful, and the command diagnose fmupdate fds-dump subs to display all the entitlement information for the loaded entitlement file.

 

Note: Both CLI commands are available in FortiManager v7.0.4 GA, v7.2.1 GA, and above.

 

To upload the entitlement file through CLI:

 

execute fmupdate ftp import license <remote_file> <Server_IP> <remote_path> <username> <pass>
Terms & ConditionsAccessibility statement