0% found this document useful (0 votes)
71 views

CCR Tuning in Infraestructure Use

This document discusses CCR tuning and infrastructure use in MikroTik RouterOS. It explains that RouterOS 6.19 and later versions improved performance on CCR devices by utilizing multiple CPU cores. Specifically, it introduced Fast Path to accelerate packet handling, optimized PPP to use multiple cores, and introduced FastTrack in 6.29 to improve connection tracking performance. The document recommends handling packets in isolation using Fast Path when possible for core infrastructure, while also handling flows when features like NAT or firewalls are needed.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views

CCR Tuning in Infraestructure Use

This document discusses CCR tuning and infrastructure use in MikroTik RouterOS. It explains that RouterOS 6.19 and later versions improved performance on CCR devices by utilizing multiple CPU cores. Specifically, it introduced Fast Path to accelerate packet handling, optimized PPP to use multiple cores, and introduced FastTrack in 6.29 to improve connection tracking performance. The document recommends handling packets in isolation using Fast Path when possible for core infrastructure, while also handling flows when features like NAT or firewalls are needed.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

CCR Tuning in

Infrastructure Use
By Alexander Neilson, UFONE
[email protected] | www.ufone.co.nz
Resources

• MikroTik RouterOS v6 Whats new?? 



http://mum.mikrotik.com/presentations/RU13/megis.pdf

• CloudCoreRouter and RouterOS v6.x Tips & Tricks



http://mum.mikrotik.com/presentations/RU14/megis.pdf

• FastTrack

http://www.mikrotik.com/download/share/FastTrack.pdf
What did we get in ROS 6?

• Fast Path

• Improved Queueing

• PPP MultiCore (from 6.8)

• RouterOS 6.19 (More about this later)

• FastTrack (from 6.29)


CCR vs x86
• Memory Limits - Gone

• Parallel Architecture

• Many Small Cores - Up to 72 in CCR’s to come

• Ports directly linked to core (Excl. CCR1009)

• So what does this mean for us?


Practicalities of CCR
Architecture
We have to take one of two approaches:

1. Handle packets in isolation

2. Handle flows

Both have their place but both need tuning


Handle Packets in Isolation

• This is our preferred approach to core


infrastructure

• Avoiding state exhaustion

• Core agnostic packet handling

• Fast Path (Maybe)


Fast Path
• Fast path shortens the path of the packets through
user space / software

• Very fast handling of compliant packets

• Critical structure underlying “Millions of Packets”


specs for CCR Products

• Tight Criteria
Fast Path

• http://wiki.mikrotik.com/wiki/Manual:Fast_Path
Fast Path Handlers

• RouterOS Handlers:
• http://wiki.mikrotik.com/wiki/Manual:Fast_Path

• There are still limitations inside these handlers

• Whats Missing?

- PPP

- VLAN
Fast Path Restrictions
• No Connection Tracking

• No Netflow

• No Firewall Rules

• No Interface Queues / Queues

• No VRF’s

This list is only some of the key restrictions


Fast Path Effect

• http://routerboard.com/CCR1036-12G-4S
PPP Optimisations (6.8)
• Starting in 6.8 Mikrotik made PPP operate on all
cores

• Making CCR much more effective as a PPP


Concentrator

• A single CCR1016 now handles potentially


thousands of connections

• Took a few versions to settle down



(I suggest 6.19+)
Mikrotik Comparison

• http://mum.mikrotik.com/presentations/RU14/megis.pdf
What’s so Important About
RouterOS 6.19?
Prior to 6.19 even
with conntrack
disabled the
packet reassembly
and disassembly
was still performed
Handle Flows

• Flow handling brings conntrack into play

• FastTrack (from 6.29)

• Needed for NAT / Stateful firewall


Fast Track (6.29)
• Fast Track - Fast Path for Connection Tracking

• Lab Test first (or dog food it heavily)

• Reports on the forums are suggesting 2.5-3x real


world improvement

• Restrictions the same as for Fast Path



(No PPP, No VLAN)
Fast Track Announcement
6.29RC20 Change Log
Any Questions?
Discussions?
Thank You
By Alexander Neilson, UFONE
[email protected] | www.ufone.co.nz

You might also like