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 >BGP peers that actually have changes in IRR) > >They have a size limit of 400mb, and that's pretty easy to hit. Once you >hit that size limit, you'll start getting weird errors back when >changing the normal configuration (it *seems* like it ends up committing >a fraction of the ephemeral configs, so for us it complaints about >missing communities and policy statements) > >I'm considering changing over to prefix-lists (instead of >route-filter-lists), and moving to the dynamic DB instead. I'm not even >sure if this will help :/
This is definitely not expected behavior. Please reply offlist with details and we start investigating the issues you are seeing. Thanks, Phil _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp