What happens if FortiSwitch fails to discover either FortiEdge Cloud or a FortiGate with FortiLink?

A factory-default FortiSwitch unit first attempts to discover a managing FortiGate for FortiLink mode or connect to FortiEdge Cloud for zero-touch provisioning. If the switch is unable to find either of these management platforms on the network, it will not be able to enter a centrally managed mode. Consequently, the switch defaults to and remains in its standalone, or local management, mode. This allows an administrator to access the switch directly through its command-line interface (CLI) or graphical user interface (GUI) for manual configuration and troubleshooting.

A. The switch cannot enter FortiLink mode without first successfully discovering and being authorized by a managing FortiGate. A discovery failure prevents this.

C. Manual reimaging is a recovery or upgrade procedure and is not the standard operational response to a failed management discovery.

D. Auto-network is a port configuration feature, not the fundamental management mode of the switch. A discovery failure affects the management mode, not this specific feature.

1. Fortinet FortiSwitch Manager 7.6.0 Administration Guide, Page 13, Section: "FortiSwitch deployment". The guide states, "By default, a new or factory-reset FortiSwitch unit is in standalone mode." This confirms that if the subsequent discovery process for FortiLink fails, it remains in this default state.

2. Fortinet FortiSwitch OS 7.6.0 Administration Guide, Page 10, Section: "Introduction". This document outlines the two primary management methods: "As a standalone switch, where you configure and manage the switch individually" or "Managed by a FortiGate unit". This establishes that standalone (local management) is the alternative to FortiLink management.