Troubleshooting Tip: FortiSwitch Unresponsive After Upgrade

[dwivedis]

Description	This article outlines steps to troubleshoot scenarios where a FortiSwitch becomes unresponsive, its configuration stops working, or the network goes completely down after an upgrade.
Scope	FortiSwitch.
Solution	In some cases, a FortiSwitch may stop functioning correctly or configurations may not behave as expected following an upgrade. This can potentially bring down the entire network. To resolve the issue, the switch can be rebooted from the secondary partition. By default, FortiSwitch has two partitions: primary and secondary. Verify the partitions by running the following command: diagnose sys flash list  Partition  Image                                     TotalSize(KB)  Used(KB)  Use%  Active  (*) 1      S148FF-7.6.0-FW-build1015-240812                  26624     20812   78%  Yes                                                                3072       232    8%  Yes  2          S148FF-7.4.4-FW-build0861-241004                  26624     19782   74%  No                                                                3072       232    8%  No  Flag * : next-boot partition  Image build at Aug 12 2024 10:55:31 for b1015  In this output, there are two partitions (1 and 2). The (*) symbol indicates the current active partition. If the switch is not operating as expected after the upgrade, follow the steps below to reboot from the alternate partition: Steps to Reboot FortiSwitch from the Secondary Partition: Disable Image Rotation: Image rotation is enabled by default. Disable it using the following commands: config system global      set image-rotation <enable | disable>  end  Set the Next Reboot Partition: Use the following command to set the partition for the next reboot: execute set-next-reboot <primary | secondary>  Reboot the Switch: execute reboot  This will reboot the switch from the specified partition, helping recover it from the unresponsive state.