- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HA not synchronized
Hi, guys,
I am rather new to Fortigate devices, after a pair of Forti400e have formed HA structure, I found them not synchronized due to the following message:
login: slave's configuration is not in sync with master's, sequence:0 slave's external files are not in sync with master, sequence:1. (type APPDB) slave's external files are not in sync with master, sequence:3. (type CERT_CA) slave's external files are not in sync with master, sequence:4. (type CERT_CA) slave succeeded to sync external files with master slave's external files are not in sync with master, sequence:0. (type APPDB) slave's external files are not in sync with master, sequence:1. (type APPDB) slave's external files are not in sync with master, sequence:3. (type APN_CERT) slave's external files are not in sync with master, sequence:4. (type APN_CERT) slave succeeded to sync external files with master slave's external files are not in sync with master, sequence:0. (type APN_CERT) slave's external files are not in sync with master, sequence:1. (type APN_CERT) slave's external files are not in sync with master, sequence:2. (type APN_CERT) slave's external files are not in sync with master, sequence:3. (type APN_CERT) slave's external files are not in sync with master, sequence:4. (type APN_CERT) slave succeeded to sync external files with master
Any recommendation, thx a lot
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These messages are normal when initially you form a cluster, or after reloading a member.
Is it still looking NOT synced ??? (though GUI ? or cli).
Else you need to troubleshoot this.
The configuration seems syncing,,, and some external files might be the issue if still not synced.
check:
https://kb.fortinet.com/kb/documentLink.do?externalID=FD45183
https://kb.fortinet.com/kb/documentLink.do?externalID=FD36494
https://kb.fortinet.com/kb/documentLink.do?externalID=FD31379
else if it a fresh install,, try to
a. factory default the passive unit and after reboot configure only HA configuration on secondary. Nothing else.
Then try again to from HA.
--------------------------------------------
If all else fails, use the force !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These messages are normal when initially you form a cluster, or after reloading a member.
Is it still looking NOT synced ??? (though GUI ? or cli).
Else you need to troubleshoot this.
The configuration seems syncing,,, and some external files might be the issue if still not synced.
check:
https://kb.fortinet.com/kb/documentLink.do?externalID=FD45183
https://kb.fortinet.com/kb/documentLink.do?externalID=FD36494
https://kb.fortinet.com/kb/documentLink.do?externalID=FD31379
else if it a fresh install,, try to
a. factory default the passive unit and after reboot configure only HA configuration on secondary. Nothing else.
Then try again to from HA.
--------------------------------------------
If all else fails, use the force !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, jklapas
Thanks so much for your kind replied.
Finally, I found the issue from the event log...the slave became master after reboot.
Cheers
