Dear Aaron, I can't relate for MX product-line and LSYS interactions.
Regarding SRX product-line and LSYS, it's mostly some functionnalities not being handled well by the firewall at the LSYS level. In the end, I know it forced my hosting colleagues to resort to some nasty workarounds that became cumbersome and painful over time. So, in th end, less (if not !?!) operationnel gain and a complexified debug process. Regarding Logical DOM, it's is going to replace the LSYS functionnality. Juniper is going to move trade off ressources / process separation for scalabilty... Meaning, hardware and software ressources will not be segregated anymore. Instead, you will be able to use create much more logical DOM instances. Juniper is just going to align with what other vendors are doing out there. I hope this answers your questions. Best regards. 2017-10-10 14:13 GMT+02:00 Aaron Gould <[email protected]>: > Thanks Youssef, yes sir, you may advise me anytime :) > > I currently use lsys in lab for testing and is a nice way of having lots > of separate routers in one MX104 > > We (my coworkers and I) have thought that when we rollout a new ring of > MX960's, that maybe it would be good to try to put the PE functions of an > MX960 into a lsys. What are the limitations with that? > > What is logical DOM ? Is this another way of saying "Junos Node Slicing" > or is logical DOM something altogether different than slicing ? > > -Aaron > > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
