Yeah, it was a firmware update that made it show up in the logs for us too. In our setup, each OSPF instance is inside its own vlan running a public /30. We've got one CCR with two ports in a bridge, each port going to a 24 port edge switch. The CCR has multiple OSPF peers and all are throwing the error. Our router ID's are not 0.0.0.0.
Robbie Wright Siuslaw Broadband <https://siuslawbroadband.com> 541-902-5101 On Wed, Dec 14, 2016 at 6:23 AM, Dan Harling via Mikrotik-users < [email protected]> wrote: > Duplicate router ID causes a different message--and no small amount of > routing table instability. (Don't ask how I know.) IIRC, this > message specifies the same MAC as the interface receiving it. So it > seems to be a L2 message not related to IP. As I said, we never saw > it prior to a recent ROS update. > > An OSPF router ID of 0.0.0.0 will use the "lowest IP address > configured on an active interface," according to the ROS Wiki. Which > makes OSPF precisely as stable as your lowest-IP interface. > > > > On Wed, Dec 14, 2016 at 8:49 AM, Scott Reed via Mikrotik-users > <[email protected]> wrote: > > My experience is that has almost always been a configuration error. > Often > > related to Router ID, but not necessarily the one reporting the errors. > > > > One thing MT appears to not like is Router ID of 0.0.0.0. > > > > Duplicate IP addresses can cause this message. The packet actually came > > from somewhere else, but looks like it is local. > > > > I am sure there are some other common things, but it has been a while > since > > I was dealing with this error message. > > > > > > > > On 12/14/2016 7:24 AM, Dan Harling via Mikrotik-users wrote: > > > > Some of our routers report this same "locally originated" OSPF message > > every few minutes. It's nothing close to "blowing up" the logs, but > > troubling nonetheless. And yes, it didn't start happening until we > > upgraded, probably to 6.36.x. Just another data point. > > > > Daniel Harling <>< > > Engineering, Cape Ann Communications > > 183 Main Street, Gloucester, MA 01930 > > [email protected] > > > > > > On Wed, Dec 14, 2016 at 1:12 AM, Robbie Wright via Mikrotik-users > > <[email protected]> wrote: > > > > Yeah, that's how we have it set. Each router has a unique router ID. Our > > main router has one ID, but has a dozen or so ospf neighbors. We've been > > running this setup for quite a while. Doesn't seem like we saw it until > an > > upgrade a while back. We do have a loop in our network, on purpose, that > > OSPF routes around for primary and redundant. However, all of the IP's > that > > are showing in the logs aren't part of the ring. They are all legs/stubs > of > > the ospf, not anything to do with the ring. > > > > > > Robbie Wright > > Siuslaw Broadband > > 541-902-5101 > > > > On Tue, Dec 13, 2016 at 9:30 PM, Faisal Imtiaz <[email protected] > > > > wrote: > > > > Each router should have a unique router ID > > > > typically, best practice, is to take an IP Address (unique) and assign it > > to the Loopback interface ( a dummy bridge interface) and use that a > router > > id in your OSPF instance.. > > > > irrespective of how many interfaces you have running OSPF, only one > unique > > router id is required. > > > > > > --------- > > is it possible that you have created a loop where you are seeing the > > packets from the router it-self ? > > > > > > Regards. > > > > > > Faisal Imtiaz > > Snappy Internet & Telecom > > 7266 SW 48 Street > > Miami, FL 33155 > > Tel: 305 663 5518 x 232 > > > > Help-desk: (305)663-5518 Option 2 or Email: [email protected] > > > > ________________________________ > > > > From: "Robbie Wright via Mikrotik-users" <[email protected]> > > To: "Mikrotik Users" <[email protected]> > > Sent: Tuesday, December 13, 2016 11:50:36 PM > > > > Subject: Re: [Mikrotik Users] OSPF errors on router > > > > I saw this issue pop up again. The duplicate router ID thing caught me. > > We've got a main tower that has a vlan to a dozen other sites, each > > running an MT with OSPF. Each vlan has a ptp ospf interface, not > broadcast, > > with a unique /30 public IP space. We only run one instance of OSPF on > our > > main tower router, with only one router ID. > > > > I'm thinking maybe the one router ID across all the vlans is causing the > > issue? Functionally, everything is working fine. But our logs are > blowing up > > with the "Discarding packet: locally originated" error. > > > > > > Robbie Wright > > Siuslaw Broadband > > 541-902-5101 > > > > On Thu, Sep 17, 2015 at 10:07 AM, Steve Barnes <[email protected]> wrote: > > > > Justin I think I have followed all those steps. I am using 6.29 > > exclusively. Is there issues with that release? > > > > > > > > Steve Barnes > > > > General Manager > > > > PCSWIN.COM > > > > Howard Power Performance > > > > > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Justin Wilson - > MTIN > > Sent: Thursday, September 17, 2015 12:47 PM > > > > > > To: Mikrotik Users <[email protected]> > > Subject: Re: [Mikrotik Users] OSPF errors on router > > > > > > > > > > Some things to make sure of before banging your head. > > > > > > > > 1.Make sure *every* router participating in OSPF is on the same OS > > version. They don’t have to be the latest greatest, just the same. one > > router in a pool of 50 can taint the database. Even if it’s one version > > behind of ahead. > > > > > > > > 2.Make sure your loopback IP addresses (you are using loopbacks correct?) > > are listed as the router ID. > > > > > > > > 3.If these are true point-to-point backhauls change the OSPF type to PTP. > > This cuts down on the chatter on the link. Once OSPF establishes a > session > > it stops talking as much as if it were in broadcast mode. > > > > > > > > 4.Double check your IPs and subnet masks. > > > > > > > > 80some% of the OSPF issues I see are a result of mismatched router OS > > versions. Bringing everything to the same version solves a ton of issues. > > > > > > > > Justin Wilson > > > > [email protected] > > > > > > > > --- > > http://www.mtin.net Owner/CEO > > > > xISP Solutions- Consulting – Data Centers - Bandwidth > > > > http://www.midwest-ix.com COO/Chairman > > > > Internet Exchange - Peering - Distributed Fabric > > > > > > > > On Sep 17, 2015, at 8:25 AM, Steve Barnes <[email protected]> wrote: > > > > > > > > Not completely. Not sure we don’t have a small Comm issue to a backhaul. > > However the outages have gone away just get 2-3 errors a day but it is > not > > causing any OSPF issues or outages. Thinking of just adding a Filter > rule > > to block them and go on with life. > > > > > > > > Steve Barnes > > > > General Manager > > > > PCSWIN.COM > > > > Howard Power Performance > > > > > > > > From: [email protected] > > [mailto:[email protected]]On Behalf Of Mike Hammett > > Sent: Thursday, September 17, 2015 8:14 AM > > To: Mikrotik Users <[email protected]> > > Subject: Re: [Mikrotik Users] OSPF errors on router > > > > > > > > Did you figure this out? > > > > > > > > ----- > > Mike Hammett > > Intelligent Computing Solutions > > http://www.ics-il.com > > > > > > > > ________________________________ > > > > From: "Steve Barnes" <[email protected]> > > To: "Mikrotik Users ([email protected])" > > <[email protected]> > > Sent: Thursday, September 3, 2015 11:57:17 AM > > Subject: [Mikrotik Users] OSPF errors on router > > > > I am getting the attached errors in my event log on one tower. No ports > > are flapping on the backhaul. Both Mikrotiks are on 6.29. Both routers > CPU > > is <10%. As soon as this error passes they will work 100% for hours, > even > > days. I am confused and lost. PTP conection was Broadcast and have > changed > > to point to point. What to look at? > > > > > > > > <image001.jpg> > > > > > > > > > > > > Steve Barnes > > > > General Manager > > > > PCSWIN.COM > > > > Howard Power Performance > > > > > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > > > _______________________________________________ > > Mikrotik-users mailing list > > [email protected] > > http://lists.wispa.org/mailman/listinfo/mikrotik-users > > > > > > -- > Daniel Harling <>< > Engineering, Cape Ann Communications > 183 Main Street, Gloucester, MA 01930 > [email protected] > _______________________________________________ > Mikrotik-users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/mikrotik-users >
_______________________________________________ Mikrotik-users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/mikrotik-users
