Installing Fim Firmware From The Bios After A Reboot - Fortinet FortiGate-7000E Series System Manual

Firmware upgrades
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 FIM has
completely restarted, it will not appear in the command output. As well, the Configuration Sync Monitor will
temporarily show that it is not synchronized.
5. 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.
Installing FIM firmware from the BIOS after a reboot
Use the following procedure to upload firmware from a TFTP server to an FIM. The procedure involves creating a
connection between the TFTP server and one of the FIM MGMT interfaces. You don't have to use a MGMT interface on
the FIM that you are upgrading.
This procedure also involves connecting to the FIM CLI using a FortiGate-7000 front panel System Management
Module console port. From the console session, the procedure describes how to restart the FIM, interrupting the boot
process, and follow FIM BIOS prompts to install the firmware.
During this procedure, the FIM will not be able to process traffic. However, the other FIM and the FPMs should continue
to operate normally.
1. Set up a TFTP server and copy the firmware file to the TFTP server default folder.
2. Set up your network to allow traffic between the TFTP server and one of the FIM MGMT interfaces.
If the MGMT interface you are using is one of the MGMT interfaces connected as a LAG to a switch, you must
shutdown or disconnect all of the other interfaces that are part of the LAG from the switch. This includes MGMT
interfaces from both FIMs.
3. Using the console cable supplied with your FortiGate-7000, connect the SMM Console 1 port on the FortiGate-
7000 to the USB port on your management computer.
4. Start a terminal emulation program on the management computer. Use these settings:
Baud Rate (bps) 9600, Data bits 8, Parity None, Stop bits 1, and Flow Control None.
5. Press Ctrl-T to enter console switch mode.
6. Repeat pressing Ctrl-T until you have connected to the FIM to be updated. Example prompt for the FIM in slot 2:
<Switching to Console: FIM02 (9600)>
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.
execute reboot command.
.
43