What can an administrator do to maintain the existing standalone FortlSwltch configuration while changing the management mode to FortLink?

When a FortiSwitch operating in standalone mode is converted to FortiLink mode, the managing FortiGate will overwrite the switch's existing configuration upon authorization. To preserve the standalone configuration, an administrator must use the fortiswitch-standalone-to-fortilink-config-converter tool. This official Python-based script reads a backup of the standalone FortiSwitch configuration and converts it into a series of FortiGate CLI commands. The administrator can then execute this script on the FortiGate to replicate the original VLANs, policies, and port settings within the FortiGate's switch controller, effectively migrating the configuration.

B. Enabling the FortiLink setting on the FortiSwitch is a necessary step for connection but does not prevent the configuration from being wiped by the FortiGate.

C. The FortiGate does not automatically save or convert the existing FortiSwitch configuration. The default behavior is to overwrite it with the FortiGate's switch-controller configuration.

D. Registering and backing up to FortiSwitch Cloud saves the configuration in a standalone format, which is not compatible with the FortiGate's switch controller. It does not perform the necessary conversion.

1. Fortinet Cookbook, "Migrating a standalone FortiSwitch to a FortiGate-managed FortiSwitch," Document Version 1.0.0. This document explicitly details the migration challenge and solution. It states, "When a standalone FortiSwitch is connected to a FortiGate, the FortiGate will wipe the configuration of the FortiSwitch... To migrate the configuration from a standalone FortiSwitch to a FortiGate-managed FortiSwitch, you can use a Python script to convert the standalone configuration to a FortiGate configuration."

2. Fortinet Developer Network (FNDN), GitHub Repository: fortinet-solutions-cse/fortiswitch-standalone-to-fortilink-config-converter. This is the official repository for the migration tool. The README file describes its purpose: "This tool converts a standalone FortiSwitch configuration to a set of FortiGate CLI commands that can be used to configure the FortiSwitch from the FortiGate."

3. FortiSwitch—Managed by FortiOS 7.6.0, Administration Guide, Page 21, "Connecting the FortiSwitch unit to the FortiGate unit." The guide describes the authorization process where the FortiGate takes control. It states, "After the FortiSwitch unit is authorized, the FortiGate unit will be able to manage the FortiSwitch unit," which implies the FortiGate's configuration takes precedence, overwriting the local one.