Hi IPANetEngineer (Kevin?),
First of all: thank you for your great talks at MUMs! They are enjoyable, of very high quality and I've learned a lot from them in the past weeks! Please keep doing them
I also like your detailed postings in this forum and your fantastic lab setup - just wow!
fwiw, you can also combine queries using the && operator to specify only IPv6 or any other attribute as well as the community search. Here is an example with large communities.
[zuul@sw-core-01.jan1.us.ipa] > routing/route/print detail where afi=ip6 && bgp.large-communities="65012:0:6"
Flags: X - disabled, F - filtered, U - unreachable, A - active; c - connect, s - static, r - rip, b - bgp, o - ospf, d - dhcp, v - vpn, m - modem, a - ldp-address, l - ldp-mapping, y - copy; H - hw-offloaded;
+ - ecmp, B - blackhole
bH afi=ip6 contribution=best-candidate dst-address=::/0 routing-table=main gateway=fc00:127:32::2 immediate-gw=fe80::de2c:6eff:fe39:18b%vlan3013-to-rtr-edge-02.jan1.us.ipa
[...]
bgp.peer-cache-id=*B000005 .large-communities=65012:0:6 .local-pref=100 .atomic-aggregate=no .origin=igp
That's cool! That's great for live debugging without too much hassle and even better than the missing "| in" , "| match" or even "| grep".
I'm coming from cisco (ios,xe,xr), Arista and Junos and learning ROS syntax is equally challenging as fun
Thanks! I stumbled upon your blog a few days ago, subscribed to your feed, but haven't seen this compilation yet.
It's for ROS6, but I guess I will find my way for ROS7 as well sometime.
Hi Heino,
if you intend to use Mikrotik routers for production purposes I recommend ROS6 (I am evaluating ROS7 for a quite long time but there are some important features still missing, e.g. show advertised routes). We are running CCR1072-1G-8S+ routers (full bgp table) for some years without major problems. The main disadvantage (ROS6) is a single core bgp (running at 100% nearly all the time). Nevertheless it is a powerful system with an excellent value for money and a lot of nice features.
Well - I thought about that from reading some of the beta and release threads I got the impression that there is still a lot of stuff missing in ROS7 and some things are just broken of course... but on the other hand there's a lot that changed going from 6 to 7 (general syntax, routing filter rule syntax, wireguard and some other features). I'm betting here on Mikrotik to get 7 stable and complete sooner than later. At the moment I did get everything to work I was looking for, so I guess I could stay on 7 for now for my personal stuff.
I got into Mikrotik mainly because I'm going to join a new company soon that uses Mikrotik for their enterprise routing. Coming from a datacenter and ISP company that's a huge step, so I thought I would have to look into this equipment before having to deal with it professionally. You might say I fell in love pretty hard, so I now have a little lab built myself and some production routers for my personal official networking project: a CHR and an x86 at IXPs with peering and transit, a 3011 at my home, all of those with fulltable (ipv6 only). The labbing stuff includes 3 HAP lites, some wifi APs. Then (of course...) Mikrotik decided to drop BGP and MPLS support from the HAPlites, so three HEX joined the club. I'm still waiting for two 5009, two ltAPs(LTE) and two R11e-LT8... from this you might see that I fell in love quite deep...
So I guess what will happen is: I will downgrade the HAPlites to 6.48.6 (to train the cli in case the new company is still on 6 and to get BGP back) and I will keep the rest on 7 to be up to date with the new stuff and to know what to lookout for when moving the company from 6 to 7 sometime.
Thanks to both of you for your insights, very much appreciated!
All the best,
Johannes