Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1
ORIGINAL: zack I had suspected AV/IPS definition updates were causing the error. Mine are set to update hourly though and i really don' t want to change to a more infrequent update schedule. As an FYI I did what Fortinet recommended by breaking and recreating the firewall cluster. No change or improvement as i still get the error daily. I got it after upgrading to 4.2.6 and still get it with 4.2.9. Kind of annoying. Since I had suspected this was an error generated by av/ips updates AND those updates always appear to be in sync when I check - i have taken to ignoring he error. I wish they would fix it though... Based on the amount of equipment in your signature TopJimmy I place weight on your thoughts as confirming my opinion. Thanks for the info.What' s worked for me was essentially what Bob posted above. Break the HA cluster, disconnect the slave completely. Wipe it and reload the same version firmware that the master has using the TFTP process (never had one of those fail but I don' t have any 320' s). When that is done, I boot it into the OS, and plug an ethernet cable from my PC (laptop) into the internal interface (depends on unit), make sure HTTPS for web management is on via the console and then I upload the current config from the master (after editing the system name and HA priority). Then reboot it again (watching from console cable) and check to see if it comes back up without any errors. If it looks good, I power it down, re-cable it back into the cluster (mine is full mesh) and power it back on. It will join the cluster and sync. This process works for me every time. I' ve only had to do a few times in 5 years due to the sync process failing and not correcting itself but I' ve had to do a few other times for adding new slaves into the cluster or replacing bad hardware. I' ve got it down where the whole process, if I have my ducks in a row, is done in less than 15 minutes. This assumes you have physical access to the cluster. I' ve had to travel to do this once or twice but I do it because I want to assure it' s done right.
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 |
---|---|
1692 | |
1087 | |
752 | |
446 | |
228 |
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 2024 Fortinet, Inc. All Rights Reserved.