Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
stefano_gobbi
New Contributor

Heartbeat device(interface) down

hello to evrybody. I have a cluster made of 2 fortigate. sometimes I get from logs this error from both appliance: Heartbeat device (interface) down - neighbor info lost I changed the cables that connect the appliances. But I get the same errors. Does anyone know what are the reasons of this errors? maybe one port of the appliance has problem? how could I get more information? I also checked the interface messages but there are no errors. thanks.
11 REPLIES 11
ede_pfau
SuperUser
SuperUser

You have probably configured more than one heartbeat interface. Otherwise you' d have noticed (losing the HA interface means breaking up the cluster).
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
stefano_gobbi
New Contributor

yes, I have configured two heartbeat interface. But I don' t understand why. what could be the reasons the interfaces go down ? I' ve changed the cables. there are no errors in the interface info. do you have any advice?
ede_pfau
SuperUser
SuperUser

As long as one of the two HA interfaces work...could it be heavy traffic on the interface so that heartbeat packets are lost?
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
stefano_gobbi
New Contributor

well...actually both HA interface go down...and I don' t suppose that the cause is heavy traffic of the interfaces because it happens also during the night when the appliance is doing nothing. The interfaces go down for some seconds and then go up. I don' t know what to check more..any idea? thanks
ede_pfau
SuperUser
SuperUser

a) open a ticket with Fortinet support b) downgrade to a different patch level You didn' t mention: - do you have direct cabling between the FGs? - which FortiOS version?
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
stefano_gobbi
New Contributor

-yes, I have direct cabling between FGs. -v4.0,build0205,100629 (MR1 Patch 6) thanks.
ede_pfau
SuperUser
SuperUser

Two more ideas: - 4.1.6 seems odd to me; I' ve had trouble with it in conjunction with IPSec. Try 4.1.4 and/or 4.1.8 instead. It' ll only cost you a couple of seconds without traffic. - about the cables: do you use cross-over TP? it might work with straight-through cables as well if the interface is GbE but that (auto-MDI/MDIX) could be a point of failure.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
stefano_gobbi
New Contributor

yes I use cross-over. the interface is 100 Mbps/full duplex. do you think that updating the version cuold be a solution?
ede_pfau
SuperUser
SuperUser

*read my lips* yes. At least you will eliminate one variable. Other than that I' m out of clues. If it is a hardware issue, you' ll have to replace the unit(s) to prove it. Changing the firmware is done quicker. But still, consider a support call in order to get a hardware replacement.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors