Verify your time on the routers is the same. We sync to the national pool. 

Are these connected via a wireless link?  If so try using Point to Point. It is 
much more forgiving. 


--------------------------------
Tommy A.
Digitex.com

817.558.6230 V
817.558.1204 F

> On Oct 30, 2018, at 10:05 AM, Josh Luthman via Mikrotik-users 
> <mikrotik-users@wispa.org> wrote:
> 
> Yuck, really hoping to avoid any messy config like that =(
> 
> .122 is the remote router that's having issues sticking together with OSPF.  
> I got some debug log that can hopefully spark some ideas.
> 
> Oct/30/2018 10:59:21 route,ospf,info OSPFv2 neighbor 10.255.0.14: state 
> change from Exchange to 2-Way
> 
> Oct/30/2018 10:59:22 route,ospf,debug Deleting an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000370
> Oct/30/2018 10:59:22 route,ospf,debug Should form adjacency: yes, I am DR/BDR
> Oct/30/2018 10:59:22 route,ospf,debug     remoteID=10.255.0.14
> Oct/30/2018 10:59:22 route,ospf,debug Starting Database Description exchanges
> Oct/30/2018 10:59:22 route,ospf,debug     neighbor=10.255.0.14
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Database Description 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug OSPFv2 neighbor 10.255.0.14: state 
> change from 2-Way to ExStart
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Database Description <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug OSPFv2 neighbor 10.255.0.14: state 
> change from ExStart to Exchange
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Database Description 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Link State Request <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug Received Link State Request
> Oct/30/2018 10:59:22 route,ospf,debug     type=Network LSA
> Oct/30/2018 10:59:22 route,ospf,debug     id=192.149.254.122
> Oct/30/2018 10:59:22 route,ospf,debug     originator=10.255.0.14
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Link State Update 192.149.254.121 
> -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Database Description <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Link State Request 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Database Description 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Database Description <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug Retransmitting last Database 
> Description packet
> Oct/30/2018 10:59:22 route,ospf,debug     to=192.149.254.122
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Database Description 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Link State Update <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug LSA Update received: Installing and 
> flooding it
> Oct/30/2018 10:59:22 route,ospf,debug     header=Network LSA 
> id=192.149.254.122 originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:22 route,ospf,debug Installing an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:22 route,ospf,debug     old=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:22 route,ospf,debug Flooding an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:22 route,ospf,debug     area=backbone
> Oct/30/2018 10:59:22 route,ospf,debug Adding to neighbor's retransmit list
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:22 route,ospf,debug     neighbor=10.255.0.1
> Oct/30/2018 10:59:22 route,ospf,debug     number of retransmits=1
> Oct/30/2018 10:59:22 route,ospf,debug Deleting an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> 
> Oct/30/2018 10:59:22 route,ospf,debug RECV: Link State Update <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:22 route,ospf,debug LSA Update received: Installing and 
> flooding it
> Oct/30/2018 10:59:22 route,ospf,debug     header=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> Oct/30/2018 10:59:22 route,ospf,debug Installing an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> Oct/30/2018 10:59:22 route,ospf,debug     old=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002218
> Oct/30/2018 10:59:22 route,ospf,debug Flooding an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> Oct/30/2018 10:59:22 route,ospf,debug     area=backbone
> Oct/30/2018 10:59:22 route,ospf,debug Adding to neighbor's retransmit list
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> Oct/30/2018 10:59:22 route,ospf,debug     neighbor=10.255.0.1
> Oct/30/2018 10:59:22 route,ospf,debug     number of retransmits=2
> Oct/30/2018 10:59:22 route,ospf,debug SEND: Database Description 
> 192.149.254.121 -> 192.149.254.122 on ether4
> Oct/30/2018 10:59:22 route,ospf,debug Deleting an LSA
> Oct/30/2018 10:59:22 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002218
> 
> 
> Oct/30/2018 10:59:23 route,ospf,debug RECV: Link State Update <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:23 route,ospf,debug LSA Update received: Installing and 
> flooding it
> Oct/30/2018 10:59:23 route,ospf,debug     header=Network LSA 
> id=192.149.254.122 originator=10.255.0.14 seqnum=0x80000372
> Oct/30/2018 10:59:23 route,ospf,debug Installing an LSA
> Oct/30/2018 10:59:23 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000372
> Oct/30/2018 10:59:23 route,ospf,debug     old=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000371
> Oct/30/2018 10:59:23 route,ospf,debug Flooding an LSA
> Oct/30/2018 10:59:23 route,ospf,debug     lsa=Network LSA id=192.149.254.122 
> originator=10.255.0.14 seqnum=0x80000372
> Oct/30/2018 10:59:23 route,ospf,debug     area=backbone
> 
> 
> Oct/30/2018 10:59:23 route,ospf,debug SEND: Link State Acknowledgement 
> 192.149.254.121 -> 224.0.0.5 on ether4
> O
> Oct/30/2018 10:59:23 route,ospf,debug SEND: Hello 192.149.254.121 -> 
> 224.0.0.5 on ether4
> 
> Oct/30/2018 10:59:24 route,ospf,debug Recalculating all OSPFv2 intra-area 
> routes
> Oct/30/2018 10:59:24 route,ospf,debug Recalculating all inter-area routes
> Oct/30/2018 10:59:24 route,ospf,debug     summary-area=backbone
> Oct/30/2018 10:59:24 route,ospf,debug Recalculating AS-external routes
> Oct/30/2018 10:59:25 route,ospf,debug RECV: Hello <- 192.149.254.122 on 
> ether4 (192.149.254.121)
> Oct/30/2018 10:59:25 route,ospf,debug   received options: E
> 
> Oct/30/2018 10:59:27 route,ospf,debug RECV: Link State Update <- 
> 192.149.254.122 on ether4 (192.149.254.121)
> Oct/30/2018 10:59:27 route,ospf,debug LSA Update received: Installing and 
> flooding it
> Oct/30/2018 10:59:27 route,ospf,debug     header=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x8000221a
> Oct/30/2018 10:59:27 route,ospf,debug Installing an LSA
> Oct/30/2018 10:59:27 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x8000221a
> Oct/30/2018 10:59:27 route,ospf,debug     old=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> Oct/30/2018 10:59:27 route,ospf,debug Flooding an LSA
> Oct/30/2018 10:59:27 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x8000221a
> Oct/30/2018 10:59:27 route,ospf,debug     area=backbone
> Oct/30/2018 10:59:27 route,ospf,debug Adding to neighbor's retransmit list
> Oct/30/2018 10:59:27 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x8000221a
> Oct/30/2018 10:59:27 route,ospf,debug     neighbor=10.255.0.1
> Oct/30/2018 10:59:27 route,ospf,debug     number of retransmits=2
> Oct/30/2018 10:59:27 route,ospf,debug Deleting an LSA
> Oct/30/2018 10:59:27 route,ospf,debug     lsa=Router LSA id=10.255.0.14 
> originator=10.255.0.14 seqnum=0x80002219
> 
> 
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
> 
>> On Tue, Oct 30, 2018 at 10:57 AM, Tim Cailloux <t...@southern-internet.com> 
>> wrote:
>> This sounds familiar(ish).... I think I “fixed it” by setting up an EoIP 
>> tunnel and running OSPF inside. 
>> 
>> Tim
>> 
>>> On Tue, Oct 30, 2018 at 10:40 AM Josh Luthman via Mikrotik-users 
>>> <mikrotik-users@wispa.org> wrote:
>>> Both routers are using the NTP server here in the office (private address) 
>>> and the Tock public server as a secondary.
>>> 
>>> 
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>> 
>>>> On Tue, Oct 30, 2018 at 10:38 AM, Robert via Mikrotik-users 
>>>> <mikrotik-users@wispa.org> wrote:
>>>> time server sync?
>>>> 
>>>> On 10/30/18 7:33 AM, Josh Luthman via Mikrotik-users wrote:
>>>> > I have an rb750 and CCR1009 both with 6.34.4 and their latest firmware.  
>>>> > They'll match right up and then after 6-12 hours they refuse to talk 
>>>> > OSPF.  Once it "locks up" I'll get this constantly:
>>>> > 
>>>> > 10:07:24 route,ospf,info OSPFv2 neighbor 10.255.0.14 
>>>> > <http://10.255.0.14>: state change from Exchange to 2-Way
>>>> > 10:08:05 route,ospf,info OSPFv2 neighbor 10.255.0.14 
>>>> > <http://10.255.0.14>: state change from Exchange to 2-Way
>>>> > 10:08:05 route,ospf,info Ignoring Link State Acknowledgment packet: 
>>>> > wrong peer state
>>>> > 10:08:05 route,ospf,info     state=ExStart
>>>> > 10:08:46 route,ospf,info OSPFv2 neighbor 10.255.0.14 
>>>> > <http://10.255.0.14>: state change from Exchange to 2-Way
>>>> > 10:09:27 route,ospf,info OSPFv2 neighbor 10.255.0.14 
>>>> > <http://10.255.0.14>: state change from Exchange to 2-Way
>>>> > 
>>>> > Now if I go to the 10.255.0.14 router (this is a management address, the 
>>>> > OSPF network is public space) and simply disable and enable the OSPF 
>>>> > network, it comes right back - again for 6-12 hours.
>>>> > 
>>>> > Any ideas or suggestions?
>>>> > 
>>>> > Josh Luthman
>>>> > Office: 937-552-2340
>>>> > Direct: 937-552-2343
>>>> > 1100 Wayne St
>>>> > Suite 1337
>>>> > Troy, OH 45373
>>>> > 
>>>> > 
>>>> > _______________________________________________
>>>> > Mikrotik-users mailing list
>>>> > Mikrotik-users@wispa.org
>>>> > http://lists.wispa.org/mailman/listinfo/mikrotik-users
>>>> > 
>>>> _______________________________________________
>>>> Mikrotik-users mailing list
>>>> Mikrotik-users@wispa.org
>>>> http://lists.wispa.org/mailman/listinfo/mikrotik-users
>>> 
>>> _______________________________________________
>>> Mikrotik-users mailing list
>>> Mikrotik-users@wispa.org
>>> http://lists.wispa.org/mailman/listinfo/mikrotik-users
>> -- 
>> Tim Cailloux
>> Southern Internet -- Locally Owned and Operated
>> t...@southern-internet.com
>> (404) 406-9911
> 
> _______________________________________________
> Mikrotik-users mailing list
> Mikrotik-users@wispa.org
> http://lists.wispa.org/mailman/listinfo/mikrotik-users
_______________________________________________
Mikrotik-users mailing list
Mikrotik-users@wispa.org
http://lists.wispa.org/mailman/listinfo/mikrotik-users

Reply via email to