❦ 21 mai 2018 14:51 -0400, Brian Rak <b...@gameservers.com> :
> 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 that our IRR filters no longer show up in the
> main configuration, and 'show | compare' is back to being fast again.
>
> The downside seems to be that these can blow up the router somehow...
> there's a big warning about it in the py-ez code:
> https://github.com/Juniper/py-junos-eznc/blob/master/lib/jnpr/junos/utils/config.py#L750
There are also some warnings about use with GRES and NSR. They explain a
bit about GRES, but they don't say what's wrong with NSR. For IRR, it
seems that if the static database contains an "allow all" and the
ephemeral database contains the IRR filter, you should be good. Did you
get Juniper to confirm your use case is correct?
--
"Not Hercules could have knock'd out his brains, for he had none."
-- Shakespeare
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
