Description | This article describes how to resolve an issue where the user is not able to access a secondary FortiGate GUI interface and receiving the 'reverse path check fail drop' error in debugs. |
Scope | FortiGate. |
Solution |
If FortiGate is in the HA cluster and the primary device is accessible through HA Reserved Management interface but the secondary device is not accessible through the GUI, run the following debug commands on the secondary unit. The errors below will be shown:
di de dis di de flow filter addr 192.168.x.x 172.23.y.y and di de flow filter port 443 diag debug console timestamp enable diag debug flow trace start 1000 diag debug en
d=65308 trace_id=1 func=print_pkt_detail line=5836 msg="vd-vsys_hamgmt:0 received a packet(proto=6, 192.168.x.x :57291->
This issue appears to be due to the gateway not being configured under HA configuration on the secondary FortiGate.
In order to resolve the issue, follow the steps below:
To connect to the slave FortiGate, proceed with the following command in the CLI:
execute ha manage <HA cluster index of slave> <username> <password>
config system ha config ha-mgmt-interface edit 1 set interface <interface name> set gateway <x.x.x.x.> <- The gateway should be the same as the primary unit. next end
After specifying the Gateway, the Secondary unit GUI should be accessible.
For more details about the HA Reserved Management Interface, refer to Technical Tip: HA Reserved Management Interface. |
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.