Before verifying normal operation and making configuration changes and so on you should wait until the FortiGate-6000 is completely started up and synchronized. This can take a few minutes.
To confirm that the FortiGate-7000E is synchronized, view the Security Fabric dashboard widget. If the system is synchronized, all of the FIMs and FPMs should be visible and FortiGate telemetry status should be Connected. The widget also indicates if any FPMs are not synchronized. You can also view the Sensor Information widget to confirm that the system temperatures are normal and that all power supplies and fans are operating normally.
The FortiGate-7000 uses the Fortinet Security Fabric for communication and synchronization between the FIMs and the FPMs and for normal GUI operation. By default, the Security Fabric is enabled and must remain enabled for normal operation.
From the CLI you can use the
diagnose sys confsync status | grep in_sy command to view the synchronization status of the FIMs and FPMs. If all of the FIMs and FPMs are synchronized, each output line should include
in_sync=1. If a line ends with
in_sync=0, that FIM or FPM is not synchronized. The following example just shows a few output lines:
diagnose sys confsync status | grep in_sy FIM10E3E16000062, Slave, uptime=53740.68, priority=2, slot_id=2:2, idx=3, flag=0x10, in_sync=1 FIM04E3E16000010, Slave, uptime=53790.94, priority=3, slot_id=1:1, idx=0, flag=0x10, in_sync=1 FIM04E3E16000014, Master, uptime=53781.29, priority=1, slot_id=2:1, idx=1, flag=0x10, in_sync=1 FIM10E3E16000040, Slave, uptime=53707.36, priority=4, slot_id=1:2, idx=2, flag=0x10, in_sync=1 FPM20E3E16900234, Slave, uptime=53790.98, priority=16, slot_id=2:3, idx=4, flag=0x64, in_sync=1 FPM20E3E16900269, Slave, uptime=53783.67, priority=17, slot_id=2:4, idx=5, flag=0x64, in_sync=1 FPM20E3E17900113, Slave, uptime=53783.78, priority=116, slot_id=1:3, idx=6, flag=0x64, in_sync=1 FPM20E3E17900217, Slave, uptime=53784.11, priority=117, slot_id=1:4, idx=7, flag=0x64, in_sync=1 ...