Created on
11-26-2021
12:48 AM
Edited on
04-13-2025
10:48 PM
By
Jean-Philippe_P
Description | This article discusses why the OSPF neighborship is stuck in an EXSTART state. |
Scope | FortiGate. |
Solution |
The OSPF Neighborship can get stuck in the Exstart/Exchange state, especially when OSPF is negotiated over an IPsec tunnel.
How is this MTU mismatch is identified:
Configuring MTU.
config router ospf
Enable mtu-ignore on the OSPF interface.
config router ospf
Configure MTU value at the Interface:
Note: This configuration is necessary when jumbo frame is enabled on the neighbor's interface. Since FortiGate by default doesn't support Jumbo frames(as default MTU is 1500) and it has to be enabled at the interface level by using the MTU size 9000+ at the interface level that is participating in the OSPF configuration.
config system interface edit port <x> set mtu-override enable set mtu 9216 ------> MTU Value. end end
Note: To form the OSPF neighborship, the MTU also should match on both ends or ignore the MTU using the command set mtu-ignore enable.
Troubleshooting steps:
diagnose ip router ospf all enable diagnose ip router ospf level info diagnose debug console timestamp enable diagnose debug enable Here is an example of the debug output:
Related articles: Technical Note: MTU size and Jumbo frames support on FortiGate devices Technical Tip: Set up a jumbo frame in the IPsec VPN 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 2025 Fortinet, Inc. All Rights Reserved.