Firmware upgrades
Fortinet Technologies Inc.
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.
Synchronizing FIMs and FPMs after upgrading the primary FIM
firmware from the BIOS
After you install firmware on the primary FIM from the BIOS after a reboot, the firmware version and configuration of the
primary FIM will most likely be not be synchronized with the other FIMs and FPMs. You can verify this from the primary
FIM CLI using the
diagnose sys confsync status | grep in_sy
command. The
in_sync=0
entries in the
following example output show that the management board (serial number ending in 68) is not synchronized with the
other FIM and the FPMs shown in the example.
FortiCarrier-7000F [FIM01] (global) # diagnose sys confsync status | grep in_sy
FIM21FTB21000063, Slave, uptime=327.36, priority=2, slot_id=1:2, idx=0, flag=0x0, in_sync=1
FIM21FTB21000068, Master, uptime=327729.56, priority=1, slot_id=1:1, idx=1, flag=0x0, in_sync=0
FPM20FTB21900165, Slave, uptime=327578.35, priority=17, slot_id=1:4, idx=2, flag=0x64, in_sync=1
FPM20FTB21900168, Slave, uptime=327527.53, priority=24, slot_id=1:11, idx=3, flag=0x64, in_sync=0
FPM20FTB21900170, Slave, uptime=327520.91, priority=18, slot_id=1:5, idx=4, flag=0x64, in_sync=1
FPM20FTB21900179, Slave, uptime=327556.85, priority=19, slot_id=1:6, idx=5, flag=0x64, in_sync=1
FPM20FTB21900182, Slave, uptime=327579.41, priority=25, slot_id=1:12, idx=6, flag=0x64, in_sync=1
FPM20FTB21900186, Slave, uptime=327559.41, priority=16, slot_id=1:3, idx=7, flag=0x64, in_sync=1
FPM20FTB21900189, Slave, uptime=327591.45, priority=22, slot_id=1:9, idx=8, flag=0x64, in_sync=1
...
You can also verify synchronization status from the primary FIM Configuration Sync Monitor.
To re-synchronize the FortiGate-7000F, which has the effect of resetting the other FIM and the FPMs, re-install firmware
on the primary FIM.
You can also manually install firmware on each individual FIM and FPM from the BIOS after a
reboot. This manual process is just as effective as installing the firmware for a second time on
the primary FIM to trigger synchronization to the FIM and the FPMs, but takes much longer.
1.
Log into the primary FIM GUI.
2.
Install a firmware build on the primary FIM from the GUI or CLI. The firmware build you install on the primary FIM
can either be the same firmware build or a different one.
Installing firmware synchronizes the firmware build and configuration from the primary FIM to the other FIM and the
FPMs.
3.
Check the synchronization status from the Configuration Sync Monitor or using the
diagnose sys confsync
status | grep in_sy
command.
FortiGate-7121F System Guide
43
