Study guide
1.5 High Availability (FGCP) Configuration & Election
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.5 High Availability (FGCP) Configuration & Election
Key Takeaways Explain This Topic AI
FortiGate Clustering Protocol (FGCP) forms High Availability clusters, utilizing virtual MAC (vMAC) addresses (00-09-0f-09-xx-xx) to ensure transparent traffic failover without requiring upstream ARP updates.
Active-Passive (A-P) HA mode provides complete redundancy with a single active primary node processing all traffic, while Active-Active (A-A) offloads UTM security inspection to secondary cluster nodes.
FGCP primary master election follows a strict sequential decision hierarchy: Monitored Interfaces > HA Uptime (300s window) > Configured Priority > Hardware Serial Number.
When override is disabled (default), HA Uptime takes precedence over Priority, preventing unnecessary cluster failback re-elections when a recovered node rejoin the cluster.
Enabling session-pickup synchronizes established TCP connection state tables across cluster nodes, preventing active user session termination during an HA failover event.
Last updated: July 2026
High Availability (FGCP) Configuration & Election
Enterprise security architecture demands high availability and seamless hardware fault tolerance. The FortiGate Clustering Protocol (FGCP) is a proprietary clustering solution that groups two or more identical FortiGate appliances into a single logical High Availability (HA) cluster. FGCP guarantees sub-second failover, continuous stateful security inspection, and link failure recovery.
FGCP Operational Modes: Active-Passive vs. Active-Active
FGCP supports two primary cluster operational topologies:
1. Active-Passive (A-P) Mode
In an Active-Passive (A-P) cluster, one unit is elected as the Primary (Master) node, while all remaining units act as Secondary (Slave / Standby) nodes.
Traffic Handling : The Primary unit processes 100% of data traffic, routing, NAT, and security profile content inspection.
State Synchronization : The Primary unit continuously synchronizes firewall session state tables, IPsec VPN structures, DHCP leases, and routing tables to Secondary units across dedicated heartbeat links.
Failover Behavior : If the Primary unit suffers a hardware, power, or link failure, a Secondary unit immediately assumes the Primary role with zero loss of active network sessions (when session-pickup is enabled).
2. Active-Active (A-A) Mode
In an Active-Active (A-A) cluster, all members actively process data traffic.
Traffic Handling : The elected Primary unit continues to receive all incoming traffic, process Layer 3/4 routing, and manage NAT state tables. However, the Primary offloads resource-intensive Layer 7 Security Profile inspection (Antivirus, Web Filtering, IPS) for selected connections to Secondary units.
Operational Caveat : Active-Active mode introduces processing overhead for connection distribution and does not increase overall Layer 3 packet routing capacity beyond that of a single node.
Virtual MAC (vMAC) Address Architecture
To ensure seamless network failover without requiring adjacent routers or switches to update their ARP tables, FGCP automatically assigns Virtual MAC (vMAC) addresses to all cluster interfaces.
- vMAC Address Format
- 00-09-0f-09-xx-yy
00-09-0f : Fortinet Organizational Unique Identifier (OUI).
09 : Standard FGCP vMAC identifier.
xx : Cluster Group ID in hexadecimal (e.g., Group ID 10 = 0a ).
yy : Interface ID number in hexadecimal.
When a failover occurs, the secondary unit assuming the Primary role takes over ownership of the identical vMAC addresses. Surrounding network infrastructure continues transmitting frames to the same MAC destination, completely eliminating ARP cache convergence delays.
FGCP Primary Master Election Algorithm Hierarchy
When a cluster initializes or a topology change occurs, FGCP executes a strict sequential decision algorithm to select the Primary master node. The evaluation proceeds through four criteria in exact order: [1. Monitored Interfaces] --> [2. HA Uptime (300s)] --> [3. HA Priority] --> [4. Serial Number]
Step-by-Step Election Decision Criteria
Monitored Interfaces : The FortiGate unit with the highest number of operational monitored interfaces wins the election. If an interface configured under set monitor experiences a link down event, the node loses points and fails over.
HA Uptime : If monitored interface counts are equal, FGCP compares continuous cluster uptime. A node whose uptime is at least 300 seconds (5 minutes) greater than competing nodes wins the election. (This 300-second buffer prevents flap failovers).
HA Priority : If uptime differences are within the 300-second window (or if override is enabled), the unit with the higher configured priority value (range: 1–255; default: 128) wins.
Serial Number : If priority values are identical, the unit with the alphabetically higher serial number wins as a final tie-breaker.
Important
By default, the override setting is disabled ( set override disable ). When override is disabled, HA Uptime takes precedence over Priority. If a failed Primary node reboots and rejoins the cluster, it will NOT reclaim the Primary role even if it has a higher priority, preventing unnecessary traffic interruptions. If set override enable is configured, Priority overrides Uptime, forcing instant preemptive failback.
High Availability CLI Configuration & Session Pickup
Configuring FGCP requires matching group names, identical firmware builds, and assigned heartbeat interfaces on both units.
- Primary Node CLI Setup config system ha
- set group-id 10
- set group-name "HQ-HA-CLUSTER"
- set mode a-p
set password EncryptedHAPassword123!
- set hbdev "port5" 50 "port6" 50
- set override disable
- set priority 200
- set monitor "port1" "port2"
- set session-pickup enable
- set session-pickup-delay disable
- end
- Critical HA Parameters Explained
hbdev : Specifies dedicated physical heartbeat interfaces and their link priorities. At least two physical heartbeat links should be configured for redundancy to prevent split-brain conditions.
monitor : Designates critical data interfaces (e.g., WAN and LAN). If a monitored link fails, FGCP triggers an automatic cluster failover.
session-pickup : Enables real-time synchronization of non-sessionless TCP session tables across the heartbeat link. If disabled, active TCP connections drop during failover and clients must re-establish sessions.
session-pickup-delay : When disabled, forces immediate synchronization of all sessions, including short-lived connections.
FGCP Primary Master Election Algorithm Decision Matrix
Election Step Criterion Evaluated Winning Parameter Value Operational Notes & Impact of Override Setting
Step 1 Monitored Interfaces Highest Operational Link Count Monitored link failures immediately trigger failover regardless of priority settings.
Step 2 HA Uptime Uptime > 300 seconds greater Evaluated BEFORE Priority when override is disabled (default). Prevents failback flapping.
Step 3 HA Priority Higher Numeric Value (1-255) Evaluated BEFORE Uptime ONLY when set override enable is explicitly configured.
Step 4 Serial Number Alphabetically Higher String Deterministic tie-breaker when all prior criteria are completely identical.