Check BGP routes efficiently

RouterOS Forwarding Protocols
1

Hi guys,

I have this router which has the entire Internet routing table. However I find it difficult to show any routes for troubleshooting purpose since it took 8 minutes to complete a command… For example, if I want to see how to reach 1.1.1.1, so I ran

/ip route print where 1.1.1.1 in dst-address

And it will take a long time…

I am also wondering how to check the actual BGP table instead of routing table.. For example this router peer with two uplink ISPs so how to check the BGP route that is less preferred? I think I am just looking for Cisco equivalent command “show ip bgp 1.1.1.1” which also tells me other BGP attributes such as local preference, metric, …etc..

Thanks!
Difan

2

Currently in RouterOS v6.x implementation there is no faster way.

3

Out of curiosity, how much of a performance improvement is expected for route lookups in RouterOS v7.x? (if you happen to know)

4

It’s ironic that this is the case.

When the routing table is small, there’s almost no need for route table search commands.
When you have a huge routing table, that’s the only thing that even remotely makes sense.
Yet - it takes 8 minutes to see a route table entry via search on a full BGP table…

I’ve only ever run Cisco routers with a full table. I can say for sure that I would switch from Mikrotik to Cisco for this one reason alone. Don’t get me wrong, I love Mikrotiks (I participate in the forums even though I’ve been at my current job for over two years and we don’t even use Mikrotik) - they’re one of the best boxes out there for so many things…

But this one behavior alone would prevent me from using ROS in a production BGP environment.
“show IP route x.x.x.x m.m.m.m” is near-instantaneous, and to say that I used this command every day would be like saying the Sun is hot… “show ip bgp x.x.x.x/m” is also lightning fast, and another indispensable tool. If BGP routing is like carpentry, these two tools are like a hammer and a screwdriver. If you don’t have them, you aren’t a carpenter.

5

It is hard to say for version that will be available for masses, but right now it is

[admin@MikroTik] /routing route> :put [:time [print where 192.0.128.1 in dst-address] ] 

     DST-ADDRESS        GATEWAY            DISTANCE
 AS> 0.0.0.0/0          10.5.101.1                0
  S  0.0.0.0/0          10.5.101.1                1
D bY 192.0.128.0/17     10.5.101.1               20
D bY 192.0.128.0/17     10.5.101.1               20

00:00:00.010344

from 1milion routes on CCR1036

6

That is a fantastic improvement!
I can’t wait to try it out.

Thanks for the news.

(Also interesting to see that there is a new /routing route sub-menu to replace /ip route and /ipv6 route)

7

Nice!

What does the Y flag mean?

8

Maybe reflect route to another machine/BGP Monitor?

9

Don’t TEASE me like this…