Created on
07-19-2022
09:08 PM
Edited on
09-18-2025
12:50 AM
By
Debbie_FTNT
Description | This article describes the FortiGate license expired date incorrectly which happens on HA clusters. |
Scope | FortiGate. |
Solution |
Confirm both HA cluster unit's expiry dates.
Example:
Primary FortiGate expiry date: 10/10/2024 Secondary FortiGate expiry date: 10/10/2023
The FortiGate license will reflect the earliest expiry date among the cluster units. FortiGate GUI will show the expiry date as 10/10/2023.
In the CLI it should show as below when 'diagnose debug app update -1" executes for the expired license on the secondary unit:
upd_status_set_ha_expiry[1477]-Extracting contract...(SerialNumber=FG101E4Qxxxxxxxx|Contract=AVDB-1- -------------- update_status_obj[740]-SBCL contract expiry=Sat Dec 7 01:00:00 2024 level(6) alert(0) level(6) alert(0) update_status_obj[740]-SBCL contract expired=Sat Dec 7 01:00:00 2023 <<<<< Should see Expired
diagnose debug reset execute update-now
diagnose debug disable <----- Stop the logs after the update is successful.
FortiCloud portal verification: Login to support.fortinet.com and go to the Section Product -> My Assets.
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.