Synchronizing Fims And Fpms After Upgrading The Primary Fim Firmware From The Bios - Fortinet FortiGate-7000F Series System Manual

Firmware upgrades
To make corrections, press C and make the changes as required. When the configuration is correct proceed to the
next step.
18. To start the TFTP transfer, press T.
The firmware image is uploaded from the TFTP server of the FIM and installed on the FPM. The FPM then restarts
with its configuration reset to factory defaults. After restarting, the FPM configuration is synchronized to match the
configuration of the primary FPM. The FPM restarts again and can start processing traffic.
19. Once the FPM restarts, verify that the correct firmware is installed.
You can do this from the FPM GUI dashboard or from the FPM CLI using the get system status command.
20. Verify that the configuration has been synchronized.
The following command output shows example FortiGate-7000 sync status. The field in_sync=1 indicates that the
configurations of the FIMs and FPMs are synchronized.
diagnose sys confsync status | grep in_sy
FIM21FTB21000068, Secondary, uptime=210445.62, priority=2, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FIM21FTB21000063, Primary, uptime=351403.75, priority=1, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FPM20FTB20990039, Secondary, uptime=351253.83, priority=18, slot_id=1:5, idx=2, flag=0x64, in_sync=1
FPM20FTB20990047, Secondary, uptime=352.27, priority=16, slot_id=1:3, idx=3, flag=0x64, in_sync=1
FPM20FTB20990078, Secondary, uptime=227839.73, priority=17, slot_id=1:4, idx=4, flag=0x64, in_sync=1
FPM20FTB20990091, Secondary, uptime=351248.85, priority=22, slot_id=1:9, idx=5, flag=0x64, in_sync=1
FPM20FTB20990095, Secondary, uptime=351240.13, priority=20, slot_id=1:7, idx=6, flag=0x64, in_sync=1
FPM20FTB21900096, Secondary, uptime=351272.50, priority=24, slot_id=1:11, idx=7, flag=0x64, in_sync=1
FPM20FTB21900179, Secondary, uptime=351247.07, priority=19, slot_id=1:6, idx=8, flag=0x64, in_sync=1
FPM20FTB21900182, Secondary, uptime=351242.02, priority=25, slot_id=1:12, idx=9, flag=0x64, in_sync=1
FPM20FTB21900203, Secondary, uptime=351228.51, priority=21, slot_id=1:8, idx=10, flag=0x64, in_sync=1
FPM20FTB21900211, Secondary, uptime=351252.93, priority=23, slot_id=1:10, idx=11, flag=0x64, in_sync=1
FPM20FTB20990047, Secondary, uptime=351252.27, priority=16, slot_id=1:3, idx=2, flag=0x4, in_sync=1
FIM21FTB21000063, Primary, uptime=351403.75, priority=1, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Secondary, uptime=210445.62, priority=2, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FPM20FTB20990078, Secondary, uptime=227839.73, priority=17, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIMs and FPMs that are missing or that show in_sync=0 are not synchronized. To synchronize an FIM or FPM
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the execute reboot command . If
this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
The command output also shows that the uptime of the FPM in slot 3 is lower than the uptime of the other modules,
indicating that the FPM in slot 3 has recently restarted.
If you enter the diagnose sys confsync status | grep in_sy command before the FPM has restarted, it
will not appear in the command output. As well, the Configuration Sync Monitor will temporarily show that it is not
synchronized.
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. The in_sync=0 entries in the
following example output show that the management board (serial number ending in ) is not synchronized with the other
FIM and the FPMs shown in the example.
FortiGate-7081F 7.0.5 System Guide
Fortinet Technologies Inc.
46