Created on
07-07-2009
06:51 AM
Edited on
06-08-2025
03:01 PM
By
Jean-Philippe_P
Description
2009-02-16 11:06:34 device_id=FG2001111111 log_id=0105035001 type=event subtype=ha pri=critical vd=root msg="HA secondary heartbeat interface internal lost neighbor information"
or
2009-02-16 11:06:40 device_id=FG2001111111 log_id=0105035001 type=event subtype=ha pri=notice vd=root msg="Virtual cluster 1 of group 0 detected new joined HA member"
or
2009-02-16 11:06:40 device_id=FG2001111111 log_id=0105035001 type=event subtype=ha pri=notice vd=root msg="HA primary heartbeat interface internal get peer information"
Scope
FortiGate is running in HA mode.
Solution
Debug log: from the GUI, download the GUI: System -> Maintenance -> Advanced -> Debug log.
CLI commands output:
diagnose sys top 2 <-- Keep it running for 20s.
get sys perf status <-- Repeat this command multiple times to get good samples.
get sys ha status
diagnose sys ha status
diagnose sys ha dump all
diagnose sys ha dump 2
diagnose sys ha dump 3
diagnose netlink dev list
diagnose hardware dev nic <Heartbeat port Name>
execute log filter category event
execute log display
Related articles:
Troubleshooting Tip : Monitor CPU and Memory on a FortiGate
Troubleshooting Note : FortiGate HA synchronization messages and cluster verification steps
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.