Fortinet FortiGate-7000E Series System Manual page 38

Firmware upgrades
9. When the FIM starts up, follow the boot process in the terminal session, and press any key when prompted to
interrupt the boot process.
10. To set up the TFTP configuration, press C.
11. Use the BIOS menu to set the following. Change settings only if required.
[P]: Set image download port: MGMT1 (the connected MGMT interface.)
[D]: Set DHCP mode: Disabled
[I]: Set local IP address: The IP address of the MGMT interface that you want to use to connect to the
TFTP server. This address must not be the same as the FortiGate-7000 management IP address and cannot
conflict with other addresses on your network.
[S]: Set local Subnet Mask : Set as required for your network.
[G]: Set local gateway : Set as required for your network.
[V]: Local VLAN ID : Should be set to <none> . (use -1 to set the Local VLAN ID to <none> .)
[T]: Set remote TFTP server IP address : The IP address of the TFTP server.
[F]: Set firmware image file name : The name of the firmware image file that you want to install.
12. To quit this menu, press Q.
13. To review the configuration, press R.
To make corrections, press C and make the changes as required. When the configuration is correct, proceed to the
next step.
14. To start the TFTP transfer, press T.
The firmware image is uploaded from the TFTP server and installed on the FIM. The FIM then restarts with its
configuration reset to factory defaults. After restarting, the FIM configuration is synchronized to match the
configuration of the primary FIM. The FIM restarts again and can start processing traffic.
15. Once the FIM restarts, verify that the correct firmware is installed.
You can do this from the FIM GUI dashboard or from the FPM CLI using the
16. Verify that the configuration has been synchronized.
The following command output shows the sync status of a FortiGate-7040E. The field
the configurations of the FIMs and FPMs are synchronized.
diagnose sys confsync status | grep in_sy
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x4, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FIM04E3E16000010, Master, uptime=69398.91, priority=1, slot_id=1:1, idx=0, flag=0x0, in_sync=1
FIM10E3E16000040, Slave, uptime=346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=69387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FIMs and FPMs that are missing or that show
that is not synchronized, log into the CLI of the FIM or FPM and restart it using the
If this does not solve the problem, contact Fortinet Support at
The command output also shows that the uptime of the FIM in slot 2 is lower than the uptime of the other modules,
indicating that the FIM in slot 2 has recently restarted.
If you enter the diagnose sys confsync status | grep in_sy command before the FIM has
restarted, it will not appear in the command output. As well, the Security Fabric dashboard widget will temporarily
show that it is not synchronized.
FortiGate-7040E System Guide
in_sync=0 are not synchronized. To synchronize an FIM or FPM
https://support.fortinet.com
get system status command.
in_sync=1 indicates that
execute reboot command.
.
Fortinet Technologies Inc.
38