> Source: [sk117599](https://support.checkpoint.com/results/sk/sk117599) # sk117599 - RouteD - OSPF Informational and Error Messages | Property | Value | |----------|-------| | Solution ID | sk117599 | | Date Created | 2017-05-25 | | Last Modified | 2017-09-14 | | Technical Level | General | | Products | Security Gateway | | Versions | R82.10, R82, R81.20 | | OS | Gaia | ## Solution **This SecureKnowledge article is intended as a repository of the Gaia routing daemon (RouteD) OSPF informational and error messages.** **Background** Dynamic Routing is fully integrated into the Gaia WebUI and command-line shell. BGP, OSPF and RIP are supported. Dynamic Multicast Routing is supported, using PIM (Sparse Mode (SM), Dense Mode (DM) and Source-Specific Multicast (SSM)) and IGMP. **Open Shortest Path First (OSPF)** - is an interior gateway protocol (IGP) used to exchange routing information between routers within a single autonomous system (AS). OSPF calculates the best path based on true costs using a metric assigned by a network administrator. RIP, the oldest IGP protocol chooses the least-cost path based on hop count. OSPF is more efficient than RIP, has a quicker convergence, and provides equal-cost multipath routing where packets to a single destination can be sent using more than one interface. OSPF is suitable for complex networks with a large number of routers. It can coexist with RIP on a network. Gaia supports OSPFv2, which supports IPv4 addressing. You can run OSPF over a Route-Based VPN by enabling OSPF on a virtual tunnel interface (VTI). For more detailed information, refer to Gaia Advanced Routing Administration Guide ([R77.X](http://downloads.checkpoint.com/dc/download.htm?ID=24803), [R80.10](http://downloads.checkpoint.com/dc/download.htm?ID=54803)). **Important** **These messages should be seen (either in */var/log/routed_messages* or */var/log/messages* ) and in */var/log/routed.log* on non-VSX machines.** **On VSX machines these errors should be seen (either in */var/log/routed_messages_vs* or */var/log/messages* ) and in */var/log/routed_.log*** **Related Solutions:** * [sk117597: RouteD - PIM Informational and Error Messages](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk117597) * [sk117598: RouteD - BGP Informational and Error Messages](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk117598) |-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Error Message Text | Description | | OSPF IO: Malformed xx LSA from xx | Link State Update (LSU) packets implement the flooding of link state advertisements. Each Link State Update packet carries a collection of link state advertisements one hop further from its origin. Several link state advertisements may be included in a single packet. In order to make the flooding procedure reliable, flooded advertisements are acknowledged in Link State Acknowledgment packets. The error message here indicates that the size of the packet was less than a router LSA packet should have. Type 7 LSAs contain at least 32 bits for the LS payload as well as the OSPF header. | | OSPF IO: received ## byte runt DD packet from xxx | During the OSPF Exchange state OSPF routers exchange database descriptor packets. Database descriptors contain link-state advertisement (LSA) headers only and describe the contents of the entire link-state database. The DD packet LSA payload is compared to the information contained in the routers link-state database to check if new or more current link-state information is available with the neighbor. A packet was received which was not properly formatted, did not contain all the information it should have, or was truncated. | | OSPF IO: xxx state of is too low | Informational message indicating that the neighbor database is less recent then ours. The DD portion of OSPF packets looks like this: ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |������ 0������ |������ 0������ |��� Options��� |0|0|0|0|0|I|M|MS ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�������������������� DD sequence number����������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�������������������������������������������������������������� | ``` ``` ������ +-������������������������������������������������������������ -+ ``` ``` ������ |���������������������������� A�������������������������������� | ``` ``` ������ +-���������������� Link State Advertisement������������������� -+ ``` ``` ������ |�������������������������� Header����������������������������� | ``` ``` ������ +-������������������������������������������������������������ -+ ``` ``` ������ |�������������������������������������������������������������� | ``` ``` ������ +-������������������������������������������������������������ -+ ``` ``` ������ |�������������������������������������������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` The error occurs when the slave sends a "duplicate" DD packet which is out of sequence with the LSA header exchange. The slave should send duplicate packets back to the master in sequence to acknowledge the DD exchange process. The error can also occur when the master has sent a new DD packet to the slave which falls out of sequence with the slave's previously received packet sequence number. The master should increment the DD sequence numbers sequentially.{#SPAN20727463} | | OSPF IO: Options mismatch in Loading/Full | The options field describes the capabilities supported by the router. Two capabilities are currently defined. For example, the ExternalRoutingCapability (below called the E-bit) has meaning only in OSPF Hello Packets. Routers should reset (i.e. clear) the unassigned part of the capability field when sending Hello packets or Database Description packets and when originating link state advertisements. This error would be triggered by a mismatch in capabilities advertised and would likely be caused by misconfigurations on one or both sides of the adjacency. | | OSPF IO: x-\>x received OSPF packet on passive | OSPF routing information should neither be sent nor received on an interface when in passive mode. This message indicates that an OSPF packet was indeed received on a passive interface and thus triggers a harmless error message. | | OSPF IO: Not duplicate in Loading/Full for xxx | A new LSA describing a previous unknown network should be learned in the Exchange state, not in Loading or Full. Once learned, the LSA header is stored in the router's link state database. This error condition is triggered when a Link State Request for an unknown network is received in Loading or Full states, but the header was not previously loaded into the link state database. | | OSPF IO: xx Type-7 LSA in non NSSA area LSA | Link State Update (LSU) packets implement the flooding of link state advertisements. Each Link State Update packet carries a collection of link state advertisements one hop further from its origin. Several link state advertisements may be included in a single packet. In order to make the flooding procedure reliable, flooded advertisements are acknowledged in Link State Acknowledgment packets. Redistribution into an NSSA area creates a special type of link-state advertisement (LSA) known as type 7, which can only exist in an NSSA area. An NSSA autonomous system boundary router (ASBR) generates this LSA and an NSSA area border router (ABR) translates it into a type 5 LSA, which gets propagated into the OSPF domain. This error indicates that a type 7 LSA was received in a non-NSSA area. | | OSPF IO: xx Summary LSA in totally stubby area LSA | A totally stubby area is only connected to the backbone area. A totally stubby / totally stub area does not advertise the routes it knows. It does not send any Link State Advertisements. The only route a totally stub area receives is the default route from an external area, which must be the backbone area. This default route allows the totally stub area to communicate with the rest of the network. This error is triggered when a summary route is received in a totally stubby area; total stubs should only receive default routes (stubs can receive summary routes). | | OSPF IO: received # byte runt Hello packet from xxx | The Hello Protocol is responsible for establishing and maintaining neighbor relationships. It also ensures that communication between neighbors is bidirectional. Hello packets are sent periodically out all OSPF-enabled router interfaces. Bidirectional communication is indicated when the router sees itself listed in the neighbor's Hello Packet. The Hello Packet contains the router's Router Priority (used in choosing the Designated Router), and the interval between Hello Packets sent out the interface (Hello Interval). The Hello Packet also indicates how often a neighbor must be heard from to remain active (Router Dead Interval). **The Hello packet format looks like this:** ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�� Version #�� |������ 1������ |�������� Packet length�������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |������������������������� Router ID��������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�������������������������� Area ID���������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |���������� Checksum����������� |������������ AuType����������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |���������������������� Authentication������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |���������������������� Authentication������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |����������������������� Network Mask�������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�������� HelloInterval�������� |��� Options��� |��� Rtr Pri��� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |�������������������� RouterDeadInterval����������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |��������������������� Designated Router����������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |������������������ Backup Designated Router������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` ``` ������ |������������������������� Neighbor���������������������������� | ``` ``` ������ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ``` The cause of this error is a corrupted Hello packet received, which may be truncated. The OSPF packet header contains the length of the packet, if there is a mismatch between the reported and actual size, this error will be triggered. | | OSPF IO: Hello duplicate router ID on interface xx(xx) | The router ID uniquely identifies a router within an OSPF domain. The error here indicates a router ID collision. | | OSPF IO: Hello interval mismatch on interface xx(xx) got # expected # | This error is triggered when the Hello interval announced is not the same as the receiving router's Hello interval. | | OSPF IO: Router dead interval mismatch on interface xx(xx) got # expected # | This error is triggered when the Router Dead Interval announced is not the same as the receiving router's Dead Interval. | --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content