diag sys ha reset-uptime
FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C
config sys ha set override enable end
FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C
Triggering a failover depends upon how you have configured the failover in first place. Assuming that you have the default setup. The selection is done in a sequence:
Failed Monitored interfaces > Age >Device Priority > Serial number
There are following ways to trigger the failover:
1. Resetting one of the monitored interface on the primary unit. (Unplugging the cable or administratively shutdown the interface)
2. Resetting the age of the primary unit (diagnose sys ha reset-uptime)
3. Changing the device priority (this will not trigger the failover, you still need to trigger the failover afterwards)
4. Using diagnose sys ha set-as-master enable command on an unit will make it the primary unit until it is rebooted. (Not a recommended method & not supported by all models!)
Cheers,
Prab
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1747 | |
1114 | |
760 | |
447 | |
241 |
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.