Technical Tip: IPsec VPN stops passing traffic with DPD failure status despite no failure in actual DPD messages
| Description | This article describes an issue where the DPD status of a tunnel may fail, causing the interface to be marked as inactive. |
| Scope | FortiOS v7.4.4 and later, v7.6.0 and later. |
| Solution | Symptoms:
Working scenario:
get router info routing-table database S *> 0.0.0.0/0 [10/0] via IPSec tunnel 10.0.0.1, [1/0] <----- Route is active.
diagnose vpn tunnel list name=IPSec ver=2 serial=1 10.56.6.245:4500->10.10.88.247:4500 nexthop=10.56.6.241 tun_id=10.0.0.1 tun_id6=::10.0.0.1 status=up dst_mtu=1500 weight=1
Non-working scenario: get router info routing-table database S > 0.0.0.0/0 [10/0] via IPSec tunnel 10.0.0.1 inactive, [1/0] <----- Route listed as inactive.
diagnose vpn tunnel list name=IPSec ver=2 serial=1 10.56.6.245:4500->10.10.88.246:4500 nexthop=10.56.6.241 tun_id=10.0.0.1 tun_id6=::10.0.0.1 status=up dst_mtu=1500 weight=1
The issue has multiple possible observed triggers, including changing tunnel configuration and HA failover events.
Workaround: Bringing the tunnel down and back up or rebooting the FortiGate temporarily restores VPN functionality, but the issue may reoccur. Disabling DPD in the tunnel configuration does not serve as a workaround.
Solution: This issue has been resolved in:
The fix optimizes the DPD status check and update process to prevent inactive route behavior.
Related articles:
|