I'm not sure the BIRD logic, but it sounds like you're saying: - send static *and* - send all provider A routes *and* - send all provider B routes These would total more than a million routes. Usually what you share downstream is your own routes; the best-path selection after BGP processes all the routes it learned. That would be a list of about 680k best routes, and be less than your filter. (alternately, you're getting different routes from each of your providers, so if you add them together and remove the duplicates, you have more than 700k routes. I have more than 700k routes in my default-free zone) Jonathan On Wed, Apr 4, 2018 at 4:42 PM, Guillaume LUCAS <glucas+bird@glucas.fr> wrote:
Le 04/04/2018 à 15:28, Ondrej Zajicek a écrit :
Hi
What do you see in 'show protocols all' in import/export statistics? Do they make sense?
Hi,
# sudo birdc show protocols all
direct1 Direct master up 2018-01-12 Routes: 2 imported, 0 exported, 2 preferred Route change stats: received rejected filtered ignored accepted Import updates: 3 0 0 0 3 Import withdraws: 1 0 --- 0 1 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
kernel1 Kernel master up 2018-01-12 Routes: 31 imported, 681991 exported, 30 preferred Route change stats: received rejected filtered ignored accepted Import updates: 52 0 1 0 51 Import withdraws: 20 0 --- 1 20 Export updates: 83427721 55 0 --- 83427666 Export withdraws: 4163126 --- --- --- 4163135
static_allocations Static master up 2018-01-12 Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
bgp_upstream1 BGP master up 2018-01-27 Established Routes: 678683 imported, 0 filtered, 1 exported, 569533 preferred Route change stats: received rejected filtered ignored accepted Import updates: 38113294 0 294 12493695 25619305 Import withdraws: 2348477 0 --- 280 2348484 Export updates: 69298824 25943901 43354922 --- 1 Export withdraws: 2932089 --- --- --- 0
bgp_upstream2 BGP master up 2018-04-03 Established Routes: 681762 imported, 77 filtered, 1 exported, 112446 preferred Route change stats: received rejected filtered ignored accepted Import updates: 2828562 0 109 0 2828453 Import withdraws: 162753 0 --- 125 162737 Export updates: 2175525 646411 1529113 --- 1 Export withdraws: 67445 --- --- --- 0
ibgp BGP master up 2018-02-18 Established Routes: 681993 imported, 682012 exported, 10 preferred Route change stats: received rejected filtered ignored accepted Import updates: 29660288 0 0 518955 29141333 Import withdraws: 7164695 0 --- 0 7164695 Export updates: 51000527 12312881 0 --- 38687646 Export withdraws: 1950522 --- --- --- 12715457
bgp_downstream BGP master up 20:17:52 Established Routes: 0 imported, 681980 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 2121052 0 17236 --- 2103816 Export withdraws: 4750 --- --- --- 18179
It seems to me it makes sense: in ibgp (no filter in place), this router redistributes 682012 routes (upstream1 + upstream2 + some differences between them, probably). 682012 - 2 (direct1) - 31 (kernel1) = 681979 = downstream. (kernel1 and direct1 are block by the "export where", see my previous mail)
Yes, I use iBGP because I have an another router. Quagga. Same two upstreams. No downstreams. Same receive limits (shutdown BGP session if routes > 700,000).
-- Jonathan