Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
So I leave the HA interface configured with 0.0.0.0.0/0.0.0.0.0?
If you use broadcast, you are right. You should leave 0.0.0.0.0/0.0.0.0.0.
And also you can review these documents about troubleshooting HA.
When I set up HA on the primary I have GUI connectivity to the primary and when I then set up HA on the secondary I lose GUI connectivity to the primary. They never synchronise....
Thank you for your help but I think this is impossible....
Hello @amg7 ,
it is not impossible. I have used this before and it worked properly.
My advice is, if you have a contract you can create a case. Fortinet engineers inspect the problem deeply and will solve the problem.
Yes I did that too, they checked the configuration of my fortigate and in principle it was correct, they tell me it could be a HyperV problem, the only solution they gave me is to configure everything again.
Created on 03-20-2024 08:56 AM Edited on 03-20-2024 08:58 AM
Btw, i found one more document about ha troubleshooting.
Can you try to collect output with these commands? With these output results, we can see whether there is a problem with Hyper-V or not.
Collect heartbeat packet captures during the 'heartbeat packet loss' issue from both the primary and secondary units, then use them to verify whether the heartbeat packets sent from the primary are received on the secondary and vice versa.
Packet capture commands:
HA Master:
diag sniffer packet any 'ether proto 0x8890' 4 0 l | grep ha1
2023-06-05 16:52:15.630003 ha1 out Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.698791 ha1 in Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.740012 ha1 out Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.798792 ha1 in Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.840003 ha1 out Ether type 0x8890 printer hasn't been added to sniffer.
HA slave:
diag sniffer packet any 'ether proto 0x8890' 4 0 l | grep ha1
23-06-05 16:52:15.822283 ha1 out Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.863515 ha1 in Ether type 0x8890 printer hasn't been added to sniffer.
2023-06-05 16:52:15.932283 ha1 out Ether type 0x8890 printer hasn't been added to sniffer.
Port3 out Ether type 0x8890 printer hasn't been added to sniffer
Port3 in Ether type 0x8890 printer hasn't been added to sniffer
I get that all the time
Can I follow this?
Here if you configure IP on the HA-sync interface.
If you use the Live migration feature on Hyper-V. You need to do these steps also.
I cannot launch this test
diag sniffer packet any 'ether proto 0x8890' 4 0 l | grep ha1
Will not allow me to type ' or paste into HyperV console
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
227 |
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 2024 Fortinet, Inc. All Rights Reserved.