Synchronizing FIMs and FPMs after upgrading the primary FIM firmware from the BIOS

After you install firmware on the primary FIM from the BIOS after a reboot, the firmware version and configuration of the primary FIM will most likely be not be synchronized with the other FIMs and FPMs. You can verify this from the primary FIM CLI using the diagnose sys confsync status | grep in_sy command.

diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Secondary, uptime=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=0
FIM04E3E16000010, Primary, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Secondary, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=0
FIM04E3E16000010, Primary, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
...

You can also verify synchronization status from the primary FIM Cluster Status dashboard widget.

To re-synchronize the FortiGate 7000E, which has the effect of resetting the other FIM and the FPMs, re-install firmware on the primary FIM.

You can also manually install firmware on each individual FIM and FPM from the BIOS after a reboot. This manual process is just as effective as installing the firmware for a second time on the primary FIM to trigger synchronization to the FIM and the FPMs, but takes much longer.

1. Log into the primary FIM GUI.

2. Install a firmware build on the primary FIM from the GUI or CLI. The firmware build you install on the primary FIM can either be the same firmware build or a different one.

   Installing firmware synchronizes the firmware build and configuration from the primary FIM to the other FIM and the FPMs.

3. Check the synchronization status from the Cluster Status dashboard widget or using the diagnose sys confsync status | grep in_sy command.