Confirming startup status

Before verifying normal operation and making configuration changes and so on you should wait until the FortiGate 6000F is completely started up and synchronized. This can take a few minutes.

To confirm that the FortiGate 6000F is synchronized, you can refer to the Cluster Status dashboard widget. If the system is synchronized, the management board (slot 0) all of the FPCs (slots 1 to 6 or 1 to 10) should be visible and their Configuration Status should be In Sync. The Cluster Status dashboard widget also indicates if any FPCs are not synchronized.

The FortiGate 6000F uses the Fortinet Security Fabric for communication and synchronization between the management board and the FPCs and for normal GUI operation. By default, the Security Fabric is enabled and must remain enabled for normal operation.

You can also view the Sensor Information dashboard widget to confirm that the system temperatures are normal and that all power supplies and fans are operating normally.

From the CLI you can use the diagnose sys confsync status | grep in_sy command to view the synchronization status of the management board and FPCs. If all of the FPCs are synchronized, each output line should include in_sync=1. If a line ends with in_sync=0, that FPC is not synchronized. The following example just shows a few output lines:

diagnose sys confsync status | grep in_sy
FPC6KF3E17900200, Secondary, uptime=5385.45, priority=119, slot_id=2:1, idx=2, flag=0x4, in_sync=1
F6KF313E17900031, Secondary, uptime=5484.74, priority=2, slot_id=1:0, idx=0, flag=0x10, in_sync=1
F6KF313E17900032, Primary, uptime=5488.57, priority=1, slot_id=2:0, idx=1, flag=0x10, in_sync=1
FPC6KF3E17900201, Secondary, uptime=5388.78, priority=120, slot_id=2:2, idx=2, flag=0x4, in_sync=1
F6KF313E17900031, Secondary, uptime=5484.74, priority=2, slot_id=1:0, idx=0, flag=0x10, in_sync=1
...