Just to chime in --- for scale-out, wouldn't you be better offloading those MS-MPC functions to another box? (i.e. VM/Dedicated Appliance/etc..?).
You burn slots for the MSMPC plus you burn the backplane crossing twice; so it's at worst a neutral proposition to externalise it and add low-cost non-HQoS ports to feed it. or is it the case of limited space/power/RUs/want-it-all-in-one-box? and yes, MS-MPC won't scale to Nx100G of workload. - CK. > On 5 Mar 2020, at 1:36 am, Tom Beecher <[email protected]> wrote: > > It really depends on what you're going to be doing,but I still have quite a > few MX960s out there running pretty significant workloads without issues. > > I would suspect you hit the limits of the MS-MPCs way before the limits of > the chassis. > > On Wed, Mar 4, 2020 at 6:56 AM Ibariouen Khalid <[email protected]> wrote: > >> dear Juniper community >> >> is there any limitation of using MX960 as DC-GW compared to MX10K ? >> >> juniper always recommends to use MX10K , but i my case i need MS-MPC which >> is not supported on MX10K and i want to knwo if i will have some limitation >> on MX960. >> >> Thanks >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
