Technical Tip: How to check all FPC s are in sync with Configuration SYNC Master in FortiGate-6000

[rmankotia]

Description

This article describes how to check all FPCs are in sync with Configuration SYNC Master in FortiGate-6000.

The FortiGate-6000 uses the Fortinet Security Fabric for communication and synchronization between the management board and the FPCs.

Scope

FortiGate.

Solution

From GUI.

Go to Monitor -> Configuration Sync Monitor.

From CLI.

F6KFXXXXXXXXXX15 (global) # get system status
Version: FortiGate-6301F v6.2.4,build8163,210903 (GA)
Virus-DB: 89.00290(2021-09-11 03:20)
Extended DB: 88.00298(2021-08-11 15:19)
Extreme DB: 1.00000(2018-04-09 18:07)
IPS-DB: 6.00741(2015-12-01 02:30)
IPS-ETDB: 18.00138(2021-08-11 21:27)
APP-DB: 18.00138(2021-08-11 21:27)
INDUSTRIAL-DB: 6.00741(2015-12-01 02:30)
Serial-Number: F6KFXXXXXXXXXX15
Module Serial-Number: F6KFXXXXXXXXXX15
IPS Malicious URL Database: 3.00128(2021-09-10 07:02)
Botnet DB: 4.00705(2021-08-05 17:09)
BIOS version: 05000012
Module BIOS version: 05000012
System Part-Number: P22354-03
Module Part-Number: P22354-03
Log hard disk: Available
Hostname: F6KFXXXXXXXXXX15
Operation Mode: NAT
Current virtual domain: mgmt-vdom
Max number of virtual domains: 10
Virtual domains status: 2 in NAT mode, 0 in TP mode
Virtual domain configuration: multiple
FIPS-CC mode: disable
Current HA mode: standalone
Config-Sync: Master
FPC Master: slot-1
Branch point: 1116
Release Version Information: GA
FortiOS x86-64: Yes
System time: Sat Sep 11 23:26:15 2021

F6KXXXXXXXXXX15 (global) # diagnose sys confsync status
ELBC: svcgrp_id=1, chassis=1, slot_id=0
zone: self_idx:0, master_idx:0, ha_master_idx:255, members:7
F6KFXXXXXXXXXX15, Master, uptime=536741.39, priority=1, slot_id=1:0, idx=0, flag=0x0, in_sync=1
FPC6KXXXXXXXXX85, Slave, uptime=536670.12, priority=23, slot_id=1:5, idx=1, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.7, last_hb_time=536829.92, hb_nr=2682696
FPC6KXXXXXXXXX88, Slave, uptime=536670.19, priority=21, slot_id=1:3, idx=2, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.5, last_hb_time=536829.98, hb_nr=2682681
FPC6KXXXXXXXXX96, Slave, uptime=536666.52, priority=22, slot_id=1:4, idx=3, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.6, last_hb_time=536829.94, hb_nr=2682636
FPC6KXXXXXXXXX67, Slave, uptime=536677.97, priority=24, slot_id=1:6, idx=4, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.8, last_hb_time=536830.10, hb_nr=2682664
FPC6KXXXXXXXXX68, Slave, uptime=536663.81, priority=19, slot_id=1:1, idx=5, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.3, last_hb_time=536829.94, hb_nr=2682631
FPC6KXXXXXXXXX76, Slave, uptime=536634.38, priority=20, slot_id=1:2, idx=6, flag=0x24, in_sync=1
        elbc-b-chassis: state=3(connected), ip=169.254.2.4, last_hb_time=536829.94, hb_nr=2682490

If all FPCs are synchronized with Master, it will show in_'sync=1'.
If any of the FPCs are not synchronized with Master, it will show in'_sync=0'.

To fix a confsync issue the following command could be used:

F6KFXXXXXXXXXX15(global) # diagnose sys confsync csum-recalculate