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

[HA Issue][v5.4.1] Going back to standalone after a reboot.

Hi everybody.

 

I'm setting up a new Fortigate HA cluster (300D) and i have a strange issue. Each time i have to reboot a node of the cluster, he came back as a standalone Fortigate. 

 

Any idea how i can resolve that ? This is pretty annoying.

 

Here is the HA configuration.

config system ha
set group-name "Toto"
set mode a-p
set password ENC toto
set hbdev "mgmt1" 50 "mgmt2" 50
set session-pickup enable
set ha-mgmt-status enable
set ha-mgmt-interface "Management" <= this is actually a vlan interface
set ha-mgmt-interface-gateway x.x.x
set override disable
end

1 Solution
pyy
New Contributor III

Hi Can you try to unset this

set ha-mgmt-interface "Management" <= this is actually a vlan interface

and dont use vlan interface just a physical

View solution in original post

22 REPLIES 22
pyy
New Contributor III

Hi Ede the issue is related to the sub-interface(vlan) used for management purposes not the HA ports

AlexandreL
New Contributor

pyy is totally right

 

Management port 1 and 2 still works very fine as HA ports. It was the Management sub-interface for the HA which caused my problem.

ede_pfau

Ah, thanks that you put that right explicitely.

 

Is my reasoning right that if you are allowed to select a VLAN port for the HA link it should work? So this might really be a bug (and should be reported to FTNT via support ticket - otherwise it might not be fixed).

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