Community discussions

just joined
Topic Author
Posts: 17
Joined: Tue Mar 15, 2011 3:03 am

/ip route print where ... slow

Fri May 31, 2013 3:35 pm

Hi All.

Is there any thoughts on the best way to investigate/check routing when feeding full BGP tables into a RB?

Using /ip route print where x.x.x.x in dst-address when trying to troubleshoot routing/route preference is a really slow and frustrating.

On my new CCR at least it gets locked to one CPU and doesn't impact the unit too much. What do most people do?

I am thinking about a BGP feed to a VM with OpenBGPd?

Just wondering what others do....
User avatar
Member Candidate
Member Candidate
Posts: 151
Joined: Fri Oct 16, 2015 10:09 am
Location: Johannesburg, South Africa

Re: /ip route print where ... slow

Mon Aug 26, 2019 4:47 pm

I tip which doesn't seem to stand out is to enclose the prefix with " 's
ip route print detail where dst-address="xx.xx.xx.xx/xx"
On a large route DB, this shouldn't take more than a few seconds to complete.
User avatar
Posts: 1053
Joined: Fri Aug 10, 2012 6:46 am
Location: Jackson, MS, USA

Re: /ip route print where ... slow

Mon Aug 26, 2019 5:01 pm

Route lookups and routing table convergence is significantly faster when using the CHR as a border router.

Here is a presentation I did at MUM Europe in 2018 on that topic.
Global - MikroTik Support & Consulting - English | Francais | Español | Portuguese +1 855-645-7684 ... l-support/

Who is online

Users browsing this forum: No registered users and 13 guests