[j-nsp] logical system in production - MX960
Pavel Lunin
plunin at gmail.com
Tue Oct 3 08:55:04 EDT 2017
Strongly agree with Ytti. Most LSYS deployments I've seen were really
"deploy an LSYS to deploy an LSYS" kind of of thing.
Some more or less viable use-case I know is BGP scaling: dedicated rpd in
an LSYS for an off-path RR. It creates a dedicated 32-bit rpd, which can
consume another 4GB of RAM. But nowadays, with all the kinds of VM-based
routers/RRs, 64-bit rpd, node slicing and stuff, this approach looks to be
obsolete.
2017-10-03 10:25 GMT+02:00 Saku Ytti <saku at ytti.fi>:
> On 25 September 2017 at 15:10, Aaron Gould <aaron1 at gvtc.com> wrote:
>
>
> Hey,
>
> > Do you all use logical systems in your production environment ?
>
> No. Be sure you're solving real technical problems, not political or
> process. I know there are use-cases, but I suspect there are fewer
> use-cases than deployments.
>
> There are several layers of function multiplexting
>
> virtual-router: essentially just VRF
> logical-system: separate rpd running in same control-plane
> node slicing: separate freebsd KVM running on single hypervisor
>
> Since node slicing, I think logical-systems are rather useless.
>
> https://www.juniper.net/documentation/en_US/junos/
> topics/concept/node-slicing-overview.html
>
> --
> ++ytti
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list