Re: [j-nsp] Managing large route-filter-lists

Brian Rak writes: >Trip report: > >Don't use these for massive IRR configs. > >There's seemingly no garbage collection done on IRR configs, so you'll >be having to wipe the database via shell and start over around once a >week (we've got a config that's about 100k lines, and we only change the

Re: [j-nsp] Managing large route-filter-lists

On 5/22/2018 11:46 AM, Brian Rak wrote: On 5/22/2018 10:03 AM, Brian Rak wrote: On 5/22/2018 12:58 AM, Phil Shafer wrote: Brian Rak writes: The downside seems to be that these can blow up the router somehow... Not blow up, but obfuscate.  Imagine a user (or support person) who is

Re: [j-nsp] Managing large route-filter-lists

On 5/22/2018 10:03 AM, Brian Rak wrote: On 5/22/2018 12:58 AM, Phil Shafer wrote: Brian Rak writes: The downside seems to be that these can blow up the router somehow... Not blow up, but obfuscate.  Imagine a user (or support person) who is unaware that ephemeral databases are in use and

Re: [j-nsp] Managing large route-filter-lists

On 5/22/2018 2:48 AM, Pavel Lunin wrote: Hi list, Anyone knows if this "ephemeral configuration" thing is just a new fancy hipster-ish name of the dynamic database feature, which has been in JUNOS since 9.x and never really been widely used in production by normal people? -- Kind

Re: [j-nsp] Managing large route-filter-lists

On 5/22/2018 12:58 AM, Phil Shafer wrote: Brian Rak writes: The downside seems to be that these can blow up the router somehow... Not blow up, but obfuscate. Imagine a user (or support person) who is unaware that ephemeral databases are in use and resorts to pulling out hair, muttering

Re: [j-nsp] Managing large route-filter-lists

❦ 22 mai 2018 08:48 +0200, Pavel Lunin  : > Anyone knows if this "ephemeral configuration" thing is just a new fancy > hipster-ish name of the dynamic database feature, which has been in JUNOS > since 9.x and never really been widely used in production by normal > people?

Re: [j-nsp] Managing large route-filter-lists

Hi list, Anyone knows if this "ephemeral configuration" thing is just a new fancy hipster-ish name of the dynamic database feature, which has been in JUNOS since 9.x and never really been widely used in production by normal people? -- Kind regards, Pavel

Re: [j-nsp] Managing large route-filter-lists

Brian Rak writes: >The downside seems to be that these can blow up the router somehow... Not blow up, but obfuscate. Imagine a user (or support person) who is unaware that ephemeral databases are in use and resorts to pulling out hair, muttering profanity, and sticking pins in their "Mr. Phil

Re: [j-nsp] Managing large route-filter-lists

On 5/21/2018 3:37 PM, Vincent Bernat wrote: ❦ 21 mai 2018 14:51 -0400, Brian Rak  : We switched this over to using ephemeral configs: https://www.juniper.net/documentation/en_US/junos/topics/concept/ephemeral-configuration-database-overview.html This seems to have

Re: [j-nsp] Managing large route-filter-lists

❦ 21 mai 2018 14:51 -0400, Brian Rak  : > We switched this over to using ephemeral configs: > https://www.juniper.net/documentation/en_US/junos/topics/concept/ephemeral-configuration-database-overview.html > > This seems to have dramatically reduced configuration time (at

Re: [j-nsp] Managing large route-filter-lists

Another downside here is disk usage: > show ephemeral-configuration irrdata | display set | count Count: 216414 lines which ends up being: -rw-r-  1 root  config 164M May 21 19:11 juniper.eph_irrdata I don't think that this would be any smaller in the normal config database, but that

Re: [j-nsp] Managing large route-filter-lists

We switched this over to using ephemeral configs: https://www.juniper.net/documentation/en_US/junos/topics/concept/ephemeral-configuration-database-overview.html This seems to have dramatically reduced configuration time (at the expense of being slightly less clear). It also has the bonus

Re: [j-nsp] Managing large route-filter-lists

Hey Brian. Yeah you should just expect long commits. We're closer to 1M than 500k right now. One thing to consider, if you are able to pull off received but not accepted routes off the router BMP or just 'show route ... hidden', and then offline create intersection of IRR data and received

[j-nsp] Managing large route-filter-lists

What is the best way to manage large numbers of large route-filter-lists effectively? We've been generating per-peer route-filter-lists based on IRR data, and loading them via netconf.  However, I'm noticing that commits take longer and longer, and that we're hitting weird junos errors around