Study guide

1.3 Virtual Domains (VDOMs) & System Operation Modes

Fortinet FCP - FortiGate 7.6 Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the Fortinet FCP FortiGate Administrator Exam (FCP_FGT_AD-7.6) How to Study and Prepare for FortiOS 7.6 Certification

2 Chapter 1: Deployment & System Configuration

1.1 Initial Configuration, GUI/CLI Management & Admin Profiles 1.2 FortiGuard Services, Licensing & Firmware Upgrades 1.3 Virtual Domains (VDOMs) & System Operation Modes 1.4 Fortinet Security Fabric & Device Integration 1.5 High Availability (FGCP) Configuration & Election 1.6 System Logging, Diagnostics & Troubleshooting Tools 1.7 FortiGate CNF, FortiGate VM in Public Cloud & FortiSASE Administration

3 Chapter 2: Firewall Policies & NAT

2.1 Firewall Policy Matching & Object Management 2.2 Source Network Address Translation (SNAT) & IP Pools 2.3 Destination NAT (DNAT), Virtual IPs (VIPs) & Central NAT

4 Chapter 3: Content Inspection & Security Profiles

3.1 Flow-Based vs Proxy-Based Inspection Modes 3.2 Antivirus & FortiSandbox Integration 3.3 Intrusion Prevention System (IPS) Configuration 3.4 Web Filtering & Static URL Management 3.5 Application Control & Traffic Shaping 3.6 DNS Filtering & Botnet C&C Protection

5 Chapter 4: Authentication & FSSO

4.1 Local & Remote Authentication (LDAP, RADIUS, 2FA) 4.2 Fortinet Single Sign-On (FSSO) Architecture & Modes

6 Chapter 5: Routing & SD-WAN

5.1 Static Routing, Policy Routes & Reverse Path Forwarding 5.2 SD-WAN Architecture, Performance SLAs & Balancing Rules

7 Chapter 6: SSL VPN & IPsec VPN

6.1 SSL VPN Web Mode & Tunnel Mode Configuration 6.2 IPsec VPN Phase 1 & Phase 2 Fundamentals 6.3 Advanced IPsec Topologies (Hub-and-Spoke & ADVPN)

8 Chapter 7: SSL/SSH Inspection

7.1 SSL Certificate Inspection vs Deep SSL/SSH Inspection 7.2 CA Certificates, Port Handling & Inspection Exemptions

1.3 Virtual Domains (VDOMs) & System Operation Modes

Key Takeaways Explain This Topic AI

Virtual Domains (VDOMs) logically partition a single physical FortiGate into multiple independent virtual firewalls, each maintaining distinct interfaces, routing tables, and security policies.

FortiOS supports two primary operational modes: NAT/Route Mode (Layer 3 routing and stateful NAT) and Transparent Mode (Layer 2 bridge without IP addressing on traffic interfaces).

Enabling VDOMs creates a Management VDOM (default: mgmt-vdom or root) dedicated to global management traffic, while user traffic is segregated into operational VDOMs.

System configuration is divided into Global Context (hardware, firmware, global FortiGuard) and VDOM Context (routing tables, firewall rules, security profiles).

Inter-VDOM Links (vdom-link) provide internal, software- or NPU-accelerated virtual interfaces connecting two VDOMs without requiring physical external cabling.

Last updated: July 2026

Virtual Domains (VDOMs) & System Operation Modes

FortiOS Virtual Domains (VDOMs) enable network administrators to partition a single physical FortiGate hardware appliance or virtual machine into multiple logically independent security firewalls. Each VDOM functions as a completely autonomous unit, maintaining its own dedicated network interfaces, routing tables, security policies, VPN tunnels, and administrative access profiles.

Virtual Domain (VDOM) Fundamentals & Multi-Tenancy

VDOM architecture brings multi-tenancy to network security infrastructure. It allows Managed Security Service Providers (MSSPs) and enterprise organizations to isolate departments (e.g., HR, Finance, Engineering) or customer tenants on shared hardware while maintaining strict administrative and traffic separation.

Key VDOM Capabilities

Independent Resource Allocation : Interfaces, VLAN subinterfaces, and IPsec tunnels are assigned to specific VDOMs.

Routing Table Segregation : Each VDOM runs isolated routing daemons (BGP, OSPF, static routes). overlapping IP address spaces across different VDOMs are fully supported.

Granular Security Policies : Firewall policies and Security Profiles (AV, IPS, Web Filter) are authored independently per VDOM.

Role-Based Administration : Administrators can be granted full control over a single VDOM without exposing global platform settings.

VDOM Modes: Split-Task vs. Multi-VDOM

FortiOS 7.6 supports two administrative VDOM operational topologies:

Split-Task VDOM Mode : Segregates the system into exactly two VDOMs:

mgmt-vdom : Dedicated exclusively to administrative management traffic, FortiGuard updates, FortiAnalyzer logging, and DNS queries.

root : Dedicated exclusively to customer data traffic forwarding and security policy enforcement.

Multi-VDOM Mode : Enables full multi-tenancy, permitting administrators to create multiple custom VDOMs (up to physical platform or license limits) alongside global system management.

Enabling Multi-VDOM Mode via CLI

Enabling multi-VDOM mode alters global system configuration structures. Executing the mode change forces an administrative session logout. config system global

  • set vdom-mode multi-vdom
  • end
  • Global Context vs. VDOM Context

When VDOMs are enabled, the CLI environment splits into two operating contexts: Global Context and VDOM Context .

CLI Navigation and Privileges # Enter Global Context (System-wide hardware, global objects, physical interface assignment)

  • config global
  • config system interface
  • edit "port3"
  • set vdom "Accounting-VDOM"
  • next
  • end
  • end
  • # Enter specific VDOM Context (VDOM-specific routing, policies, security profiles)
  • config vdom
  • edit "Accounting-VDOM"
  • config router static
  • edit 1
  • set gateway 10.200.1.1
  • set device "port3"
  • next
  • end
  • end
  • Operational Parameter Configured in Global Context Configured in VDOM Context
  • Firmware Upgrades & License Yes No
  • Physical Interface Assignment Yes No
  • FortiGuard Server Settings Yes No
  • High Availability (HA) Parameters Yes No
  • Firewall Policies & NAT Rules No Yes
  • Routing Protocols (BGP/OSPF/Static) No Yes
  • Security Profiles (AV, IPS, Web) No Yes
  • IPsec / SSL VPN Configuration No Yes
  • System Operation Modes: NAT/Route Mode vs. Transparent Mode

Each VDOM (or a non-VDOM FortiGate) operates in one of two fundamental network layer modes: NAT/Route Mode or Transparent Mode .

1. NAT/Route Mode (Layer 3)

In NAT/Route Mode (the default operational mode), the FortiGate functions as a Layer 3 network router. Interfaces are assigned IP addresses across distinct IP subnets. The FortiGate routes traffic between interfaces based on its routing table while performing Network Address Translation (NAT) and stateful packet inspection.

2. Transparent Mode (Layer 2)

In Transparent Mode , the FortiGate functions as a Layer 2 bridge or transparent switch. Physical interfaces do not have IP addresses assigned. The FortiGate forwards packets transparently between network segments based on MAC address tables while continuing to enforce Layer 4 firewall policies and Layer 7 Security Profile inspection.

Transparent Mode Management Setup

To manage a Transparent Mode VDOM, a dedicated Management IP address ( manageip ) and default gateway are assigned to the system settings node: config system settings

  • set opmode transparent
  • set manageip 192.168.1.99 255.255.255.0
  • set gateway 192.168.1.1
  • end

Important

In Transparent Mode, all interfaces assigned to the VDOM belong to the same broadcast domain by default. To prevent broadcast loops, administrators must configure Virtual Virtual Local Area Networks (VLANs) or forward domains ( set forward-domain ).

Inter-VDOM Links (vdom-link)

When multiple VDOMs exist on a single FortiGate, traffic transferring between VDOMs normally requires exiting a physical interface, traversing an external switch, and re-entering another physical interface. Inter-VDOM Links (vdom-link) eliminate physical cabling by creating a pair of connected virtual network interfaces inside the FortiOS kernel.

Hardware Acceleration & Interface Types

NPU-Accelerated vdom-link : Processed directly by Network Processor (NPU) ASIC chips (e.g., NP6, NP7), delivering line-rate throughput with minimal CPU overhead.

Software vdom-link : Processed by the general CPU daemon; used when NPU acceleration is unavailable.

  • Inter-VDOM Link CLI Configuration # Step 1: Create the virtual inter-VDOM link pair in Global Context
  • config global
  • config system vdom-link
  • edit "vlink-corp-to-dmz"
  • next
  • end
  • # Assign interface endpoints to target VDOMs
  • config system interface
  • edit "vlink-corp-to-dmz0"
  • set vdom "Corporate-VDOM"
  • set ip 172.16.1.1 255.255.255.252
  • set allowaccess ping
  • next
  • edit "vlink-corp-to-dmz1"
  • set vdom "DMZ-VDOM"
  • set ip 172.16.1.2 255.255.255.252
  • set allowaccess ping
  • next
  • end
  • end

Once the endpoints are assigned, administrators create static routes and firewall policies in both VDOMs, referencing the respective vlink interfaces to permit secure inter-VDOM traffic flow.

NAT/Route Mode vs. Transparent Mode Architectural Matrix

  • Feature / Property NAT / Route Mode (Layer 3) Transparent Mode (Layer 2)
  • Network Layer Operation Layer 3 Router Layer 2 Bridge / Switch
  • Interface IP Addressing Mandatory (IP assigned per interface) Prohibited (Interfaces have no IPs)
  • Management Access Via Interface Allowed Access IPs Dedicated Management IP ( manageip )
  • NAT Support (SNAT/DNAT) Full Support Not Supported (Packets maintain IPs)
  • Routing Protocols BGP, OSPF, RIP, Static Routes Not Supported
  • Stateful Packet Inspection Supported (L4 - L7 Security Profiles) Supported (L4 - L7 Security Profiles)
  • Network Topology Change Requires Subnet & Gateway Changes Zero Topology Change (Drop-in placement)

Loading diagram... Multi-VDOM Infrastructure with Inter-VDOM Link Routing