Community discussions

MikroTik App
 
midsizewisp
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 55
Joined: Tue Dec 08, 2009 10:34 pm

v7.1.1 OspfNeighbor received wrong LS Ack

Tue Feb 08, 2022 4:55 pm

I'm getting "OspfNeighbor { router-id: X.X.X.X state: Full } received wrong LS Ack" in my v7.1.1 routers from my v6.48.6 routers.
It seems like restarting the OSPF instance on the v6 routers fixes it for a while.

Any idea what is causing this?
 
mhugo
Member Candidate
Member Candidate
Posts: 179
Joined: Mon Sep 19, 2005 11:48 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Feb 15, 2022 4:49 pm

We even got this between a 7.1.1 and 7.1 today. Only visible in the 7.1 router.
 
mlab
just joined
Posts: 1
Joined: Tue Feb 15, 2022 6:24 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Feb 15, 2022 6:50 pm

Yeah, same issue here ... we have a mikrotik only OSPF with about 40 switches and the logs get spammed a lot. All running 7.1.1

There is 7.1.2 now, but there is no mention of solving this issue ....
 
stavros54cy
just joined
Posts: 2
Joined: Mon Feb 21, 2022 2:37 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon Feb 21, 2022 2:40 pm

Hello there

I have set up a GNS3 lab with only 7.1.2 cloud hosted routers and I am facing the same issue

Did you manage to resolve this?
 
sette
just joined
Posts: 18
Joined: Mon Mar 12, 2012 11:53 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Mar 22, 2022 10:43 am

Hello,
any news regarding this problem?
I've tried 7.1.3 and it's still present. Is somehow related to BFD?

thank you
 
stavros54cy
just joined
Posts: 2
Joined: Mon Feb 21, 2022 2:37 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Mar 22, 2022 10:58 am

Hello In my case in the VM lab I had to upgrade and restart the VM host.

After that I have not experienced the same
 
Flyerman
just joined
Posts: 2
Joined: Mon May 02, 2022 8:31 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon May 02, 2022 8:35 am

We have same problem. Very simple OSPF setup, 3x v6 routers, 1x v7 (now 7.3beta37)

On the v7 route OSPF fails with the same error "ignoring LS Ack - wrong neighbor state" , sometimes after few seconds, sometimes 5-10 minutes..

BFD on v6 is enabled.
 
aoxiangtianji
just joined
Posts: 2
Joined: Fri Jun 03, 2022 5:25 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Sat Jun 04, 2022 6:13 am

Same problem here...
 
User avatar
UplinkLLC
just joined
Posts: 12
Joined: Sun May 15, 2022 7:29 am
Location: USA

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Sat Jun 04, 2022 11:32 pm

Hello,

We had the same problem where V7 routers were getting hammered by LS ACK messages.

What fixed it for us was to upgrade adjacent V6 routers to V7. We have 40 routers in our network and have now upgraded half of them running V7.2.3. So far everything is working well.

We also turn off BFD on V6 routers OSPF interface that connect to V7 routers. Be aware that if you are using OSPF and NAT on the same V7 router you need to disable connection tracking for OSPF.

Not suggesting that you do any of that, but that is what works for us.

Regards,
 
bozallen
just joined
Posts: 3
Joined: Fri May 27, 2022 7:28 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Wed Jul 06, 2022 3:24 am

This still appears to be an issue in routeros 7.3.1. I'm trying to form an OSPF adjacency from a CCR2116-12G-4S+ running 7.3.1 to a CCR1036-8G-2S+ running 6.47.10 or 6.45.9. The adjacency gets stuck in the 'Exchange' state and the ROS7 box constantly reports "received wrong LS Ack for..." Any news on when this will be resolved?
 
wtechlink
just joined
Posts: 11
Joined: Tue Mar 03, 2020 3:09 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Thu Jul 21, 2022 11:00 pm

I'm seeing the same error every time a client disconnects from the PPPOE server on the router. Only happens on RouterOS7. Currently using 7.2.3. Most of my OSPF network is still running ROS6, only seeing the error on the router with ROS7

I will try updating to 7.4 later tonight and see if that resolves the issue or not.
 
User avatar
gilljr
newbie
Posts: 49
Joined: Thu Nov 15, 2012 10:47 pm
Location: Phoenix, AZ USA
Contact:

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Wed Aug 17, 2022 1:18 am

I am running v7.4.1 and I am seeing this on a link to a router running v6.47.9. I added a second link between the routers and I am getting the same error on the secondary link.
 
marcbou
just joined
Posts: 13
Joined: Tue Jul 03, 2018 11:19 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Sun Aug 28, 2022 1:31 pm

Hey Mikrotik could we please get an answer on this?
 
User avatar
nichky
Forum Guru
Forum Guru
Posts: 1235
Joined: Tue Jun 23, 2015 2:35 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon Aug 29, 2022 8:19 am

on my case moving to v7.4.1 fixed the issue
 
ultimus247
just joined
Posts: 8
Joined: Tue Jul 03, 2012 12:20 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Sep 02, 2022 11:29 pm

Im preparing to upgrade my companies network from 6.49.6 to 7.5 but we cannot do this without showing the transition will be smooth.
In our test lab Im upgrading a single router to 7.5 and connecting over a GRE tunnel. When I do this our OSPF doesnt work like it does from 6.x to 6.x.
We initially get the routes: state Change to Full
We see all routes for a split second and then we then receive these errors on the 7.5 router: received wrong LS Ack for inter-area-prefix 10.10.0.0 10.10.9.14 0x80000006 expected 0x80000007.
This then brings DOWN the gre tunnel entirely, which is very interesting as without OSPF the tunnel is stable.
After this the gre tunnel comes back online and we start the loop again.
 
hjoelr
newbie
Posts: 38
Joined: Mon Apr 28, 2008 11:29 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Dec 16, 2022 10:57 pm

We see all routes for a split second and then we then receive these errors on the 7.5 router: received wrong LS Ack for inter-area-prefix 10.10.0.0 10.10.9.14 0x80000006 expected 0x80000007.
This then brings DOWN the gre tunnel entirely, which is very interesting as without OSPF the tunnel is stable.
After this the gre tunnel comes back online and we start the loop again.

You probably already got this figured out, but it sounds like OSPF is installing a route for your external IPs to go across the tunnel. The moment the routes get installed, your routers start sending your tunnel management traffic across the tunnel. You need to filter out the external IPs of the tunnel from OSPF using a Route Filters. You can see my related post about this over here: viewtopic.php?p=961905
 
sep
newbie
Posts: 25
Joined: Thu Nov 28, 2013 2:34 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Thu Jan 19, 2023 1:20 pm

did anyone figure out the proper fix for this ? i see it on CCR2216 running 7.7 with 3 CCR's in a triangle.
 
MitchelBraybh
just joined
Posts: 3
Joined: Tue Jan 24, 2023 9:58 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Feb 14, 2023 12:41 pm

The OSPF setup is straightforward, consisting of three v6 routers and one v7 (currently 7.3beta37). However, the v7 router experiences an OSPF failure with the error message "ignoring LS Ack - wrong neighbor state," occurring intermittently, ranging from a few seconds to 5-10 minutes. BFD is enabled on the v6 routers.
 
sjmudd
just joined
Posts: 9
Joined: Mon Dec 03, 2018 9:19 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Sat Jun 03, 2023 1:01 pm

7.9.1 gave me a lot of issues with this lsack issue. I've seen 7.9.2 released and the problem seems to have gone away. Was only affecting 1 device a RB951G-2HnD but made it unusable. Release notes don't mention anything related so maybe this was just luck
 
cvalenzuela
just joined
Posts: 1
Joined: Fri Jul 21, 2023 9:30 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Jul 21, 2023 9:52 pm

Hello,

I am upgraded to firmware version 7.10.2 and am receiving same warning. Is there any insight as to what might be causing this?


default-v2 { version: 2 router-id: 192.168.0.2 } ospf-area-2.0.2.2 { 2.0.2.2 } interface { p2p x.x.x.x%vlanxxx1 } neighbor { router-id: x.x.x.x state: Full } received wrong LS Ack for router 192.168.0.2 192.168.0.2 0x80003214 expected 0x80003215

I have multiple OSPF routes but this is the only one giving me this warning state
 
essam
just joined
Posts: 1
Joined: Tue Aug 29, 2023 2:01 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Aug 29, 2023 2:23 pm

The same here ,I'm faceing the same issue on CCR 2116 With V 7.11 is connected to other routers (CCR2116 V 7.10.2 and CCR 1009 V 6.49.3 etc ...)
the log is : route ospf warning ospf-instance-1 { version: 2 router-id: x.x.x.x } ospf-area-1 { 0.0.0.0 } interface { broadcast x.x.x.x%vlan.21 } neighbor { router-id: x.x.x.x state: Full } received wrong LS Ack for network xx.x.x x.x.x.x 0x80000001 expected 0x80000004

no diffrence when we using Network type:ptp or Broadcast
can anyone give a hand or consider this issue an bug in V7
 
pmsfm
just joined
Posts: 3
Joined: Fri Jul 14, 2023 4:01 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Thu Sep 07, 2023 11:36 am

Hi all,

I'm also getting these errors between 7.10.2 and 6.48.6 routers. Is there any further information regarding these OSPF messages please?

"default { version: 2 router-id: 10.1.100.150 } 10 { 0.0.0.10 } interface { p2p 10.1.1.173%ether8 } neighbor { router-id: 10.1.100.151 state: Full } received wrong LS Ack for inter-area-prefix 100.67.12.0 10.1.100.150 0x80000014 expected 0x80000015"

Many Thanks
 
User avatar
Joni
Member Candidate
Member Candidate
Posts: 156
Joined: Fri Mar 20, 2015 2:46 pm
Contact:

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Sep 26, 2023 8:49 am

Bumpbump, on between any 7.11.2.
default-v2 { version: 2 router-id: x.x.x.13 } backbone { 0.0.0.0 } interface { p2p x.x.x.13%l2tp-x} neighbor { router-id: x.x.x.254 state: Full } received wrong LS Ack for router x.x.x.13 x.x.x.13 0x80000382 expected 0x80000383
(the so called +1 , 2 -> 3)
 
User avatar
Joni
Member Candidate
Member Candidate
Posts: 156
Joined: Fri Mar 20, 2015 2:46 pm
Contact:

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Sun Oct 08, 2023 2:25 pm

Bumpbump, on between any 7.11.2.
default-v2 { version: 2 router-id: x.x.x.13 } backbone { 0.0.0.0 } interface { p2p x.x.x.13%l2tp-x} neighbor { router-id: x.x.x.254 state: Full } received wrong LS Ack for router x.x.x.13 x.x.x.13 0x80000382 expected 0x80000383
(the so called +1 , 2 -> 3)

Responding to myself... ymmv, masqurade / nat seems to cause this (internal interfaces). Probably shouldn't, quite certainly a default type of logic bug.

Referenced here (without the +1 "received wrong LS Ack for router" keywords, why it can't be found, crossposting):
NAT killing OSPF
 
User avatar
vmiro
Frequent Visitor
Frequent Visitor
Posts: 79
Joined: Sun Jan 29, 2006 6:53 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Wed Oct 11, 2023 11:34 pm

Bumpbump, on between any 7.11.2.
default-v2 { version: 2 router-id: x.x.x.13 } backbone { 0.0.0.0 } interface { p2p x.x.x.13%l2tp-x} neighbor { router-id: x.x.x.254 state: Full } received wrong LS Ack for router x.x.x.13 x.x.x.13 0x80000382 expected 0x80000383
(the so called +1 , 2 -> 3)

Responding to myself... ymmv, masqurade / nat seems to cause this (internal interfaces). Probably shouldn't, quite certainly a default type of logic bug.

Referenced here (without the +1 "received wrong LS Ack for router" keywords, why it can't be found, crossposting):
NAT killing OSPF
Not for me. I'm using MT as a VPN concentrator and I don't have NAT configured and still receiving "wrong LS Ack" messages :(
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon Nov 13, 2023 4:10 am

So did anybody actually log a support case with MikroTik?

https://mikrotik.com/support
Last edited by oeyre on Mon Nov 13, 2023 5:50 am, edited 1 time in total.
 
User avatar
Joni
Member Candidate
Member Candidate
Posts: 156
Joined: Fri Mar 20, 2015 2:46 pm
Contact:

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon Nov 13, 2023 5:13 am

You funny. If they don't understand to enrich insight from their own user-base forum and want to hide the revelation process in private tickets then they may suffer their own ignorance. It's not like they would need to worry about competitive advances leaking on a proprietary platform. It's not like they're actually listening, so why bother. Just like with Microsoft, the answers never arrive from the manufacturers in their ivory towers.
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Mon Nov 13, 2023 6:06 am

@Joni, its almost as if the MikroTik community forums aren't an official tech support method hey?

MikroTik have stated several times that they don't monitor this forum closely as its a user forum for users to discuss amongst each other. Maybe you have noticed that when MikroTik staff do participate in the forums, they will encourage people having bugs or other misbehaviours to log a support case?

Even if they did see this thread I am curious how you think they are supposed to solve it when nobody has shared any particularly detailed information about their setup or what they are seeing, let alone a supout file (one of the first steps of logging a support case).

So if you just want to sit around and feel sorry for yourself that's fine and you have my sympathy. But its been nearly 2 years doing the same thing without any results, so maybe its time to try another way?

BTW to add something productive to the discussion: I am having the same issue with CCR1036 running 7.12 (also seen in 7.11 and 7.10) speaking OSPF with CCR1036 running 6.48.6

While the OSPF adj does form, I get the following log message:
default-v2 { version: 2 router-id: 10.200.199.131 } area10-v2 { 0.0.0.10 } interface { p2p 172.23.253.9%VLAN18 } neighbor { router-id: 10.200.199.130 state: Full } received wrong LS Ack for router 10.200.199.131 10.200.199.131 0x80001186 expected 0x80001187
I have firewall filter rules but no NAT. Connection tracking was auto, however no change when I set to no.

I will advise the case ref when I log it.
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Nov 17, 2023 9:22 am

SUP-134528 logged, comments from MikroTik as follows:

Regarding "received wrong LS Ack for external"
Thank you for the report. It is cosmetical bug and does not influence OSPF working. It is reported to our specialists but currently I can't provide ETA.
Regarding similar messages but for "received wrong LS Ack for router"
If there is ROS version on v6 on one router and v7 - on the second side and adjacency is formed - then yes, it is same issue.
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Nov 17, 2023 9:23 am

You're welcome.
 
User avatar
vmiro
Frequent Visitor
Frequent Visitor
Posts: 79
Joined: Sun Jan 29, 2006 6:53 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Fri Nov 17, 2023 1:19 pm

Great, thanks for the info ;)
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Nov 28, 2023 1:08 pm

No word via the support ticket yet, but this looks interesting...

viewtopic.php?t=201465&start=300#p1038543
What's new in 7.13beta3 (2023-Nov-24 13:52):
...
*) ospf - fixed LSA Type3 advertisement for OSPFv2;
 
oeyre
Member Candidate
Member Candidate
Posts: 134
Joined: Wed May 27, 2009 12:48 pm

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Tue Nov 28, 2023 1:23 pm

I loaded this onto a CCR in my test setup...

Before I was getting "wrong LS ack for router" messages. After upgrading I am still getting those and now also "wrong LS ack for opaque-area".

I am only getting "wrong LS Ack for external" in my live network, so can't confirm if those are fixed just yet.
 
User avatar
NetHorror
just joined
Posts: 19
Joined: Fri Dec 06, 2013 8:12 am

Re: v7.1.1 OspfNeighbor received wrong LS Ack

Thu Dec 07, 2023 11:15 pm

still has the same issue...

received wrong LS Ack for router

7.13rc3

Who is online

Users browsing this forum: manish and 6 guests