Fortinet Document Library

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Check HA sync status

The HA sync status can be viewed in the GUI through either a widget on the Dashboard or on the System > HA page. It can also be confirmed through the CLI. When a cluster is out of sync, administrators should correct the issue as soon as possible as it affects the configuration integrity and can cause issues to occur.

HA sync status in the GUI

  • Dashboard widget:
    • Following HA setup, the HA Status widget can be added to the Dashboard. The widget shows the HA sync status by displaying a green checkmark next to each member in sync. A red mark indicates the member is out of sync.
  • System > HA page:
    • The same set of icons will be displayed on the System > HA page to indicate if the member is in sync.

HA sync status in the CLI

In the CLI, run the get system ha status command to see if the cluster is in sync. The sync status is reported under Configuration Status. In the following example, both members are in sync:

# get system ha status
HA Health Status: OK
Model: FortiGate-VM64
Mode: HA A-P
Group: 0
Debug: 0
Cluster Uptime: 0 days 0:29:2
Cluster state change time: 2020-09-25 08:23:09
Primary selected using:
    <2020/09/25 08:23:09> FGVME000000JUG0E is selected as the primary because it has the largest value of override priority.
    <2020/09/25 08:23:09> FGVMEV00000M6S87 is selected as the primary because it's the only member in the cluster.
ses_pickup: disable
override: disable
Configuration Status:
    FGVME000000JUG0E(updated 2 seconds ago): in-sync
    FGVMEV00000M6S87(updated 4 seconds ago): in-sync
System Usage stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        sessions=11, average-cpu-user/nice/system/idle=1%/0%/1%/98%, memory=69%
    FGVMEV00000M6S87(updated 4 seconds ago):
        sessions=1, average-cpu-user/nice/system/idle=0%/0%/1%/99%, memory=69%
HBDEV stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=60578029/155605/0/0, tx=13360110/25218/0/0
    FGVMEV00000M6S87(updated 4 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=7006310/19328/0/0, tx=6220835/13974/0/0
MONDEV stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=60578029/155605/0/0, tx=13360110/25218/0/0
        port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=70459776/175970/0/0, tx=36854/226/0/0
    FGVMEV00000M6S87(updated 4 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=7006310/19328/0/0, tx=6220835/13974/0/0
        port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=7197677/20580/0/0, tx=29200/83/0/0
Primary     : HA1             , FGVME000000JUG0E, HA cluster index = 0
Secondary   : HA2             , FGVMEV00000M6S87, HA cluster index = 1
number of vcluster: 1
vcluster 1: work 169.254.0.1
Primary: FGVME000000JUG0E, HA operating index = 0
Secondary: FGVMEV00000M6S87, HA operating index = 1 

Check HA sync status

The HA sync status can be viewed in the GUI through either a widget on the Dashboard or on the System > HA page. It can also be confirmed through the CLI. When a cluster is out of sync, administrators should correct the issue as soon as possible as it affects the configuration integrity and can cause issues to occur.

HA sync status in the GUI

  • Dashboard widget:
    • Following HA setup, the HA Status widget can be added to the Dashboard. The widget shows the HA sync status by displaying a green checkmark next to each member in sync. A red mark indicates the member is out of sync.
  • System > HA page:
    • The same set of icons will be displayed on the System > HA page to indicate if the member is in sync.

HA sync status in the CLI

In the CLI, run the get system ha status command to see if the cluster is in sync. The sync status is reported under Configuration Status. In the following example, both members are in sync:

# get system ha status
HA Health Status: OK
Model: FortiGate-VM64
Mode: HA A-P
Group: 0
Debug: 0
Cluster Uptime: 0 days 0:29:2
Cluster state change time: 2020-09-25 08:23:09
Primary selected using:
    <2020/09/25 08:23:09> FGVME000000JUG0E is selected as the primary because it has the largest value of override priority.
    <2020/09/25 08:23:09> FGVMEV00000M6S87 is selected as the primary because it's the only member in the cluster.
ses_pickup: disable
override: disable
Configuration Status:
    FGVME000000JUG0E(updated 2 seconds ago): in-sync
    FGVMEV00000M6S87(updated 4 seconds ago): in-sync
System Usage stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        sessions=11, average-cpu-user/nice/system/idle=1%/0%/1%/98%, memory=69%
    FGVMEV00000M6S87(updated 4 seconds ago):
        sessions=1, average-cpu-user/nice/system/idle=0%/0%/1%/99%, memory=69%
HBDEV stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=60578029/155605/0/0, tx=13360110/25218/0/0
    FGVMEV00000M6S87(updated 4 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=7006310/19328/0/0, tx=6220835/13974/0/0
MONDEV stats:
    FGVME000000JUG0E(updated 2 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=60578029/155605/0/0, tx=13360110/25218/0/0
        port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=70459776/175970/0/0, tx=36854/226/0/0
    FGVMEV00000M6S87(updated 4 seconds ago):
        port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=7006310/19328/0/0, tx=6220835/13974/0/0
        port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=7197677/20580/0/0, tx=29200/83/0/0
Primary     : HA1             , FGVME000000JUG0E, HA cluster index = 0
Secondary   : HA2             , FGVMEV00000M6S87, HA cluster index = 1
number of vcluster: 1
vcluster 1: work 169.254.0.1
Primary: FGVME000000JUG0E, HA operating index = 0
Secondary: FGVMEV00000M6S87, HA operating index = 1