The %OSPF-4-ERRRCV error message
indicates that an Open Shortest Path First (OSPF) router has received an
invalid OSPF packet. These are the possible causes:
The first three items in the list are the most common causes of the
%OSPF-4-ERRRCV error message, and are discussed
in more detail below.
There are no specific requirements for this document.
This document is not restricted to specific software and hardware
Technical Tips Conventions for more information on document
%OSPF-4-ERRRCV: Received invalid packet: mismatch area ID, from backbone area
must be virtual-link but not found from 22.214.171.124, Ethernet0
The router generating this message received an invalid OSPF packet on
Ethernet 0 from neighbor 126.96.36.199. The packet is invalid because its area ID
is area 0 (the backbone area). This implies that the receiving router's
Ethernet 0 interface is not in area 0. Note that the neighboring router, which
has its interface in area 0, won't display this message in its console logs.
Only the router whose interface is in an area other than area 0 generates the
To avoid these messages, make sure that both sides have the same area
ID by checking the network statement under OSPF in the router configuration.
For example, if the link 10.10.10.0/24 between two routers should be in area 1,
make sure the network statement on both routers includes this particular link
in area 1. The network command on both routers would look like this:
router ospf 1
network 10.10.10.0 0.0.0.255 area 1
%OSPF-4-ERRRCV: Received invalid packet: Bad Checksum from 188.8.131.52,
The router generating this message has received an invalid OSPF packet
on TokenRing0/0 from neighbor 184.108.40.206. The packet is invalid because the
OSPF checksum is incorrect. The cause of the bad checksum is difficult to
define. Some possible causes of the problem are:
A device between the neighbors, such as a switch, is corrupting the
The sending router's packet is invalid. In this case, either the
sending router's interface is bad, or the error is caused by a software
The receiving router is calculating the wrong checksum. In this case,
either the receiving router's interface is bad, or the error is caused by a
software bug. This is the least likely cause of this error
This problem can be difficult to troubleshoot, but you can start with
this solution. Cisco has found that this solution is effective in 90 percent of
cases. It is important to complete these steps in order:
Change the cable between the routers. In the previous example, this
would be the router that sends the bad packet (220.127.116.11) and the router
that complains about these bad packets.
If the previous step does not fix the problem, use a different port
on the switch in between the routers.
If the previous step does not fix the problem, connect the routers
directly using a crossover cable (whenever physical location allows). If you
receive no further messages, the switch is most likely corrupting the
If none of the above solves the problem, contact the
Technical Support and work with an engineer to look for a bug in the
Cisco IOS® Software, or for a possible Return
Material Authorization (RMA) for partial or full parts replacement.
%OSPF-4-ERRRCV: Received invalid packet: OSPF not enabled on interface
from 18.104.22.168, Serial0.100
The router generating this message received a packet from 22.214.171.124
on Serial0.100, but OSPF is not enabled on the Serial0.100 interface. This
message is only generated once for a non-OSPF interface.
This problem is rarely seen on a router. To solve this problem, make
sure OSPF is enabled on the interface. Try re-entering the network statement in
the router configuration. To verify if OSPF is enabled on the interface
mentioned above, type the following command:
R1#show ip ospf interface serial0.100
If OSPF is not enabled, either the command output will be empty or it
will say that OSPF is not enabled on the interface.
There could be a situation where the OSPF updates may be corrupted in
the Cisco 7500 Series router configured with OSPF, MPLS and CEF. IP routes are
temporarily deleted from the IP routing table and a loss of connectivity may
occur. This is due to Cisco bug ID
(registered customers only)
Upgrade your Cisco IOS to the latest IOS release.
The error %OSPF-5-ADJCHG: Process ID , Nbr [ip-address]
on GigabitEthernet 1/0/3 from FULL to DOWNis caused due to
Bidirectional Forwarding Detection (BFD) errors. BFD can potentially generate
false alarms-signaling a link failure when one does not exist.
The timers used for BFD are so intensive CPU cycle, or a brief interval
of data corruption or queue congestion could potentially cause BFD to miss
enough control packets to allow the detect-timer to expire. The Minimum
Transmit Interval, Minimum Receive Interval and Multiplier are recommended to
be set as 100 100 3 respectively. Configuring process-max-timer
50 is also recommended to prevent unpredictable CPU