OSPF routes are not advertised due to MTU size restriction

Support Center > Search Results > SecureKnowledge Details

Technical Level

Solution ID	sk100866
Technical Level
Product	Quantum Security Gateways, ClusterXL, Cluster - 3rd party, VSX
Version	R77 (EOL), R77.10 (EOL), R77.20, R77.30 (EOL)
OS	Gaia
Platform / Model	All
Date Created	23-May-2014
Last Modified	22-May-2017

Symptoms

Some OSPF routes are not advertised to peer.
Total number of routes to be advertised is more than the MTU allows.
OSPF neighbor state is stuck on LOADING phase.

Debug for routed daemon according to SK84520 shows the following messages in routed.log:

task_send_packet_iovec: task OSPF2_IO socket 17 length 1800 if_index 5 to Y.Y.Y.Y: Message too long 
OSPFv2: *NOT* SENT X.X.X.X -> Y.Y.Y.Y LSU length 1780 (1780)

Cause

The handling of fragmentation was incorrect in the Gaia kernel.

Routed passed packets to be sent out towards peers and due to fragmentation it was sent with incorrect headers.

Solution

Note: To view this solution you need to Sign In .