Technical Tip: Standalone FortiSwitch password and static route config loss after reboot

After the FortiSwitch reboot, only the password and static route configuration are lost. As a result, need to re-configure them post-reboot.

Collect the output of 'diagnose sys config-debug' and check if any header is missing.

Note: The command is available on FortiSwitch models 2xx and above.

For example, in the below output, the header '#' is missing.

No header: (There should be a header # before 'config system'):

19xxx31_16xx_57x/./sys_vd_root.conf.gz
------------------------------
00000000 63 6f 6e 56 59 57 10 63 69 63 74 65 6d 20 73 65 |config system se|
00000010 74 74 69 6e 67 73 0a 65 6e 64 0a 63 6f 6e 66 69 |ttings.end.confi|

Should have a header like this ('#config-version=' etc...):

196xxxx1_16xx_5x2/./sys_global.conf.gz
------------------------------
00000000 23 63 6f 4e 66 59 27 2d 46 55 72 73 69 6f 6e 3d |#config-version=|

Missing header causes a parse failure, and the system fails back to the default configuration, as the config is considered corrupted.

Solution: Upgrade FortiSwitch to version 7.4.7/7.6.2 and above to fix the following bug:

• 1091216 - After a random power outage caused the FortiSwitch unit to restart, the switch configuration is lost.

Release notes:

• FortiSwitch 7.4.7 release notes
• FortiSwitch 7.6.2 release notes

If the issue is still seen, take console access to the FortiSwitch (make sure console session is logged) - reboot the FortiSwitch - open a support ticket and attach the console log along with the following outputs from the FortiSwitch:

diag debug report

show full-config

diagnose sys config-debug

Related articles:

Technical Tip: Standalone FortiSwitch returning to previously set configuration or default configuration after reboot

Technical Tip: Standalone FortiSwitch default configuration to avoid loosing VLAN configs

Troubleshooting Tip: Internal interface native VLAN changes after switch reboot