|
In the loading state, LS request packets are sent to request the more recent instance of an LSA that has not been received during the exchange process.
In the above Figure, Router1 is in the loading state and is sending LS request packets to receive a more recent instance of an LSA.
Problem:
OSPF neighbor stuck in the loading state.
The most common causes of this problem are as follows:
- Mismatched MTU.
- Corrupted link-state request packet.
- When the OSPF database is full, the LSA limit is exceeded.
- large LSU packets containing a larger router LSA.
- Packet loss results in LSAs being dropped in between.
- Corrupted LSAs are generally seen in logs as BADLSA.
For this, it is necessary to check that the LSA is limited.
Solution:
- Adjust the MTU. Reset the IPsec /OSPF neighbor (do not do it if it is an ADVPN setup), and during the downtime, reset the IPsec /OSPF neighbor on the spoke device and check.
- Configure the stub area, and the HUB advertises the default route to this spoke.
- Summarize the network in the Hub (ABR OR ASBR) and send the route to the spoke.
- Once the spoke receives a summarized route and a default route from the Hub, it will reduce the OSPF database.
Run the commands below and check the status:
get router info OSPF interface
get router info OSPF neighbor
get router info ospf database brief
Related article:
Troubleshooting Tip: OSPF neighbor stuck in the 'loading' state
|
