We have 3 1072's in a live environment with no reboot issues, albeit with low traffic levels.What realistically can you do before you notice issues? I have issues with the 1072's where they randomly reboot and the watchdog triggers. Maybe 1 time a week or less. No pattern to it and the supout shows nothing.
is time to test using the new V7 beta 8Same here, around 30 CCRs 1072&1036 in production, around 5Gbps in peak, no reboot issues...
Have you tried with disabled connection tracking?You can reach 80gbps of unrealistic traffic with a 1072, but with real traffic, it begins to lost packets with a fraction of the max throughput.
We have route cache disabled on IPv4, what issues has it introduced that has caused you problems?The only way I found to be able to handle SYN Flood attacks, was to disable Route Cache (which introduces other problems though...)
Released a new beta RouterOS 7. Try it on it, maybe something has changed?I did try with up to 50 threads, still same results
Yeah, I've seen that as well on some versions of 6.x long term stable on our CCR 1072.Some of us need to use nat for particulars so we need to keep connection tracking on. Even with a light amount of connection tracking it crashes weekly on our 1072's. Some of our 1072's with it disabled still randomly watchdog reboot. It all started a few versions back.
we did some throughput tests with the CCR2004 - running 6.48b12. it actually performed quite well, we were able to reach peak ipv4 routing throughput of 32Gbps with just 8 streams. as for ipv6, the picture is a bit different...Probably you have to generate far more sessions in order to see the other cores working.
If only there was IPv6 fastpath....we did some throughput tests with the CCR2004 - running 6.48b12. it actually performed quite well, we were able to reach peak ipv4 routing throughput of 32Gbps with just 8 streams. as for ipv6, the picture is a bit different...Probably you have to generate far more sessions in order to see the other cores working.
well since there were no rules in firewall, it had the lightest load possible - basically packet forwarding along connected routes.If only there was IPv6 fastpath....
I'll look forward to itwell since there were no rules in firewall, it had the lightest load possible - basically packet forwarding along connected routes.If only there was IPv6 fastpath....
in terms of PPS it is pretty much understandable you will always get subpar results compared to IPv4. the header size is twice big, so it takes at best twice the time to parse it. but no worries on that, as most other vendors have their v6 performance halved compared to IPv4 forwarding rate. initial impressions from the short test are below.
with bridging on multiple ports (8) we got 950000 per port-pair per direction, so altogether 7.6Mpps.
on a single port pair we could get 3.2Mpps/direction = 6.4Mpps
IPv4 results were 10.4Mpps and 4.2Mpps respectively.
IPv6 numbers were far behind, such as 1.63Mpps and 1.3Mpps.
clearly IPv4 results leave everything else behind. surprisingly the cpu util was kind of balanced almost all the time.
we'll post the finished full test results on yt soon.
Hello,Here is CPU usage from my ccr2004 router.. 6.47 and ~1M routes
The graph looks like it's rrdtool. Many monitoring systems use it. OpenNMS, LibreNMS, Cacti, Observium, ...What graphing software do you use?
Hello,Here is CPU usage from my ccr2004 router.. 6.47 and ~1M routes
What graphing software do you use?
Thanks, hero1c
Im also interested in issues caused by disabling route cache and using BGPWe have route cache disabled on IPv4, what issues has it introduced that has caused you problems?The only way I found to be able to handle SYN Flood attacks, was to disable Route Cache (which introduces other problems though...)
Hello.BGP Benchmarks are much better with a lower amount of routes :
1 Full (800k routes):
* Insertion : 47 seconds
* Removal : 7 seconds
2 Full (1,6M routes):
* Insertion : 1 minute 9 seconds
* Removal : 39 seconds
3 Full (2,4M routes) :
* Insertion : 1 minute 29 seconds
* Removal : 3 minutes
4 Full (3,2M routes) :
* Insertion : 1 minute 51 seconds
* Removal : 7 minutes 30 seconds
For the bandwidth tests, i don't have much stuff at home, i will try but i can't guarantee anything :)