said by DarkLogix:Personaly I'm at a place that uses juniper, and well due to it juniper has made a awful impression on me.
So for now I mess with my cisco gear at home.
juniper makes some solid kit, but just like any other vendor -- it takes knowledge of the code lineage, an understanding of hardware/software limitations, and the best practices for configuration.
in fact -- $current_customer would have a lot fewer headaches if they would have used srx firewalls instead of cisco asa.
juniper mx-kit is pretty solid as well, as long as you know the limitations of mpc, dpc, ms-dpc and how they play inside the chassis.
the ex-series is a little half-baked -- but most of the bugs are solved for simpler switching, etc. when you start running mpls bits on top, then it gets interesting.
long story short -- as a consultant -- you have to keep an open mind when it comes to hardware. blanket statements that $vendor sucks prevent you from developing a true best-of-breed solution. of course -- at times -- you have to tow the line of whichever vendor you are more closely associated with. for me -- that means cisco -- but being a var/partner with multiple companies provides that enablement to choose what is best.
make yourself an olive box. you'll enjoy it.
q.