Description
This article describes how to fix a Standalone FortiSwitch returning to a previously set configuration or default configuration after a reboot.
Scope
FortiSwitch
Solution
Possible cause of the issue.
When 'cfg-save' under system global is changed from 'automatic' to 'manual or revert' as shown below, the new config changes made on a Standalone FortiSwitch will not be saved automatically.
# config system global
set cfg-save <manual/revert>
By default, 'cfg-save' is set to 'automatic' - all changes are added to the saved configuration as created.
Whereas, when 'cfg-save' is set to 'manual' mode - the config commands take effect but do not become part of the saved configuration unless the # execute cfg save command is used.
When the system restarts, the saved configuration is loaded.
Configuration changes that were not saved are lost.
Therefore, to save the configuration automatically every time by the FortiSwitch, execute config commands by entering either 'next' or 'end', to make the below changes on the FortiSwitch and then save the changes:
# config system global
set cfg-save automatic
end
# execute cfg save
Note:
'# execute cfg save' is applicable only for Standalone FortiSwitch, because in a FortiLink Managed Switch – the config is automatically saved on FortiGate.
Related link:
Page# 58: https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/a7c76c1d-754c-11ea-9384-005056...
Page#171, 176, 304: https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/e3f61090-754c-11ea-9384-005056...
