<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">(forgot to copy back the list)</span></div>
<div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; "><br></span></div>Thanks, this is really helpful. I do appreciate the cost difference. We do have some "credits", so to speak, due to our early adoption of the SRX series.<div>
<br></div><div>Some of the routing engine tasks done on the SRX series are really, really slow. I have my SRX series taking a full route table from my upstream providers today on BGP. This process can take about 5 minutes to complete. Obviously, this is insane.</div>
<div><br></div><div>How fast are the Juniper MX series at taking / injecting routes? How is the failover convergence?</div><div><br></div><div>For the CLI, I'm not sure that I like JunOS better than the IOS clone. My former career was entirely Cisco, so the IOS clone is like an old, familiar friend for me. I have more or less gotten over the learning curve with JunOS, though. And I do like it is a familiar FreeBSD system underneath, even allowing you to go in to a shell.</div>
<div><br></div><div>There's a site I found, which I suspect is likely to be a bit of a Cisco talking point, but interesting nonetheless: </div><div><br></div><div><a href="http://bradreese.com/cisco-vs-competitor.htm" target="_blank" style="color: rgb(6, 88, 181); ">http://bradreese.com/cisco-vs-competitor.htm</a></div>
<div><br></div><div>Some of their "studies" show that the MX-series routers have some trouble during failover. I am taking it with a grain of salt, just curious of anyone has had those experiences.</div><div><br>
</div><div>On the MLX side of things. With a rather large Foundry switching environment, I and my team are very comfortable on that platform. The switches just work, and the strangest problem I have seen interop problems with a Cisco -- and I blame Cisco for that. We have had some struggles using the Foundry ServerIron due to a few bugs here and there. I do, however, expect that a full layer3 stack is significantly less complicated of code than what the ServerIron is able to do, so should have less bugs.</div>
<div><br></div><div>They are marketing the dual management modules as ISSU-capable. There is a cost difference, but it's not even 25% for our config. </div><div><br></div><div>Last but not least, support. Both vendors have terrible technical support when you have a bug, in my experience. I loathe having to open a case. Is it different for support on the router series?</div>
<div><br></div><div>Thanks for all the wisdom, much appreciated.</div></span><br><div class="gmail_quote">On Fri, May 7, 2010 at 12:46 AM, David Ball <span dir="ltr"><<a href="mailto:davidtball@gmail.com">davidtball@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I eval'd the XMR-4 for a couple of months (same as an MLX, really),<br>
and for the most part was quite happy with it. Amazingly fast boot,<br>
seemed stable to me, and I actually recommended it to management for a<br>
portion of our network. Politics took us in a different direction<br>
though, we stuck with Juniper (we have a T-series core, and now some<br>
MX480s/240s).<br>
Off the top of my head, these were a few of the 'shortcomings' I<br>
found with the MLX-4 which, for us, wouldn't have necessarily been<br>
showstoppers, as workarounds were surely available. They may or may<br>
not apply to you at all:<br>
<br>
-can't gather per-VLAN input/output stats via SNMP on a dot1q port<br>
(displays total port stats only), although the account team committed<br>
to providing a fix if we bought x number of them)<br>
-there were some QinQ intricacies that I had a hard time wrapping my<br>
head around, but eventually made it work<br>
-couldn't hold a global routing table inside a VRF/L3VPN due to the<br>
TCAM memory partitioning Brocade uses (we house the internet in a VRF<br>
on our Juniper network).<br>
-unable to do dot1q *and* MPLS on the same physical port (fixed in<br>
release 5.0.0 apparently)<br>
-code upgrades are a little clumsy, with multiple image upgrades<br>
required, and no In-Service Software Upgrade as far as I know.<br>
<br>
I never touched IPv6 on it, so can't help you there. But, I was<br>
running OSPFv2, BGP (no full tables during my eval), MPLS (LDP &<br>
RSVP-TE w/FRR) and interop'ing with some Junipers, and built VLLs,<br>
VPLSs, and VRFs which all worked between the platforms.<br>
<br>
I've heard the odd report of frequent hardware failures on the<br>
XMR/MLX line, but can't say how recent said reports are and I didn't<br>
hear them first hand.<br>
I still really like the MLX/XMR boxes, and would love to get my<br>
hands on one of the new CERs, but alas, it may not be in the cards. I<br>
think the MLX is a decent box (we ended up buying an MLX-4 which still<br>
sits in our lab) and you simply can't beat the price (they were less<br>
than 1/2 the price of similarly spec'd Juniper, Cisco and<br>
Alcatel-Lucent boxes).<br>
<br>
That said, the MX240 is a great box too, if not a little<br>
weird.....only 2 slots for line cards if you have redundant REs. Tons<br>
of horse power, best CLI IMO, and generally speaking it just 'works'.<br>
If it weren't for the extraordinarily high price, I'd say it was a<br>
near perfect box.<br>
<br>
Anyhow, not sure it helped, but good luck.<br>
<font color="#888888"><br>
David<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
On 6 May 2010 19:59, Scott T. Cameron <<a href="mailto:routehero@gmail.com">routehero@gmail.com</a>> wrote:<br>
> I'm in the market for a new edge router. It must be capable of performing<br>
> BGP on IPv4 and IPv6, OSPF and scale to 10GbE uplinks.<br>
> The two products in mind are:<br>
> Foundry NetIron MLX-4<br>
> vs<br>
> Juniper MX240<br>
> There will be no more than 10 BGP sessions in the configuration.<br>
> I have had a bad experience from having early adopted the Juniper SRX-series<br>
> firewall, so I'm not sure if I can trust their product lines.<br>
> We already have a large install base of Foundry FESX648s and SX800s in the<br>
> core.<br>
> Anyone have experience with either? With both? Or any other useful<br>
> guidance?<br>
> Thanks.<br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> foundry-nsp mailing list<br>
> <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
</div></div></blockquote></div><br>