It only happens at CCR. The other routers are with the same number of routers neighbors does not have it. But the difference is that each route is linked at one interface. The CCR use one ether for all the internal network.
I’m experiencing the same problem on CCR1016 when disabling ND on interfaces or after removing IP addresses from interfaces - at least since v6.23. Correspondence with MT support did not result in a solution or even acknowledgment of the problem.
Thanks again! It happens with things that change on route table. It is really strange because crash all routes and increase cpu. Other changes is okay!
Now I found out the problem. It is like a loop after a router come off. The ospf goes crazy and cpu really high. Then all the routes falls and comes up after this. I have a summarized area for pppoe clients. I am using ptp as network type on ospf.
I have 6 router in one ether out for a switch. The adjacency stay for days until this type of loop.
How can I solve it? I changed the summarized are to stub and I will try today to use nbma instead.
Thanks
How many PPPoE sessions do you have and is each one creating an OSPF route?
One thing we had to do when load testing the CCR1072 for PPPoE stability was disable the IPv6 package. Once we did that, we were able to go from 5000 PPPoE sessions to 30,000 PPPoE sessions.
There is some kind of Layer 2 issue in the IPv6 package that limits the performance of IPv4 PPPoE. This may not solve your specific problem, but I would disable IPv6 during the troubleshooting process just to simplify.
Thanks again for your help. I am no advertising the pppoe network in OSPF to reduce the interfaces in it.
I am running in this RouterOS BGP peers in the server. Do you think is is the problem to recalculation drop the OSPF?
I am setup a new RouterOS for BGP, firewall and OSPF to connect to authentication server. I will turn the main RouterOS to authentication server only with OSPF with this new serve on the border.
By default max ipv6 neighbors are set to 1024 which may cause trouble with large number of clients. You can try to increase this limit in “/ipv6 settings” menu.
Thanks MRZ, we actually increased this value after opening a ticket with MT and set it to 100,000 neighbors but we still did not see significant PPPoE performance gains until we disabled the IPv6 package entirely.