Confirming that FortiGate-6000 components are synchronized
In addition to viewing configuration synchronization status from the Configuration Sync Monitor, you can use the following command to confirm that the configurations of the management board and the FPCs are synchronized:
diagnose sys confsync status
The command shows the HA and configuration synchronization (confsync) status of the management board and all of the FPCs. For the management board and each FPC, in_sync=1 means the component is synchronized and can operate normally. If any component is out of sync, the command output will include in_sync=0. All components must be synchronized for the FortiGate-6000 to operate normally.
|
To confirm the configuration synchronization status of an HA cluster, see Confirming that the FortiGate-6000 HA cluster is synchronized . |
FPC confsync status
The diagnose sys confsync status command output begins with the confsync status for each FPC. In the following example for a FortiGate-6301F, the output begins with the confsync status if the FPC in slot 1. The two lines that begin with serial numbers and end with in_sync=1 indicate that the FPC (serial number FPC6KFT018903332) is synchronized with the management board (serial number F6KF31T019900078) and the management board is synchronized with the FPC.
diagnose sys confsync status
...
Slot: 1 Module SN: FPC6KFT018903332
ELBC: svcgrp_id=1, chassis=1, slot_id=1
ELBC HB devs:
elbc-ctrl/1: active=1, hb_count=10655
ELBC mgmt devs:
elbc-b-chassis: mgmtip_set=1
zone: self_idx:1, primary_idx:0, ha_primary_idx:255, members:2
FPC6KFT018903332, Secondary, uptime=10654.18, priority=19, slot_id=1:1, idx=1, flag=0x4, in_sync=1
F6KF31T019900078, Primary, uptime=10697.67, priority=1, slot_id=1:0, idx=0, flag=0x0, in_sync=1
elbc-b-chassis: state=3(connected), ip=169.254.2.15, last_hb_time=10880.47, hb_nr=51017
...
Management board confsync status
The diagnose sys confsync status command output ends with the confsync status of the management board, which shows the configuration status between the management board and each of FPCs:
...
MBD SN: F6KF31T019900078
ELBC: svcgrp_id=1, chassis=1, slot_id=0
zone: self_idx:0, primary_idx:0, ha_primary_idx:255, members:7
F6KF31T019900078, Primary, uptime=11355.27, priority=1, slot_id=1:0, idx=0, flag=0x0, in_sync=1
FPC6KFT018903307, Secondary, uptime=11309.71, priority=21, slot_id=1:3, idx=1, flag=0x24, in_sync=1
elbc-b-chassis: state=3(connected), ip=169.254.2.5, last_hb_time=11431.39, hb_nr=54184
FPC6KFT018903310, Secondary, uptime=11314.01, priority=23, slot_id=1:5, idx=2, flag=0x24, in_sync=1
elbc-b-chassis: state=3(connected), ip=169.254.2.7, last_hb_time=11431.43, hb_nr=54168
FPC6KFT018903327, Secondary, uptime=11313.17, priority=24, slot_id=1:6, idx=3, flag=0x24, in_sync=1
elbc-b-chassis: state=3(connected), ip=169.254.2.8, last_hb_time=11431.38, hb_nr=54175
FPC6KFT018903328, Secondary, uptime=11312.37, priority=22, slot_id=1:4, idx=4, flag=0x24, in_sync=1
elbc-b-chassis: state=3(connected), ip=169.254.2.6, last_hb_time=11431.36, hb_nr=54196
FPC6KFT018903332, Secondary, uptime=11312.10, 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=11431.38, hb_nr=54196
FPC6KFT018903333, Secondary, uptime=11313.94, 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=11431.38, hb_nr=54195