Created on
11-03-2025
10:39 PM
Edited on
11-03-2025
10:39 PM
By
Anthony_E
| Description |
This article describes an uncommon issue under investigation 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: Rebooting the FortiGate restores VPN functionality, but the issue may occur again. Disabling DPD in the tunnel configuration does not work around this issue.
Solution: The issue is resolved in v7.4.9 and scheduled for resolution in the upcoming v7.6.5. See Issue ID 1180987 in FortiOS v7.4.9 Release Notes | Resolved Issues
The fix optimizes the DPD status check and update process to prevent inactive route behavior. |
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 2025 Fortinet, Inc. All Rights Reserved.