Fortinet Document Library

Version:

Version:


Table of Contents

FortiGate-7000F Handbook

Download PDF
Copy Link

Confirming startup status

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

To confirm that the FortiGate-7000F is synchronized, go to Monitor > Configuration Sync Monitor. If the system is synchronized, all the FIMs and FPMs should be visible, and their Configuration Status should be In Sync. The Configuration Sync Monitor also indicates if any of the FIMs or FPMs are not synchronized.

Caution

The FortiGate-7000F 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.

Changing the default Security Fabric configuration could disrupt communication and affect system performance.

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

Note

From the menu bar at the top of the GUI, you can click on the host name and pull down a list of the FIMs and FPMs in the FortiGate-7000F. From the list you can hover over each FIM or FPM to see the CPU and memory usage and session count of each, change the host name, or log into the GUI using the special management port number.

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
FIM21FTB21000063, Slave, uptime=79898.73, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FPM20FTB21900165, Slave, uptime=7252.99, priority=17, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20FTB21900186, Slave, uptime=79751.32, priority=16, slot_id=1:3, idx=3, flag=0x64, in_sync=1
FPM20FTB21900186, Slave, uptime=79751.32, priority=16, slot_id=1:3, idx=2, flag=0x4, in_sync=1
FIM21FTB21000063, Slave, uptime=79898.93, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FPM20FTB21900165, Slave, uptime=7252.99, priority=17, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM21FTB21000063, Slave, uptime=79898.93, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
...

Confirming startup status

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

To confirm that the FortiGate-7000F is synchronized, go to Monitor > Configuration Sync Monitor. If the system is synchronized, all the FIMs and FPMs should be visible, and their Configuration Status should be In Sync. The Configuration Sync Monitor also indicates if any of the FIMs or FPMs are not synchronized.

Caution

The FortiGate-7000F 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.

Changing the default Security Fabric configuration could disrupt communication and affect system performance.

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

Note

From the menu bar at the top of the GUI, you can click on the host name and pull down a list of the FIMs and FPMs in the FortiGate-7000F. From the list you can hover over each FIM or FPM to see the CPU and memory usage and session count of each, change the host name, or log into the GUI using the special management port number.

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
FIM21FTB21000063, Slave, uptime=79898.73, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FPM20FTB21900165, Slave, uptime=7252.99, priority=17, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20FTB21900186, Slave, uptime=79751.32, priority=16, slot_id=1:3, idx=3, flag=0x64, in_sync=1
FPM20FTB21900186, Slave, uptime=79751.32, priority=16, slot_id=1:3, idx=2, flag=0x4, in_sync=1
FIM21FTB21000063, Slave, uptime=79898.93, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
FPM20FTB21900165, Slave, uptime=7252.99, priority=17, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM21FTB21000063, Slave, uptime=79898.93, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=79887.77, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=1
...