Fortinet FortiGate-7000E Series System Manual page 46

Firmware upgrades
[I]: Set local IP address: The IP address of the MGMT interface of the selected FIM 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.
13. To quit this menu, press Q.
14. 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.
15. To start the TFTP transfer, press T.
The firmware image is uploaded from the TFTP server 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.
16. 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
17. 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=69346.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=387.74, priority=20, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20E3E17900217, Slave, uptime=387.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=69346.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=69346.99, priority=2, slot_id=1:2, idx=1, flag=0x0, in_sync=1
FPM20E3E17900217, Slave, uptime=387.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 FPM in slot 4 is lower than the uptime of the other
modules, indicating that the FPM in slot 4 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.
18. Once the FPM is operating normally, log back in to the primary FIM CLI and enter the following command to reset
the FPM to normal operation:
diagnose load-balance switch set-compatible <slot> disable
Configuration synchronization errors will occur if you do not reset the FPM to normal operation.
FortiGate-7060E 6.4.2 System Guide
in_sync=0 are not synchronized. To synchronize an FIM or FPM
https://support.fortinet.com
Fortinet Technologies Inc.
get system status command.
in_sync=1 indicates that
execute reboot command .
.
46