Fortigate not showing any logs for HA

[ganesh_karale]

Fortigate not showing any logs in Events >> HA Events.

Checked the same in FAZ and there also it is not showing any log for HA.

Both device are showing status Synchronized in HA section.

Trying to check ha history "diagnose sys ha history " but that is also not showing any output.

Please guide.. 

[fricci_FTNT]

Hi @ganesh_karale ,

What model is your FortiGate and FOS version?
Have you configured HA a-p or a-a?

Can you paste the output of "get sys ha status" from both HA units?

Best regards,

[ganesh_karale]

Master Output :

---------------------------

get system ha status
Primary selected using:
HA Health Status: OK
Model: FortiGate-100E
Mode: HA A-P
Group: 33
Debug: 0
Cluster Uptime: 126 days 18:4:5
Cluster state change time: 2024-05-17 20:59:37
<2024/05/17 20:59:37> FG100ETK19016779 is selected as the primary because its uptime is larger than peer member FG100ETK20018741.
<2024/05/17 20:55:51> FG100ETK19016779 is selected as the primary because it's the only member in the cluster.
<2024/05/17 20:55:45> FG100ETK19016779 is selected as the primary because SET_AS_SECONDARY flag is set on peer member FG100ETK20018741.
<2024/05/17 20:38:29> FG100ETK20018741 is selected as the primary because its override priority is larger than peer member FG100ETK19016779.
ses_pickup: enable, ses_pickup_delay=disable
override: disable
Configuration Status:
FG100ETK19016779(updated 2 seconds ago): in-sync
FG100ETK20018741(updated 2 seconds ago): in-sync
System Usage stats:
FG100ETK19016779(updated 2 seconds ago):
sessions=15020, average-cpu-user/nice/system/idle=23%/0%/4%/66%, memory=43%
FG100ETK20018741(updated 2 seconds ago):
sessions=14024, average-cpu-user/nice/system/idle=8%/0%/0%/90%, memory=37%
HBDEV stats:
FG100ETK19016779(updated 2 seconds ago):
ha1: physical/1000auto, up, rx-bytes/packets/dropped/errors=1827228183/5582150/0/0, tx=2335027897/13854156/0/0
ha2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1254359956/2534670/0/0, tx=1237436919/2535256/0/0
FG100ETK20018741(updated 2 seconds ago):
ha1: physical/1000auto, up, rx-bytes/packets/dropped/errors=2328409004/13825301/0/0, tx=1766184977/5524525/0/0
ha2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1234831147/2529958/0/0, tx=1251540727/2528893/0/0
MONDEV stats:
FG100ETK19016779(updated 2 seconds ago):
port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=791501662/776299205/0/0, tx=1316336940/571297615/0/0
port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=171230198/68582653/0/0, tx=4022192008/45598585/0/0
wan1: physical/100full, up, rx-bytes/packets/dropped/errors=3300559250/559447723/0/0, tx=3094272545/500323595/0/0
wan2: physical/100full, up, rx-bytes/packets/dropped/errors=150061868/1468168/0/0, tx=2548478516/4725211/0/0
FG100ETK20018741(updated 2 seconds ago):
port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=205020/3417/0/0, tx=0/0/0/0
port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1365960/8435/0/0, tx=0/0/0/0
wan1: physical/100full, up, rx-bytes/packets/dropped/errors=18287626/140748/0/0, tx=0/0/0/0
wan2: physical/100full, up, rx-bytes/packets/dropped/errors=20430748/149515/0/0, tx=0/0/0/0
Primary : FGTRGIGOREGAON02, FG100ETK19016779, HA cluster index = 1
Secondary : FGTRGIGOREGAON01, FG100ETK20018741, HA cluster index = 0
number of vcluster: 1
vcluster 1: work 169.254.0.2
Primary: FG100ETK19016779, HA operating index = 0
Secondary: FG100ETK20018741, HA operating index = 1

==============================================

Slave Output :

---------------------------

get system ha status
HA Health Status: OK
Model: FortiGate-100E
Mode: HA A-P
Group: 33
Debug: 0
Cluster Uptime: 126 days 18:8:21
Cluster state change time: 2024-05-17 20:59:36
Primary selected using:
<2024/05/17 20:59:36> FG100ETK19016779 is selected as the primary because its uptime is larger than peer member FG100ETK20018741.
<2024/05/17 20:59:36> FG100ETK20018741 is selected as the primary because its override priority is larger than peer member FG100ETK19016779.
ses_pickup: enable, ses_pickup_delay=disable
override: disable
Configuration Status:
FG100ETK20018741(updated 1 seconds ago): in-sync
FG100ETK19016779(updated 1 seconds ago): in-sync
System Usage stats:
FG100ETK20018741(updated 1 seconds ago):
sessions=14762, average-cpu-user/nice/system/idle=30%/0%/3%/66%, memory=37%
FG100ETK19016779(updated 1 seconds ago):
sessions=15929, average-cpu-user/nice/system/idle=26%/0%/7%/55%, memory=43%
HBDEV stats:
FG100ETK20018741(updated 1 seconds ago):
ha1: physical/1000auto, up, rx-bytes/packets/dropped/errors=2349133639/13845859/0/0, tx=1767408651/5528551/0/0
ha2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1235454323/2531235/0/0, tx=1252173337/2530171/0/0
FG100ETK19016779(updated 1 seconds ago):
ha1: physical/1000auto, up, rx-bytes/packets/dropped/errors=1828449582/5586170/0/0, tx=2355718713/13874672/0/0
ha2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1254991081/2535945/0/0, tx=1238059119/2536531/0/0
MONDEV stats:
FG100ETK20018741(updated 1 seconds ago):
port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=205140/3419/0/0, tx=0/0/0/0
port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=1366608/8439/0/0, tx=0/0/0/0
wan1: physical/100full, up, rx-bytes/packets/dropped/errors=18294174/140814/0/0, tx=0/0/0/0
wan2: physical/100full, up, rx-bytes/packets/dropped/errors=20437628/149581/0/0, tx=0/0/0/0
FG100ETK19016779(updated 1 seconds ago):
port1: physical/1000auto, up, rx-bytes/packets/dropped/errors=1676328865/777202761/0/0, tx=1558228096/571950175/0/0
port2: physical/1000auto, up, rx-bytes/packets/dropped/errors=310903060/68883150/0/0, tx=175795421/45964977/0/0
wan1: physical/100full, up, rx-bytes/packets/dropped/errors=461543331/561009424/0/0, tx=3549186505/501584378/0/0
wan2: physical/100full, up, rx-bytes/packets/dropped/errors=150095793/1468718/0/0, tx=2564274891/4741254/0/0
Secondary : FGTRGIGOREGAON01, FG100ETK20018741, HA cluster index = 0
Primary : FGTRGIGOREGAON02, FG100ETK19016779, HA cluster index = 1
number of vcluster: 1
vcluster 1: standby 169.254.0.2
Secondary: FG100ETK20018741, HA operating index = 1
Primary: FG100ETK19016779, HA operating index = 0

[ganesh_karale]

Model : Fortigate 100E, Version: v7.0.14

HA : Active-Passive

[fricci_FTNT]

Thank you. I can see that there are HA events from the 17/05/2024 that should appear in the diag sys ha history read .

Can you paste the output of that command? (make sure you include the word read)

Do you see all other event log types in the FortiGate/FAZ as expected? So only HA events are not showing from my understanding, correct?
Is the GUI page loading indefinitely or it loads and it just shows 0 logs?

Best regards,

[ganesh_karale]

Hi, please find below output.

We crosschecked in FGT and FAZ as well. There is no single event for HA.

If I am running command " diag log test" it shows test log.

But apart from this there is no HA event in FGT and FAZ as well.

diag sys ha history read
version=1.1
HA state change time: 2024-05-17 20:59:37
message_count=426/512
<2024-05-17 21:15:16> port mgmt link status changed: 1->0
<2024-05-17 21:06:37> hbdev ha1 link status changed: 0->1
<2024-05-17 21:06:37> port ha1 link status changed: 0->1
<2024-05-17 21:05:09> hbdev ha1 link status changed: 1->0
<2024-05-17 21:05:09> port ha1 link status changed: 1->0
<2024-05-17 21:05:08> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2024-05-17 21:04:51> hbdev ha2 link status changed: 0->1
<2024-05-17 21:04:51> port ha2 link status changed: 0->1
<2024-05-17 21:03:56> hbdev ha2 link status changed: 1->0
<2024-05-17 21:03:56> port ha2 link status changed: 1->0
<2024-05-17 21:03:56> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2024-05-17 20:59:37> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-05-17 20:59:37> new member 'FG100ETK20018741' joins the cluster
<2024-05-17 20:58:59> hbdev ha2 link status changed: 0->1
<2024-05-17 20:58:59> hbdev ha1 link status changed: 0->1
<2024-05-17 20:58:59> port ha2 link status changed: 0->1
<2024-05-17 20:58:59> port ha1 link status changed: 0->1
<2024-05-17 20:58:56> hbdev ha2 link status changed: 1->0
<2024-05-17 20:58:56> hbdev ha1 link status changed: 1->0
<2024-05-17 20:58:56> port ha2 link status changed: 1->0
<2024-05-17 20:58:56> port ha1 link status changed: 1->0
<2024-05-17 20:57:48> hbdev ha1 link status changed: 0->1
<2024-05-17 20:57:48> hbdev ha2 link status changed: 0->1
<2024-05-17 20:57:48> port ha2 link status changed: 0->1
<2024-05-17 20:57:48> port ha1 link status changed: 0->1
<2024-05-17 20:56:27> port mgmt link status changed: 0->1
<2024-05-17 20:56:24> port mgmt link status changed: 1->0
<2024-05-17 20:56:22> port mgmt link status changed: 0->1
<2024-05-17 20:55:52> hbdev ha2 link status changed: 1->0
<2024-05-17 20:55:52> hbdev ha1 link status changed: 1->0
<2024-05-17 20:55:52> port ha2 link status changed: 1->0
<2024-05-17 20:55:52> port ha1 link status changed: 1->0
<2024-05-17 20:55:51> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-05-17 20:55:51> heartbeats from FG100ETK20018741 are lost on all hbdev
<2024-05-17 20:55:51> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2024-05-17 20:55:51> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2024-05-17 20:55:45> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-05-17 20:50:18> port wan2 link status changed: 0->1
<2024-05-17 20:49:58> port wan2 link status changed: 1->0
<2024-05-17 20:49:23> port port2 link status changed: 0->1
<2024-05-17 20:48:24> port port2 link status changed: 1->0
<2024-05-17 20:44:46> port port1 link status changed: 0->1
<2024-05-17 20:44:03> port port1 link status changed: 1->0
<2024-05-17 20:42:10> port port1 link status changed: 0->1
<2024-05-17 20:42:00> port port1 link status changed: 1->0
<2024-05-17 20:40:33> port port1 link status changed: 0->1
<2024-05-17 20:39:39> port port1 link status changed: 1->0
<2024-05-17 20:38:43> port port15 link status changed: 1->0
<2024-05-17 20:38:29> FG100ETK20018741 is elected as the cluster primary of 2 member
<2024-05-17 20:38:29> new member 'FG100ETK20018741' joins the cluster
<2024-05-17 20:38:09> hatalk started
<2024-05-17 20:34:50> hatalk exited
<2024-05-17 20:34:45> FG100ETK20018741 is elected as the cluster primary of 2 member
<2024-05-17 20:13:01> hbdev ha1 link status changed: 0->1
<2024-05-17 20:13:01> port ha1 link status changed: 0->1
<2024-05-17 20:12:19> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-05-17 20:12:19> new member 'FG100ETK20018741' joins the cluster
<2024-05-17 20:12:18> hbdev ha2 link status changed: 0->1
<2024-05-17 20:12:18> port ha2 link status changed: 0->1
<2024-05-17 20:11:24> hbdev ha2 link status changed: 1->0
<2024-05-17 20:11:24> port ha2 link status changed: 1->0
<2024-05-17 20:11:14> hbdev ha1 link status changed: 1->0
<2024-05-17 20:11:14> port ha1 link status changed: 1->0
<2024-05-17 20:11:09> hbdev ha2 link status changed: 0->1
<2024-05-17 20:11:09> port ha2 link status changed: 0->1
<2024-05-17 20:11:09> hbdev ha1 link status changed: 0->1
<2024-05-17 20:11:09> port ha1 link status changed: 0->1
<2024-05-17 20:08:34> hbdev ha2 link status changed: 1->0
<2024-05-17 20:08:34> port ha2 link status changed: 1->0
<2024-05-17 20:08:31> hbdev ha1 link status changed: 1->0
<2024-05-17 20:08:31> port ha1 link status changed: 1->0
<2024-05-17 20:08:28> hbdev ha1 link status changed: 0->1
<2024-05-17 20:08:28> port ha1 link status changed: 0->1
<2024-05-17 20:08:25> hbdev ha1 link status changed: 1->0
<2024-05-17 20:08:25> port ha1 link status changed: 1->0
<2024-05-17 19:35:34> port port8 link status changed: 1->0
<2024-05-17 19:35:22> port port8 link status changed: 0->1
<2024-05-13 08:06:40> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-05-13 08:06:40> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-05-13 08:06:40> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-05-13 08:06:40> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-16 18:13:14> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-16 18:13:14> new member 'FG100ETK19016253' joins the cluster
<2024-04-16 18:13:13> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-16 18:13:11> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-16 18:13:08> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-16 18:13:05> new member 'FG100ETK19016253' joins the cluster
<2024-04-16 18:13:04> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-16 18:13:04> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-16 18:13:04> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-16 18:13:04> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 20:36:04> hbdev ha2 link status changed: 0->1
<2024-04-15 20:36:04> port ha2 link status changed: 0->1
<2024-04-15 20:35:14> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 20:35:13> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 20:35:12> hbdev ha1 link status changed: 0->1
<2024-04-15 20:35:12> port ha1 link status changed: 0->1
<2024-04-15 20:35:10> hbdev ha1 link status changed: 1->0
<2024-04-15 20:35:10> port ha1 link status changed: 1->0
<2024-04-15 20:35:10> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 20:35:09> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 20:35:09> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 20:34:43> hbdev ha1 link status changed: 0->1
<2024-04-15 20:34:43> port ha1 link status changed: 0->1
<2024-04-15 20:34:43> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 20:34:42> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 20:34:40> hbdev ha1 link status changed: 1->0
<2024-04-15 20:34:40> hbdev ha2 link status changed: 1->0
<2024-04-15 20:34:40> port ha2 link status changed: 1->0
<2024-04-15 20:34:40> port ha1 link status changed: 1->0
<2024-04-15 20:34:40> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 20:34:39> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 20:34:39> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-15 20:34:39> hbdev ha1 link status changed: 0->1
<2024-04-15 20:34:39> port ha1 link status changed: 0->1
<2024-04-15 20:33:06> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 20:33:06> port ha1 link status changed: 1->0
<2024-04-15 20:33:06> hbdev ha1 link status changed: 1->0
<2024-04-15 15:24:21> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 15:24:21> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 15:24:21> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 15:24:19> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 15:24:19> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-15 15:24:19> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 15:24:19> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 15:24:17> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 15:24:13> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 15:24:13> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 15:24:13> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 15:24:12> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-15 15:24:10> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 15:24:10> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 15:24:06> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 15:24:06> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 15:24:06> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-15 15:24:06> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-15 09:47:01> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-15 09:47:01> new member 'FG100ETK19016253' joins the cluster
<2024-04-15 09:47:00> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-15 09:47:00> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-15 09:47:00> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-15 09:47:00> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-12 16:48:00> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-12 16:47:55> new member 'FG100ETK19016253' joins the cluster
<2024-04-12 16:47:53> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-12 16:47:53> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-12 16:47:53> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-12 16:47:53> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-12 16:47:49> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-12 16:47:49> new member 'FG100ETK19016253' joins the cluster
<2024-04-12 16:47:40> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-12 16:47:40> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-12 16:47:40> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-12 16:47:40> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-12 16:47:32> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-12 16:47:32> new member 'FG100ETK19016253' joins the cluster
<2024-04-12 16:47:17> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-12 16:47:17> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-12 16:47:17> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-12 16:47:17> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-12 12:49:53> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-12 12:49:53> new member 'FG100ETK19016253' joins the cluster
<2024-04-12 12:49:28> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-12 12:49:28> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-12 12:49:28> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-12 12:49:28> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-10 23:29:50> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-10 23:24:18> port port15 link status changed: 1->0
<2024-04-10 23:24:00> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-04-10 23:23:59> new member 'FG100ETK19016253' joins the cluster
<2024-04-10 23:23:36> hatalk started
<2024-04-10 23:20:21> hatalk exited
<2024-04-10 23:20:21> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-04-10 23:16:57> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-04-10 23:16:56> new member 'FG100ETK19016253' joins the cluster
<2024-04-10 23:16:17> hbdev ha2 link status changed: 0->1
<2024-04-10 23:16:17> port ha2 link status changed: 0->1
<2024-04-10 23:16:16> hbdev ha1 link status changed: 0->1
<2024-04-10 23:16:16> port ha1 link status changed: 0->1
<2024-04-10 23:16:14> hbdev ha2 link status changed: 1->0
<2024-04-10 23:16:14> port ha2 link status changed: 1->0
<2024-04-10 23:16:13> hbdev ha1 link status changed: 1->0
<2024-04-10 23:16:13> port ha1 link status changed: 1->0
<2024-04-10 23:15:03> hbdev ha2 link status changed: 0->1
<2024-04-10 23:15:03> port ha1 link status changed: 0->1
<2024-04-10 23:15:03> hbdev ha1 link status changed: 0->1
<2024-04-10 23:15:03> port ha2 link status changed: 0->1
<2024-04-10 23:13:19> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-04-10 23:13:18> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-04-10 23:13:18> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-04-10 23:13:18> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-04-10 23:13:18> hbdev ha1 link status changed: 1->0
<2024-04-10 23:13:17> hbdev ha2 link status changed: 1->0
<2024-04-10 23:13:17> port ha2 link status changed: 1->0
<2024-04-10 23:13:17> port ha1 link status changed: 1->0
<2024-04-10 23:13:14> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-03-16 00:21:17> port port16 link status changed: 1->0
<2024-03-16 00:20:56> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-03-16 00:20:56> new member 'FG100ETK19016253' joins the cluster
<2024-03-16 00:20:30> hatalk started
<2024-03-16 00:15:48> hatalk exited
<2024-03-16 00:15:36> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-03-16 00:15:10> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-03-16 00:15:10> new member 'FG100ETK19016253' joins the cluster
<2024-03-16 00:14:24> hbdev ha2 link status changed: 0->1
<2024-03-16 00:14:24> hbdev ha1 link status changed: 0->1
<2024-03-16 00:14:24> port ha2 link status changed: 0->1
<2024-03-16 00:14:24> port ha1 link status changed: 0->1
<2024-03-16 00:14:22> hbdev ha2 link status changed: 1->0
<2024-03-16 00:14:21> hbdev ha1 link status changed: 1->0
<2024-03-16 00:14:21> port ha2 link status changed: 1->0
<2024-03-16 00:14:21> port ha1 link status changed: 1->0
<2024-03-16 00:13:13> hbdev ha2 link status changed: 0->1
<2024-03-16 00:13:13> hbdev ha1 link status changed: 0->1
<2024-03-16 00:13:13> port ha2 link status changed: 0->1
<2024-03-16 00:13:13> port ha1 link status changed: 0->1
<2024-03-16 00:10:06> hbdev ha2 link status changed: 1->0
<2024-03-16 00:10:06> hbdev ha1 link status changed: 1->0
<2024-03-16 00:10:06> port ha2 link status changed: 1->0
<2024-03-16 00:10:06> port ha1 link status changed: 1->0
<2024-03-16 00:10:05> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-03-16 00:10:05> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-03-16 00:10:05> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-03-16 00:10:05> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-02-22 20:47:47> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-02-22 20:47:47> new member 'FG100ETK19016253' joins the cluster
<2024-02-22 20:47:11> hbdev ha2 link status changed: 0->1
<2024-02-22 20:47:11> port ha2 link status changed: 0->1
<2024-02-22 20:47:10> hbdev ha1 link status changed: 0->1
<2024-02-22 20:47:10> port ha1 link status changed: 0->1
<2024-02-22 20:47:08> hbdev ha1 link status changed: 1->0
<2024-02-22 20:47:08> port ha2 link status changed: 1->0
<2024-02-22 20:47:08> port ha1 link status changed: 1->0
<2024-02-22 20:45:57> hbdev ha2 link status changed: 0->1
<2024-02-22 20:45:57> hbdev ha1 link status changed: 0->1
<2024-02-22 20:45:57> port ha2 link status changed: 0->1
<2024-02-22 20:45:57> port ha1 link status changed: 0->1
<2024-02-22 20:44:15> hbdev ha2 link status changed: 1->0
<2024-02-22 20:44:15> hbdev ha1 link status changed: 1->0
<2024-02-22 20:44:15> port ha2 link status changed: 1->0
<2024-02-22 20:44:15> port ha1 link status changed: 1->0
<2024-02-22 20:44:14> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-02-22 20:44:13> heartbeats from FG100ETK19016253 are lost on all hbdev
<2024-02-22 20:44:13> member FG100ETK19016253 lost heartbeat on hbdev ha2
<2024-02-22 20:44:13> member FG100ETK19016253 lost heartbeat on hbdev ha1
<2024-02-22 20:44:12> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-02-22 20:35:47> port port1 link status changed: 0->1
<2024-02-22 20:35:24> port port1 link status changed: 1->0
<2024-02-22 20:15:48> port port15 link status changed: 1->0
<2024-02-22 20:15:21> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-02-22 20:15:21> new member 'FG100ETK19016253' joins the cluster
<2024-02-22 20:14:58> hatalk started
<2024-02-22 20:11:43> hatalk exited
<2024-02-22 20:11:42> FG100ETK19016253 is elected as the cluster primary of 2 member
<2024-02-22 19:57:55> port ha2 link status changed: 0->1
<2024-02-22 19:52:46> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-02-22 19:52:45> new member 'FG100ETK19016253' joins the cluster
<2024-02-22 19:52:45> hbdev ha1 link status changed: 0->1
<2024-02-22 19:52:45> port ha1 link status changed: 0->1
<2024-02-22 19:52:34> hbdev ha2 link status changed: 1->0
<2024-02-22 19:52:34> port ha2 link status changed: 1->0
<2024-02-22 19:52:30> hbdev ha1 link status changed: 1->0
<2024-02-22 19:52:30> port ha1 link status changed: 1->0
<2024-02-21 19:57:13> port port1 link status changed: 0->1
<2024-02-21 19:57:02> port port1 link status changed: 1->0
<2024-02-21 19:55:50> hbdev ha2 link status changed: 0->1
<2024-02-21 19:55:50> port ha2 link status changed: 0->1
<2024-02-21 19:55:46> hbdev ha1 link status changed: 0->1
<2024-02-21 19:55:46> port ha1 link status changed: 0->1
<2024-02-21 19:53:32> hbdev ha2 link status changed: 1->0
<2024-02-21 19:53:32> port ha2 link status changed: 1->0
<2024-02-21 19:53:27> hbdev ha1 link status changed: 1->0
<2024-02-21 19:53:27> port ha1 link status changed: 1->0
<2024-02-21 16:45:36> port mgmt link status changed: 1->0
<2024-02-21 16:45:28> port mgmt link status changed: 0->1
<2024-02-21 16:45:23> port mgmt link status changed: 1->0
<2024-02-21 16:39:53> port mgmt link status changed: 0->1
<2024-02-21 16:39:49> port mgmt link status changed: 1->0
<2024-02-21 16:39:04> port mgmt link status changed: 0->1
<2024-02-21 16:28:25> port port1 link status changed: 0->1
<2024-02-21 15:53:53> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-02-21 15:53:52> heartbeats from FG100ETK20018741 are lost on all hbdev
<2024-02-21 15:53:52> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2024-02-21 15:53:52> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2024-01-17 23:25:19> port port16 link status changed: 1->0
<2024-01-17 23:25:01> FG100ETK20018741 is elected as the cluster primary of 2 member
<2024-01-17 23:25:01> new member 'FG100ETK20018741' joins the cluster
<2024-01-17 23:24:42> hatalk started
<2024-01-17 23:21:30> hatalk exited
<2024-01-17 23:20:33> hbdev ha2 link status changed: 1->0
<2024-01-17 23:20:33> hbdev ha1 link status changed: 1->0
<2024-01-17 23:20:33> port ha2 link status changed: 1->0
<2024-01-17 23:20:33> port ha1 link status changed: 1->0
<2024-01-17 23:20:32> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-01-17 23:20:32> heartbeats from FG100ETK20018741 are lost on all hbdev
<2024-01-17 23:20:32> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2024-01-17 23:20:32> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2024-01-17 23:20:30> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-01-17 23:13:05> FG100ETK20018741 is elected as the cluster primary of 2 member
<2024-01-17 23:11:58> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-01-17 23:05:42> FG100ETK20018741 is elected as the cluster primary of 2 member
<2024-01-17 23:05:41> new member 'FG100ETK20018741' joins the cluster
<2024-01-17 23:05:07> hbdev ha2 link status changed: 0->1
<2024-01-17 23:05:07> port ha2 link status changed: 0->1
<2024-01-17 23:05:06> hbdev ha1 link status changed: 0->1
<2024-01-17 23:05:06> port ha1 link status changed: 0->1
<2024-01-17 23:05:04> hbdev ha2 link status changed: 1->0
<2024-01-17 23:05:04> port ha2 link status changed: 1->0
<2024-01-17 23:05:03> hbdev ha1 link status changed: 1->0
<2024-01-17 23:05:03> port ha1 link status changed: 1->0
<2024-01-17 23:03:54> hbdev ha2 link status changed: 0->1
<2024-01-17 23:03:54> port ha2 link status changed: 0->1
<2024-01-17 23:03:54> port ha1 link status changed: 0->1
<2024-01-17 23:02:10> hbdev ha1 link status changed: 1->0
<2024-01-17 23:02:10> port ha1 link status changed: 1->0
<2024-01-17 23:02:10> hbdev ha2 link status changed: 1->0
<2024-01-17 23:02:10> port ha2 link status changed: 1->0
<2024-01-17 23:02:10> FG100ETK19016779 is elected as the cluster primary of 1 member
<2024-01-17 23:02:10> heartbeats from FG100ETK20018741 are lost on all hbdev
<2024-01-17 23:02:10> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2024-01-17 23:02:10> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2024-01-17 23:02:08> FG100ETK19016779 is elected as the cluster primary of 2 member
<2024-01-17 22:45:08> port RGI-FLINK link status changed: 0->1
<2024-01-17 22:45:08> port port16 link status changed: 0->1
<2024-01-17 22:45:04> port RGI-FLINK link status changed: 1->0
<2024-01-17 22:45:04> port port15 link status changed: 1->0
<2024-01-17 22:39:33> port RGI-FLINK link status changed: 0->1
<2024-01-17 22:39:33> port port15 link status changed: 0->1
<2024-01-17 22:39:30> port RGI-FLINK link status changed: 1->0
<2024-01-17 22:39:30> port port16 link status changed: 1->0
<2023-12-22 01:51:41> FG100ETK20018741 is elected as the cluster primary of 2 member
<2023-12-22 01:51:41> new member 'FG100ETK20018741' joins the cluster
<2023-12-22 01:50:55> hbdev ha2 link status changed: 0->1
<2023-12-22 01:50:55> hbdev ha1 link status changed: 0->1
<2023-12-22 01:50:55> port ha2 link status changed: 0->1
<2023-12-22 01:50:55> port ha1 link status changed: 0->1
<2023-12-22 01:50:52> hbdev ha2 link status changed: 1->0
<2023-12-22 01:50:52> hbdev ha1 link status changed: 1->0
<2023-12-22 01:50:52> port ha2 link status changed: 1->0
<2023-12-22 01:50:52> port ha1 link status changed: 1->0
<2023-12-22 01:49:43> hbdev ha1 link status changed: 0->1
<2023-12-22 01:49:43> hbdev ha2 link status changed: 0->1
<2023-12-22 01:49:43> port ha2 link status changed: 0->1
<2023-12-22 01:49:43> port ha1 link status changed: 0->1
<2023-12-22 01:46:23> hbdev ha2 link status changed: 1->0
<2023-12-22 01:46:23> hbdev ha1 link status changed: 1->0
<2023-12-22 01:46:23> port ha2 link status changed: 1->0
<2023-12-22 01:46:23> port ha1 link status changed: 1->0
<2023-12-22 01:46:22> FG100ETK19016779 is elected as the cluster primary of 1 member
<2023-12-22 01:46:21> heartbeats from FG100ETK20018741 are lost on all hbdev
<2023-12-22 01:46:21> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2023-12-22 01:46:06> FG100ETK19016779 is elected as the cluster primary of 2 member
<2023-12-22 01:42:44> port port15 link status changed: 1->0
<2023-12-22 01:42:25> FG100ETK20018741 is elected as the cluster primary of 2 member
<2023-12-22 01:42:25> new member 'FG100ETK20018741' joins the cluster
<2023-12-22 01:41:55> hatalk started
<2023-12-22 01:37:10> hatalk exited
<2023-11-08 21:42:44> port port16 link status changed: 1->0
<2023-11-08 21:42:33> FG100ETK20018741 is elected as the cluster primary of 2 member
<2023-11-08 21:42:33> new member 'FG100ETK20018741' joins the cluster
<2023-11-08 21:42:04> hatalk started
<2023-11-08 20:22:53> hatalk exited
<2023-11-08 20:17:06> port RGI-FLINK link status changed: 1->0
<2023-11-08 20:17:05> port port15 link status changed: 1->0
<2023-11-08 20:01:27> hbdev ha2 link status changed: 1->0
<2023-11-08 20:01:27> hbdev ha1 link status changed: 1->0
<2023-11-08 20:01:27> port ha2 link status changed: 1->0
<2023-11-08 20:01:27> port ha1 link status changed: 1->0
<2023-11-08 20:01:25> FG100ETK19016779 is elected as the cluster primary of 1 member
<2023-11-08 20:01:25> heartbeats from FG100ETK20018741 are lost on all hbdev
<2023-11-08 20:01:25> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2023-11-08 20:01:25> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2023-11-08 20:01:23> FG100ETK19016779 is elected as the cluster primary of 2 member
<2023-09-06 21:12:15> port RGI-FLINK link status changed: 0->1
<2023-09-06 21:12:15> port port15 link status changed: 0->1
<2023-09-06 21:10:40> port RGI-FLINK link status changed: 1->0
<2023-09-06 21:10:39> port port16 link status changed: 1->0
<2023-09-06 20:45:48> FG100ETK20018741 is elected as the cluster primary of 2 member
<2023-09-06 20:45:48> new member 'FG100ETK20018741' joins the cluster
<2023-09-06 20:45:10> hbdev ha2 link status changed: 0->1
<2023-09-06 20:45:10> port ha2 link status changed: 0->1
<2023-09-06 20:45:09> hbdev ha1 link status changed: 0->1
<2023-09-06 20:45:09> port ha1 link status changed: 0->1
<2023-09-06 20:45:07> hbdev ha2 link status changed: 1->0
<2023-09-06 20:45:07> port ha2 link status changed: 1->0
<2023-09-06 20:45:06> hbdev ha1 link status changed: 1->0
<2023-09-06 20:45:06> port ha1 link status changed: 1->0
<2023-09-06 20:43:55> hbdev ha1 link status changed: 0->1
<2023-09-06 20:43:55> hbdev ha2 link status changed: 0->1
<2023-09-06 20:43:55> port ha2 link status changed: 0->1
<2023-09-06 20:43:55> port ha1 link status changed: 0->1
<2023-09-06 20:42:14> hbdev ha1 link status changed: 1->0
<2023-09-06 20:42:14> port ha1 link status changed: 1->0
<2023-09-06 20:42:12> hbdev ha2 link status changed: 1->0
<2023-09-06 20:42:12> port ha2 link status changed: 1->0
<2023-09-06 20:42:12> FG100ETK19016779 is elected as the cluster primary of 1 member
<2023-09-06 20:42:11> heartbeats from FG100ETK20018741 are lost on all hbdev
<2023-09-06 20:42:11> member FG100ETK20018741 lost heartbeat on hbdev ha2
<2023-09-06 20:42:11> member FG100ETK20018741 lost heartbeat on hbdev ha1
<2023-09-06 20:42:05> FG100ETK19016779 is elected as the cluster primary of 2 member
<2023-09-06 20:22:06> port port15 link status changed: 1->0
<2023-09-06 20:21:49> port port15 link status changed: 0->1
<2023-09-06 20:21:40> port RGI-FLINK link status changed: 0->1
<2023-09-06 20:21:39> port port16 link status changed: 0->1
<2023-09-06 20:21:28> port RGI-FLINK link status changed: 1->0
<2023-09-06 20:21:27> port port15 link status changed: 1->0
<2023-09-06 20:21:15> port RGI-FLINK link status changed: 0->1
<2023-09-06 20:21:14> port port15 link status changed: 0->1
<2023-09-06 20:14:54> port wan2 link status changed: 0->1
<2023-09-06 20:14:46> port wan1 link status changed: 0->1
<2023-09-06 20:14:17> port port2 link status changed: 0->1
<2023-09-06 20:14:09> hbdev ha2 link status changed: 0->1
<2023-09-06 20:14:09> port ha2 link status changed: 0->1
<2023-09-06 20:13:43> port mgmt link status changed: 1->0
<2023-09-06 20:11:48> FG100ETK20018741 is elected as the cluster primary of 2 member
<2023-09-06 20:11:48> new member 'FG100ETK20018741' joins the cluster
<2023-09-06 20:11:47> hbdev ha1 link status changed: 0->1
<2023-09-06 20:11:47> port ha1 link status changed: 0->1
<2023-09-06 20:11:34> FG100ETK19016779 is elected as the cluster primary of 1 member
<2023-09-06 20:10:50> hatalk started
<1970-01-01 05:30:00>
<1970-01-01 05:30:00>
<1970-01-01 05:30:00>
<1970-01-01 05:30:00>
<1970-01-01 05:30:00>
<1970-01-01 05:30:00>

[fricci_FTNT]

If you execute the following commands, how many event messages do you see?
execute log filter reset
execute log filter device 0
execute log filter category 1

execute log filter view-lines 20
execute log filter field subtype ha
execute log filter dump
execute log display

And if you execute the following commands, how many events do you see?
execute log filter reset
execute log filter device 2
execute log filter category 1

execute log filter view-lines 20
execute log filter field subtype ha
execute log filter dump
execute log display

[ganesh_karale]

FGT02 # execute log filter reset

FGT02 # execute log filter device 0

FGT02 # execute log filter category 1

FGT02 #
FGT02 # execute log filter view-lines 20

FGT02 # execute log filter field subtype ha

FGT02 # execute log filter dump
category: event
device: memory
start-line: 1
view-lines: 20
max-checklines: 0
HA member:
log search mode: on-demand
pre-fetch-pages: 2
Filter: ( subtype "ha" )
Oftp search string: (and (or subtype=="ha" not-exact))

FGT02 # execute log display
1 logs found.
1 logs returned.

1: date=2024-05-23 time=13:32:55 eventtime=1716451375542942810 tz="+0530" logid="0108037898" type="event" subtype="ha" level="warning" vd="root" logdesc="HA device interface failed" msg="HA device(interface) fail" ha_role="primary" devintfname="intf_name"

FGT02 #
FGT02 #
FGT02 #
FGT02 #
FGT02 # execute log filter reset

FGT02 # execute log filter device 2

FGT02 # execute log filter category 1

FGT02 #
FGT02 # execute log filter view-lines 20

FGT02 # execute log filter field subtype ha

FGT02 # execute log filter dump
category: event
device: fortianalyzer-cloud
start-line: 1
view-lines: 20
max-checklines: 0
HA member:
Filter: ( subtype "ha" )
Oftp search string: (and (or vd=="root" exact) (or subtype=="ha" not-exact))

FGT02 # execute log display
0 logs found.
0 logs returned.date=2024-05-23 time=13:32:55 eventtime=1716451375542942810 tz="+0530" logid="0108037898" type="event" subtype="ha" level="warning" vd="root" logdesc="HA device interface failed" msg="HA device(interface) fail" ha_role="primary" devintfname="intf_name"

[fricci_FTNT · Accepted solution]

Hi @ganesh_karale ,

Thank you for your time on this so far.
The HA events severity seems stuck at warning level even if it is set to information. This is weird behaviour and I also find strange the below fact, 0 logs but there is actually a log:

FGT02 # execute log display
0 logs found.
0 logs returned.date=2024-05-23 time=13:32:55 eventtime=1716451375542942810 tz="+0530" logid="0108037898" ...

Have you tried to change the severity, save it, then change it back?
config log memory filter
set severity warning

end

config log fortianalyzer filter
set severity warning

end

then change it back to information.

If that does not work, try to failover and see if the issue is still there. I would then suggest you to open a ticket with our support so this can be properly investigated.

Best regards,

[ganesh_karale]

Thanks. Post this changes warning and then information issue got resolved. Now able to see the logs.