Would MT consider the following updates to Manual BGP HowTo & FAQ please:
https://wiki.mikrotik.com/wiki/Manual:BGP_HowTo_%26_FAQ
— “Manual-BGP HowTo + FAQ.1.txt” 2019-02-12 21:15:12.007181300 +1030
+++ “Manual-BGP HowTo + FAQ.2.txt” 2019-02-12 21:24:49.361641000 +1030
@@ -58,31 +58,31 @@
====Question: How to quickly check how many routes there are in route table?====
For all routes use:
- ip route print count-only
- /ip route print count-only
To see route count from a particular peer look at ‘’‘prefix-count’‘’ property in:
- route bgp peer print status
- /routing bgp peer print status
====Question: How to seen routes advertised to, and routes received from a particular peer?====
To see routes advertised to a particular peer (similar to Cisco command ‘‘show ip bgp neighbor x.x.x.x advertised-routes’’ ) use:
- routing bgp advertisements print
- /routing bgp advertisements print
Or
- routing bgp advertisements print <peer_name>
- /routing bgp advertisements print <peer_name>
{{Note|At the moment AS-PATH attribute is displayed without prepends!}}
To see routes received from a particular peer (similar to Cisco command ‘‘show ip bgp neighbor x.x.x.x received-routes’’) use:
- ip route print where received-from=<peer_name>
- /ip route print where received-from=<peer_name>
{{Note|Routes that were discarded (with action ‘‘discard’’) in incoming filters, or ignored because of invalid attributes (e.g. not directly reachable next-hop for EBGP) will not be displayed!}}
====Question: Is load balancing possible with MT BGP?====
Yes. Even though BGP itself cannot propagate multiple next-hops for a single route through the network, there are ways how to have routes with multiple next-hops on a router.
One way is to set multiple next-hops with routing filter.
- routing filter add chain=bgp-in set-in-nexthop=10.0.1.1,10.0.2.1
- /routing filter add chain=bgp-in set-in-nexthop=10.0.1.1,10.0.2.1
Another way is to resolve BGP next-hop (if it is not directly reachable) through a static or OSPF route with multiple next -hops.
- ip route add dst-address=x.x.x.x/y gateway=10.0.1.1,10.0.2.1
- /ip route add dst-address=x.x.x.x/y gateway=10.0.1.1,10.0.2.1
See also: [[BGP Load Balancing with two interfaces]].
@@ -134,17 +134,17 @@
====Question: How to aggregate IGP routes?====
Since 3.30 you can specify ‘’‘include-igp’‘’ in BGP aggregate configuration. Example:
- ip route add dst-address=10.9.9.0/25 gateway=10.0.0.1
- ip route add dst-address=10.9.9.128/25 gateway=10.0.0.2
- routing bgp aggregate add instance=default prefix=10.9.9.0/24 include-igp=yes
- /ip route add dst-address=10.9.9.0/25 gateway=10.0.0.1
- /ip route add dst-address=10.9.9.128/25 gateway=10.0.0.2
- /routing bgp aggregate add instance=default prefix=10.9.9.0/24 include-igp=yes
Results:
[admin@MikroTik] > routing bgp advertisements print
PEER PREFIX NEXTHOP AS-PATH ORIGIN LOCAL-PREF
peer1 10.9.9.0/24 10.0.0.131 incomplete
Use routing filters to control which routes are aggregated. For example, if you don’t want to aggregate connected routes:
- routing filter add chain=aggregate-out protocol=connect action=discard
- routing bgp aggregate set [find] advertise-filter=aggregate-out
- /routing filter add chain=aggregate-out protocol=connect action=discard
- /routing bgp aggregate set [find] advertise-filter=aggregate-out
====Question: How to advertise the default route?====