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

HA on FortiGate-VM under Hyper-V

I' m trying to deploy an HA pair of FortiGate-VM appliances under Hyper-V. Standalone they work fine, but as soon as I change HA mode to a-p or a-a, they lose network connectivity on everything except the cluster management port(s), and the cluster never forms. Changing HA mode back to standalone instantly restores connectivity. MAC addresses don' t appear to change, ARP works, but intermittently. I tried all kinds of virtual switches and vNIC settings, but nothing seems to help. I' ve reproduced the issue using build 5.0.6 on Windows Server 2012, and 5.0.7 on Windows 8.1, different host hardware as well. Am I missing some setting that must be configured to make it work?
22 REPLIES 22
amg7
New Contributor

So I leave the HA interface configured with 0.0.0.0.0/0.0.0.0.0?

ozkanaltas
Valued Contributor III

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. 

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-How-to-troubleshoot-HA-synchronizati...

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Note-FortiGate-HA-synchronization-messag...

 

If you have found a solution, please like and accept it to make it easily accessible to others.
NSE 4-5-6-7 OT Sec - ENT FW
If you have found a solution, please like and accept it to make it easily accessible to others.NSE 4-5-6-7 OT Sec - ENT FW
amg7
New Contributor

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....

ozkanaltas
Valued Contributor III

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.

If you have found a solution, please like and accept it to make it easily accessible to others.
NSE 4-5-6-7 OT Sec - ENT FW
If you have found a solution, please like and accept it to make it easily accessible to others.NSE 4-5-6-7 OT Sec - ENT FW
amg7
New Contributor

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.

ozkanaltas
Valued Contributor III

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.

 

 

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-How-to-troubleshoot-HA-Heartbeat-pac...

If you have found a solution, please like and accept it to make it easily accessible to others.
NSE 4-5-6-7 OT Sec - ENT FW
If you have found a solution, please like and accept it to make it easily accessible to others.NSE 4-5-6-7 OT Sec - ENT FW
amg7

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

 

 

amg7
New Contributor

Can I follow this?

 

https://docs.fortinet.com/document/fortigate-private-cloud/7.4.0/microsoft-hyper-v-administration-gu...

 

Here if you configure IP on the HA-sync interface.

ozkanaltas
Valued Contributor III

If you use the Live migration feature on Hyper-V. You need to do these steps also.

If you have found a solution, please like and accept it to make it easily accessible to others.
NSE 4-5-6-7 OT Sec - ENT FW
If you have found a solution, please like and accept it to make it easily accessible to others.NSE 4-5-6-7 OT Sec - ENT FW
amg7
New Contributor

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

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