[j-nsp] DPC or MPC with MX480

[Mark Tinka]

On Friday, August 26, 2011 12:23:14 AM Vladislav A. VASILEV 
wrote:

> I am in process of procuring new hardware and I've got a
> question. If you were to go for MX480 would you order it
> with MPCs or DPCs. Also if your network were to have
> MX80s as well which are Trio based would that influence
> the decision on choosing either MPCs or DPCs for the
> MX480s?

1.  MPC's are likely going to be cheaper, particularly if
    you're looking at 10Gbps density.

2.  Juniper have just released EoS/EoL dates for the DPC's.
    So they might end up cheap on the used market, or just
    run out if you invest in them too long.

3.  Mixing-and-matching DPC's and MPC's in the same chassis
    is simply asking for it.

4.  The later the code, the better the chance of having
    MPC's that actually work, but also, the greater the risk
    of code instability (even though post-10.4 Junos is
    meant to be better).

5.  Lots of features already stable on the DPC's may not be
    ported to the Trio's. You'll have to wait and play
    Junos-chasing games.

6.  Note current generation MPC's may be oversubscribed for
    your various applications. Be sure you have your
    bandwidth requirements right.

7.  Some of the more advanced features for certain
    applications may only be present (current or future) on
    the MPC's. Check with Juniper to confirm what you need.

8.  You'll probably be chasing code for a while to fix
    stability issues while gaining important features with
    the MPC's.

9.  You're likely going to end up mixing-and-matching some
    chassis' in the future if you choose to go with DPC's
    now, and keep your MX's alive and well for years.

10. We prefer QoS on the MPC's. Not even the highest end
    DPC's will do what we want re: QoS.

Hope this helps.

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20110830/c0467732/attachment.pgp>