Troubleshooting Tip: How to resolve a non-working HA from the VM platform itself

[Ahmed_Galal]

Description	This article describes how to troubleshoot a non-working HA from the VM platform itself such as vSphere.
Scope	FortiADC.
Solution	The following issues may occur when the HA is configured on the FortiADC units while the virtual machine is not configured as expected: FortiADC does not respond to the incoming SYN packets. Many CLI commands are missing. FortiADC does not generate any outputs upon running the following HA debug commands: diagnose debug ha all diagnose debug enable Troubleshooting the HA at the virtual machine: The HA interface must be configured with its own unique VLAN and not a shared VLAN. If the dedicated management interface is enabled, ensure that Promiscuous mode is set to 'Accept' in the security options of the Vswitch.  Ensure that the security options of the HA vlan is set to accept for the MAC Address Changes and Forged Transmits. Note: While configuring the security options of the HA vlan Promiscuous mode should be set to 'Reject' when MAC Learning is enabled for the Distributed Virtual Port Group connected to the management interface. Related document: Configuring the management interface - FortiADC 7.4.7 handbook