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 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.
Set up a TFTP server and copy the firmware file to the TFTP server default folder.
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.
Using the console cable supplied with your FortiGate-7000, connect the management module Console 1 port on the FortiGate-7000 to the RS-232 port on your management computer.
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.
Press Ctrl-T to enter console switch mode.
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)>
Optionally log in to the FIM's CLI.
Reboot the FIM.
You can do this using the
execute rebootcommand from the CLI or by pressing the power switch on the FIM front panel.
When the FIM starts up, follow the boot process in the terminal session, and press any key when prompted to interrupt the boot process.
To set up the TFTP configuration, press C.
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
[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.
To quit this menu, press Q.
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.
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.
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
get system statuscommand.
Verify that the configuration has been synchronized.
The following command output shows the sync status of a FortiGate-7040E. The field
in_sync=1indicates that 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
in_sync=0are not synchronized. To synchronize an FIM or FPM that is not synchronized, log into the CLI of the FIM or FPM and restart it using the
execute rebootcommand. If this does not solve the problem, contact Fortinet Support at https://support.fortinet.com.
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_sycommand 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.