Fortinet NSE5_FSW_AD-7.6: FortiLink Architecture
FortiLink is the management connection by which a FortiGate can discover, authorize and operate managed FortiSwitch devices. Treating it as an ordinary cable between two products misses the management, control and forwarding decisions that make a campus network reliable. The Fortinet NSE 5 – FortiSwitch 7.6 Administrator exam includes managed topologies, FortiLink provisioning, switch operation and troubleshooting. This guide focuses on how to reason about the design, not memorizing an arbitrary diagram.
On this page
Choose the management boundary first
Decide which FortiGate is responsible for which switches, what happens when the controlling device is unavailable, and how management traffic travels between them. Document whether switches are directly attached or reached through supported intermediate topology. A FortiLink interface is not simply a data VLAN; it carries a management relationship and may use dedicated or aggregate links depending on design. A valid topology must be verified against the exact FortiOS and FortiSwitchOS versions deployed.
Understand discovery and authorization
A switch that is physically connected is not necessarily an authorized managed device. FortiGate discovery, switch authorization, firmware compatibility, management-address allocation and configuration synchronization all affect onboarding. Design a repeatable process that confirms serial number, role and network location before applying switch templates. A common operational mistake is treating a discovery problem as a VLAN problem while the switch is not actually in the expected management mode.
Separate user traffic from management dependencies
Map the path that endpoint frames take, including VLAN tags, trunks, access ports, spanning tree behavior and uplinks. The data path can continue or degrade differently from the FortiLink management path. Avoid designing a topology that strands devices when an upstream trunk changes. Consider link aggregation, redundant FortiGate scenarios and device-specific features only when supported. Plan for configuration backups and a known recovery path if central policy cannot be pushed.
Validate the design with failure exercises
In an authorized lab, document a healthy baseline: authorized switch list, management reachability, FortiLink status, uplink negotiation, VLAN assignments and expected forwarding. Then simulate one problem at a time: missing authorization, mismatched uplink configuration or loss of a management link. Observe which symptoms belong to discovery, control or data forwarding. Rehearse the recovery procedure without making untracked production changes. The value is diagnostic separation, not command memorization.
Review governance and change control
Choose who owns switch templates, who can authorize new devices and how firmware upgrades are sequenced. Protect administrative credentials and restrict management-plane access. Evaluate how a new branch switch will be added and how an accidentally authorized device would be detected. A usable design review includes a topology, access model, test checklist and rollback. Fortinet documentation remains the authority for exact model combinations and CLI behavior, especially after software upgrades.