[j-nsp] Why should I *not* buy an MX?

[Phil Bedard]

The only things I don't like as much about the MX is the various  
flavors of DPCs they offer depending on what your application might be  
(queueing options), having to keep track of limitations on certain  
cards (like Cisco), and licensing of certain features.   We've been  
testing the MX960 and have them deployed in a few sites today, and  
they are as solid as the M/T series.   We've tested pretty much  
everything you've listed there with the box in both a core/agg role  
and found no real flaws that weren't software related, meaning they  
affected the M/T as well.

It's a great platform.  It still doesn't compete with the 7600 on  
price for most of the market, considering there are tons of people out  
there that don't need the more expensive ESxx 7600 cards, but for  
those that are looking at 7600 w/ES20/ES40 vs. MX series, I'd take the  
MX.

Phil


On Nov 7, 2008, at 10:57 AM, nachocheeze at gmail.com wrote:

> We've been using Juniper M/T series in service provider scenarios for
> a couple of years now, and really like them.  As part of an equipment
> life cycle refresh, we're considering replacing our core (campus
> enterprise) network with something in the MX series; a la this post:
>
> http://marc.info/?l=juniper-nsp&m=122008030004203&w=1
>
> We are very "glass is half empty" on our evals; while it seems most
> are pretty happy with the MX boxen, I'm trying to find something
> show-stopper that would make us go with another product.  We're
> wanting basically a campus Ethernet version of an M/T box and all that
> that implies (besides just shoveling packets at a non-blocking line
> rate, we'd like full MPLS and RSVP/TE support, L2/L3 VPN, multicast,
> IPv6, lawful intercept, etc), so I'm curious if anyone's demo'ed an MX
> box as a campus core router and tested everything but the kitchen sink
> and found something that Juniper says "works great", but in actual
> practice just isn't quite there yet.
>
> Basically, can someone give me reasons apart from "we don't need SONET
> or any other WAN interfaces, and it's cheaper per port", why should we
> NOT choose an MX box?  Are there any gotchas waiting in the wings for
> someone who's used to the full flavored goodness that is the M/T
> series?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp