Installing FPM firmware from the BIOS after a reboot
Use the following procedure to upload firmware from a TFTP server to an FPM. To perform the upgrade, you must enter a command from the primary FIM CLI to allow the FPM BIOS to communicate through an FIM MGMT interface. The procedure involves creating a connection between the TFTP server and one of the FIM MGMT interfaces.
This procedure also involves connecting to the FPM CLI using a FortiGate-7000 front panel Management Module console port, rebooting the FPM, interrupting the boot from the console session, and following FPM BIOS prompts to install the firmware.
During this procedure, the FPM will not be able to process traffic. However, the other FPMs and the FIMs should continue to operate normally.
After you verify that the FPM is running the right firmware, you must log back in to the primary FIM CLI and return the FPM to normal operation.
Set up a TFTP server and copy the firmware file into the TFTP server default folder.
Log into to the primary FIM CLI and enter the following command:
diagnose load-balance switch set-compatible <slot> enable bios
<slot>is the number of the FortiGate-7000 slot containing the FPM to be upgraded.
Set up your network to allow traffic between the TFTP server and a MGMT interface of one of the FIMs.
You can use any MGMT interface of either of the FIMs. When you set up the FPM TFTP settings below, you select the FIM that can connect to the TFTP server. 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 module to be updated. Example prompt:
<Switching to Console: FPM03 (9600)>
Optionally log into the FPM's CLI.
Reboot the FPM.
You can do this using the
execute rebootcommand from the FPM's CLI or by pressing the power switch on the FPM front panel.
When the FPM 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:FIM01 (the FIM that can communicate with the TFTP server).
[D]: Set DHCP mode:Disabled.
[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
[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 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.
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
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=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
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 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_sycommand before the FPM 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.
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> disableConfiguration synchronization errors will occur if you do not reset the FPM to normal operation.