HA With Different Revision Hardware

So, I have run into some instances as of late where I was forced to use different revisions of the same hardware (two FortiGate’s that match model wise but are different hardware revisions, you know, cause Fortinet likes to evolve things half way through a lifecycle) in high available (HA) clusters. This is easily done with a few tweaks at the CLI level to enable it to properly function. I ignore 4.x version code because if you are still running that you are going to have a bad time in general.

execute ha ignore-hardware-revision enable
execute ha ignore-hardware-revision status

This will make the hardware work with ease in an HA cluster. Take note, you still need the same model, this just helps with variances in hardware revision between the two!

Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!

This entry was posted in FortiGate, How To on by .

About Mike

Michael Pruett, CISSP has a wide range of cyber-security and network engineering expertise. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. This site was started in an effort to spread information while providing the option of quality consulting services at a much lower price than Fortinet Professional Services. Owns PacketLlama.Com (Fortinet Hardware Sales) and Office Of The CISO, LLC (Cybersecurity consulting firm).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.