FortiSwitch
FortiSwitch: secure, simple and scalable Ethernet solutions
agodbole
Staff
Staff
Article Id 403442
Description This article describes how to troubleshoot the FortiSwitch in the event of a network outage following an unexpected power cycle, causing a loss of configuration.
Scope FortiSwitch.
Solution

In some cases, the FortiSwitch may become unresponsive after an unexpected power cycle, resulting in a loss of configuration. This is due to the FortiSwitch booting from an undesired/inactive partition. 

 

Here are the steps to identify, troubleshoot, and resolve the issue

 

  1. FortiSwitch, like the FortiGate, has two boot partitions. To check this, run the following command:

 

diagnose sys flash list

 

Example output:

 

FS1E48T422003949 # diagnose sys flash list
Partition Image                                             TotalSize(KB)  Used(KB)  Use%  Active
1          FS1E48-7.02-FW-build0479-240214-patch07          55529           45385    81%   No
                                                            71395           1397      2%   No
(*) 2      FS1E48-7.00-FW-build0092-230126-patch06          55529           37248     67%  Yes
                                                            71391           1388       2%  Yes

Flag * : next-boot partition
Image build at Jan 26 2023 14:01:37 for b0092

 

In this output, the (*) indicates the active partition.

 

  1. If the switch has booted from a version other than the one it was on before the power cycle, it means that the switch has booted from the other partition. Hence, the loss of connectivity.

  2. To resolve this issue, boot the switch from the non-active partition. Here are the steps and commands for this process. 

 

  1. Disable image rotation on the FortiSwitch under the global settings.

 

config system global
    set image-rotation disable
end

 

  1. Set the next reboot partition to primary/secondary. It should be the inactive partition.

 

execute set-next-reboot <primary/secondary>

 

  1. Reboot the FortiSwitch. This will boot it from the other partition, which contains the latest configuration, and the connectivity will be restored after the reboot.

 

execute reboot

 

  1. Re-enable the image rotation to set it to the default value.

 

config system global
    set image-rotation enable
end

 

Use the following workaround to avoid this issue:

  1. Make sure that the FortiSwitch is on the correct partition and has all the configuration needed.
  2. Run the 'show system global' command to check the image-rotation configuration and ensure it's enabled. If 'set image-rotation disable' is set, then run unset or 'set image-rotation enable'.

 

config system global

    unset image-rotation

end

 

  1. Once it is confirmed that the image rotation is enabled, upgrade your FortiSwitches to the same firmware version. In our case above, upgrade the FortiSwitch to 7.0.6 build 0092, as it has an up-to-date configuration.

  2. Now, even in cases where the FortiSwitch boots from the incorrect partition, it should still have the updated configuration. There should not be any connectivity failures or network outages. The following is an example of how the flash list output should look:

 

FS1E48T419000449 # diagnose sys flash list
Partition Image                                    TotalSize(KB)  Used(KB) Use%     Active
(*) 1     FS1E48-7.00-FW-build0092-230126-patch06  55529          37248    67%      Yes
                                                   71395          1388      2%      Yes
2         FS1E48-7.00-FW-build0092-230126-patch06  55529          37248     67%     No
                                                   71391          1390        2%    No

 

Here, both the primary and the secondary partition are on 7.0.6 build 0092. 

Contributors