Tnx for getting back aldo this is kind of off of the topic.
do you get same behavior in 4.13 as there where some serious bugs fixed.
Other idea is to introduce areas in your OSFP network.
4.13 is the version I’m running at this point. I was hoping the problem will go away with it, but it’s still there.
And I am running multiarea network and this issue is showing only on versions above 4.3 and only within backbone as far as I see.
13:37:07 route,ospf,error Discarding packet: locally originated
13:37:07 route,ospf,error src address=172.16.0.212
13:39:10 route,ospf,error Discarding packet: locally originated
13:39:10 route,ospf,error src address=172.16.0.212
13:39:15 route,ospf,error Discarding packet: locally originated
13:39:15 route,ospf,error src address=172.16.0.212
13:39:20 route,ospf,error Discarding packet: locally originated
13:39:20 route,ospf,error src address=172.16.0.212
13:39:25 route,ospf,error Discarding packet: locally originated
13:39:25 route,ospf,error src address=172.16.0.212
13:39:35 route,ospf,error Discarding packet: locally originated
13:39:35 route,ospf,error src address=172.16.0.212
13:39:50 route,ospf,error Discarding packet: locally originated
13:39:50 route,ospf,error src address=172.16.0.212
I am however considering now a reply mrz proposed. It “holds the water”, kind of. To explain, I find that the only two routers that are not displaying such behavior are ones without wireless links. To quote what mrz pointed out in the manual:
in 802.11 wireless networks multicast packets are not always reliably delivered (read Multicast_and_Wireless for details); using multicast here can create OSPF stability problems;
Further in favor of mrz’s thesis, I mentioned earlier that the logs show packet discards during higher traffic. So we have a possible cause and a possible solution.
One thing does bother me. Why is it that I haven’t had these problems with earlier MT versions?
Well, janis and mrz … tnx for helping here. I will revert with results, as soon as I get them.
Regards to all!