|
When the NP7 device upgrades from V7.2.8GA, V7.2.9GA, V7.2.10GA to V7.4.5GA, V7.4.6GA, V7.4.7GA in HA mode, an infinite reboot loop is encountered. This is observed on the secondary unit while the primary unit is stuck waiting for the secondary to restart.
The primary device appears to be waiting for the secondary to complete the reboot process. Hence, the upgrade process is halted.
The following console log is shown.
FGT4200F # Image verification OK!
Wait for HA to be primary of all clusters...
Send image to HA secondary.
.Wait for secondary to restart...................................
FortiGate-4200F (15:30-09.07.2024)
Ver:05000107
Serial number:FG420FTKxxxxxx01
RAM activation
On the secondary device, the following console log appears, where an infinite reboot is observed. Disrupting the boot process and loading the previous firmware version stops the infinite reboot loop.
FortiGate-4200F (15:30-09.07.2024)
Ver:05000107
Serial number:FG420FTKxxxxxx02
RAM activation
CPU(00:00050657 bfebfbff): MP initialization
CPU(01:00050657 bfebfbff): MP initialization
[...]
CPU('n':00050657 bfebfbff): MP initialization
Total RAM: 393200MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Boot up, boot device capacity: 28626MB.
Press any key to display configuration menu...
.............................
Verifying the integrity of system files.
Reading boot image 6107474 bytes.
Initializing firewall...
System is starting...
The config file may contain errors.
Please see details by the command 'diagnose debug config-error-log read'.
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system
FGT-4200F (15:30-09.07.2024)
Ver:05000107
Serial number:FG420FTKxxxxxx02
RAM activation
CPU(00:00050657 bfebfbff): MP initialization
CPU(01:00050657 bfebfbff): MP initialization
[...]
CPU('n':00050657 bfebfbff): MP initialization
Total RAM: 393200MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Boot up, boot device capacity: 28626MB.
Press any key to display configuration menu...
.............................
Verifying the integrity of system files.
Reading boot image 6107474 bytes.
Initializing firewall...
System is starting...
The config file may contain errors.
Please see details by the command 'diagnose debug config-error-log read'.
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system
FGT-4200F (15:30-09.07.2024)
Ver:05000107
Serial number:FG420FTKxxxxxx02
RAM activation
CPU(00:00050657 bfebfbff): MP initialization
CPU(01:00050657 bfebfbff): MP initialization
[...]
CPU('n':00050657 bfebfbff): MP initialization
Total RAM: 393200MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Boot up, boot device capacity: 28626MB.
Press any key to display configuration menu...
.....
[C]: Configure TFTP parameters.
[R]: Review TFTP parameters.
[T]: Initiate TFTP firmware transfer.
[F]: Format boot device.
[B]: Boot with backup firmware and set as default.
[I]: System configuration and information.
[Q]: Quit menu and continue to boot.
[H]: Display this list of options.
Enter C,R,T,F,B,I,Q,or H:
Loading backup firmware from boot device...
Verifying the integrity of system files.
Reading boot image 6071743 bytes.
Initializing firewall...
System is starting...
Starting system maintenance...
Scanning /dev/sda1... (0%)
Scanning /dev/sda1... (6%)
Scanning /dev/sda1... (18%)
Scanning /dev/sda1... (100%)
Scanning /dev/sda3... (0%)
Scanning /dev/sda3... (2%)
Scanning /dev/sda3... (5%)
Scanning /dev/sda3... (8%)
Scanning /dev/sda3... (11%)
Scanning /dev/sda3... (13%)
Scanning /dev/sda3... (16%)
Scanning /dev/sda3... (19%)
Scanning /dev/sda3... (100%)
Scanning /dev/sda3... (100%)
The config file may contain errors.
Please see details by the command 'diagnose debug config-error-log read'.
This is a known issue under engineering ID 1087263 and is resolved in v7.4.8 build 2750. Refer to the release notes: Resolved issues.
To workaround this issue, use one of the following methods:
Option 1: Break the HA cluster by setting the units to standalone mode and manually upgrading the devices separately: Technical Tip: Manual upgrade procedure of a FortiGate HA cluster, and then re-form the cluster: Technical Tip: Rebuilding an HA cluster after the upgrade.
Option 2: Perform the upgrade in two stages without breaking the cluster: first upgrade from v7.2.x → v7.2.10, and then upgrade from v7.2.10 → v7.4.8.
|
