Fortinet NSE5_FSW_AD-7.6: FortiSwitch VLAN Design
FortiSwitch VLAN design decides which devices share a Layer 2 broadcast domain, where traffic must be routed and which policy enforces access. The operational cost of a VLAN mistake is often larger than a single configuration error: it can connect users to the wrong security zone or break DHCP, voice and management services. FortiGate-managed and standalone FortiSwitch deployments have different configuration paths, but the fundamental design questions remain the same. The current Fortinet FortiSwitch 7.6 exam is a useful official version reference.
On this page
Define zones by trust and operational need
Build a short traffic matrix for corporate devices, guests, voice, management and infrastructure services. For each network identify its business owner, addressing, DHCP source, gateway, required destinations and disallowed destinations. A VLAN number is not a security control by itself: routing and firewall rules must enforce the boundary. Resist defining a new VLAN for every departmental label if it creates unnecessary complexity without changing access requirements.
Understand access and trunk port intent
Endpoint-facing ports normally place untagged traffic into the intended network, while uplinks and devices that carry several networks require deliberate tagged memberships. Keep a documented list of allowed VLANs on inter-switch and FortiGate-facing links. Native VLAN assumptions and inconsistent tagging can create intermittent outages or accidental bridging. The correct implementation is product- and software-specific; examine the running configuration and traffic path rather than relying on generic examples from another switch vendor.
Plan gateways, DHCP and name resolution
Decide where inter-VLAN routing lives and which firewall policies apply when traffic crosses networks. Trace a new device obtaining an address and reaching DNS, authentication, update and business services. A device with link-state up but no connectivity may be using the wrong VLAN, gateway or security policy. Include redundancy for critical uplinks and gateways, and document the expected impact if a managed FortiLink connection or switch stack member becomes unavailable.
Reduce broadcast, loop and policy risk
Keep spanning tree and other loop-protection behavior aligned with the real topology. Avoid unreviewed bridging between guest and corporate networks. Inspect how endpoint discovery, multicast, printers or voice signaling cross segments; some services need specific gateways or relay configuration. Changes to trunk membership can affect multiple VLANs at once, so require staged review and a rollback path. Check that port templates do not silently reintroduce default access.
Test an end-to-end VLAN change
For a new office network, verify port assignment, tag propagation, gateway reachability, correct address assignment, firewall enforcement and expected application access. Test negative cases: a guest device must not reach a management subnet. Use packet captures or supported interface diagnostics when traffic stops, and compare the observed tag on each hop. Save the intended and observed network matrix with the change record so the next operator can distinguish configuration intent from accident.