Description
Some FortiGate models have multiple versions of hardware. Typically, this means minor changes such as an increase in memory or a different disk drive vendor while retaining the same major platform name. These different versions are known as 'revision' levels (For example, FortiGate 5001B rev1, FortiGate 5001B rev2).
Also, when RAID is configured on one device but not on the other(s) it will result in a different hard disk status.
By default, when configuring high availability (HA), FortiGates with different revision levels and/or hard disk status will NOT be able to join together in a cluster.
The following commands will enable FortiGates with different revision hardware to form an HA cluster.
Expectations, Requirements
FortiGates are the same model but different hardware revision.
Solution
In FortiOS 4.3 and earlier:
# config system global
set ignore-hardware-revision enable
end
In FortiOS 5.0 and later:
# exec ha ignore-hardware-revision enable
# exec ha ignore-hardware-revision status
In FortiOS 5.4.0 and 5.4.1 this command is only available on FortiGate units that have had multiple hardware revisions. Also, there are some exceptions to certain models where this command is not feasible though there are different hardware generations, such as the FortiGate 1500D (However, it is compatible to form a cluster with 1500D Gen1 and 1500D Gen2 hardware revision models, and does not need the help of above commands). It should be noted that running the command 'exec ha ignore-hardware-revision enable' will cause a reboot of the firewall.For more information refer to the 'Troubleshooting HA clusters' section of the chapter 'High Availability' in the FortiOS Handbook.
Related links:
https://community.fortinet.com/t5/tkb/workflowpage/tkb-id/TKB20/article-id/943
https://community.fortinet.com/t5/FortiGate/Technical-Note-Configuring-RAID-for-supported-FortiGates...
