Table of Contents
OSPF neighbor state stuck in Exstart if MTU mismatch
OSPF neighbors are in the 2-Way or Full state when normal; 2-Way is just a neighbor relationship, and Full indicates that LSDB synchronization is complete in the Adjacency relationship. However, there are times when the neighbor state gets stuck in the Exstart state.
The main reason why neighbor gets stuck in Exstart state is MTU mismatch. The Exstart state is the state in which the neighbor is deciding which side to start from when exchanging DD packets; DD packets contain Interface MTU information, and if the Interface MTU is mismatched, the neighbor state will not proceed beyond Exstart.
LSAs are advertised in LSU packets on OSPF. If there are many LSAs to be advertised, the size of the LSU packet may become large and may be separated; if the MTUs do not match, the separated LSU packets may not be exchanged properly. Therefore, the MTU must be matched between neighbors.
Example of getting stuck in Exstart state
Let’s look at a specific example of a neighbor getting stuck in the Exstart state in the following network diagram.
The configuration related to OSPF on R1 is as follows: MTU of Fa0/0 on R1 is changed to 1400 bytes.
interface Loopback0 ip address 192.168.1.1 255.255.255.0 ip ospf network point-to-point ! interface FastEthernet0/0 ip address 192.168.12.1 255.255.255.0 ip mtu 1400 ! router ospf 1 router-id 126.96.36.199 log-adjacency-changes network 192.168.0.0 0.0.255.255 area 0
The configuration related to OSPF on R2 is as follows: R2 Fa0/0 MTU size is kept at default.
interface Loopback0 ip address 192.168.2.2 255.255.255.0 ip ospf network point-to-point ! interface FastEthernet0/0 ip address 192.168.12.2 255.255.255.0 ! router ospf 1 router-id 188.8.131.52 log-adjacency-changes network 192.168.0.0 0.0.255.255 area 0
When the MTU of R1 and R2 are mismatched, use the show ip ospf neighbor command to verify the neighbor status.
R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 184.108.40.206 1 EXSTART/DR 00:00:37 192.168.12.2 FastEthernet0/0
R2#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 220.127.116.11 1 EXSTART/BDR 00:00:37 192.168.12.1 FastEthernet0/0
You can see that the neighbor state stays in the Exstart state and the process of LSDB synchronization does not go ahead. You can also clearly see that the MTU is mismatched with the debug ip ospf adj command.
R1#debug ip ospf adj OSPF adjacency events debugging is on R1# *Mar 1 14:13:52.556: OSPF: Send DBD to 18.104.22.168 on FastEthernet0/0 seq 0x1141 opt 0x52 flag 0x7 len 32 *Mar 1 14:13:52.560: OSPF: Retransmitting DBD to 22.214.171.124 on FastEthernet0/0  *Mar 1 14:13:53.304: OSPF: Rcv DBD from 126.96.36.199 on FastEthernet0/0 seq 0x520 opt 0x52 flag 0x7 len 32 mtu 1500 state EXSTART *Mar 1 14:13:53.304: OSPF: Nbr 188.8.131.52 has larger interface MTU R1#u all All possible debugging has been turned off
ip ospf mtu-ignore command
In order to avoid getting stuck in the Exstart state, the basic rule is to make sure that the MTU is the same between neighbors. By default, the MTU of the neighbors should match, but when changing the MTU, make sure that the MTU is the same between the neighbors.
It can also be configured to ignore MTU mismatch in order to avoid getting stuck in Exstart state. The command to do so is as follows.
(config-if)#ip ospf mtu-ignore
<interface-name> : interface name
The ip ospf mtu-ignore command can be configured on the router with the smaller MTU, so that you can proceed from the Exstart state even if the MTU is mismatched. However, if LSU packets are large in size, it may not be possible to exchange LSU packets properly.
If you configure the ip ospf mtu-ignore command on Fa0/0 of R1 as shown in the previous example, the neighbor state will be Full and LSDB synchronization is ensured.
interface FastEthernet0/0 ip ospf mtu-ignore
R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 184.108.40.206 1 FULL/DR 00:00:39 192.168.12.2 FastEthernet0/0
- If the MTU does not match between neighbors, the state of the neighbor will be stuck in the Exstart state.
- To ignore the MTU mismatch, enter the following command in interface configuration mode.
- (config-if)#ip ospf mtu-ignore
- OSPF Overview
- OSPF process flow
- OSPF Router ID : Identify OSPF routers
- What if the router ID of the OSPF router is duplicated?
- OSPF Neighbor and Adjacency
- OSPF DR/BDR
- How show ip ospf neighbor looks on Ethernet
- OSPF Network Type : Classification of OSPF-enabled interfaces
- Synchronization process of OSPF LSDB
- Problems with large-scale OSPF network
- OSPF Area – Inside the area, in detail; outside the area, just a summary
- OSPF Router Type
- OSPF LSA Type
- OSPF Area Type
- OSPF Basic Configuration and Verification Commands
- Details of enabling OSPF on the interface
- OSPF Advertising Loopback Interface
- Configuring and Verifying OSPF Hello/Dead interval
- OSPF Cost Configuration and Verification
- Configuring and Verifying OSPF Router Priority
- Configuring OSPF Neighbor Authentication
- Neighbor Authentication over Virtual-link
- OSPF Configuring and Verifying Stub area [Cisco]
- OSPF Stub Area Configuration Example [Cisco]
- OSPF default route generation : default-information originate command
- Configuration Example of OSPF default route generation : stub area
- OSPF Virtual-Link : Virtual area 0 point-to-point link
- Configuring and Verifying OSPF Virtual-link [Cisco]
- OSPF Virtual-link Configuration Example [Cisco]
- OSPF Virtual-link for discontinuous backbone configuration example
- OSPF Route Summary and Configuration
- Cisco OSPF Route Summary Configuration Example
- OSPF Route Type Preference
- Why the OSPF neighbor state gets stuck in Exstart?
- OSPF packet type and header format
- OSPF Hello Packet
- OSPF DD(Database Description) Packet
- OSPF LSR(Link State Request) Packet
- OSPF LSU(Link State Update) Packet
- OSPF LSAck(Link State Acknowledgement) Packet
- Limitation of OSPF redistribution routes – redistribute maximum-prefix command
- Overview of LSA Filters for OSPF – Filter LSA Type 3/Type 5
- Configuration example of LSA type 3 filter
- Configuration example of LSA type 5 filter
- OSPFv3 Configuration Example [Cisco]