11–20 of 125 posts
I remember working with Juniper equipment a decade ago (I didn't like it because I've traditionally worked exclusively with Cisco equipment), but I haven't heard anyone in my circles mention Juniper since. Are they considered a niche vendor today (similar to Novell in the 2000s)?
I remember working with Juniper equipment a decade ago (I didn't like it because I've traditionally worked exclusively with Cisco equipment), but I haven't heard anyone in my circles mention Juniper since. Are they considered a niche vendor today (similar to Novell in the 2000s)?
The configuration syntax works as expected, it's flexible but extensible in the right places and mostly has lots of knobs to tune things but without requiring extensive boilerplate to get things to work as expected.
The hardware seems to fit intelligent niches and actually does what it says on the spec sheets.
The system is FreeBSD, while that's a debatable choice in 2024 it's far better than the obscure OSes that others are using for their core systems.
At the end of the day you can always just "start shell user root" and be root on a FreeBSD system. If you're a bit crafty on most Juniper systems you can also run unsigned code if you like. Some Juniper platforms (and not talking about just the huge ones, some of the 1U pizzabox switches) allow you to run a full-blown Linux system alongside the FreeBSD image (because they are actually Linux running FreeBSD on a hypervisor).
JTAC was filled with skilled, intelligent engineers who actually cared and tried to solve your problems. (Not sure today as I haven't had to call them in years). The other TACs I've delt with were focused on call time and ticket handling metrics and would ask obviously pointless questions or repeat information you already provided for a fast close.
I still remember calling JTAC during one outage we had. First L1 engineer after my initial description of the problem basically came back and said something like "that sounds like a really bad outage, please open SSH from 1.2.3.4 and add this public key and I'll login and get the information for L3." Within about 15 minutes I was on the phone with an L3 engineer who correctly diagnosed and proposed a fix for the issue. Amazing support. Not perfect, I have some horror stories too, but, always with people who cared and far less than with C or other vendors TACs.
Very sad day.
> Accelerating AI-Native Networking Leadership I think I just threw up in my mouth.
Happy Juniper customer since 2010. Across SRX, EX, QFX lines. What to do now, what to do...
It's sad, HPE will suck out all the life-force of Juniper; I have had other HP-acquired products and they never got better in subsequent offerings, only worse.
Happy Juniper customer since 2010. Across SRX, EX, QFX lines. What to do now, what to do...
csco beckons thee
I remember working with Juniper equipment a decade ago (I didn't like it because I've traditionally worked exclusively with Cisco equipment), but I haven't heard anyone in my circles mention Juniper since. Are they considered a niche vendor today (similar to Novell in the 2000s)?
Having worked with every vendor under the sun for networking equipment across my career, I enjoy working with Juniper by far the most. The configuration syntax works as expected, it's flexible but extensible in the right places and mostly has lots of knobs to tune things but without requiring extensive boilerplate to get things to work as expected. The hardware seems to fit intelligent niches and actually does what i…
I remember working with Juniper equipment a decade ago (I didn't like it because I've traditionally worked exclusively with Cisco equipment), but I haven't heard anyone in my circles mention Juniper since. Are they considered a niche vendor today (similar to Novell in the 2000s)?
Its not really a bad strategy. If you're going to have a large team of network engineers work continuously on a the Juniper tech stack, they'll get use to it - even if they were raised on Cisco IOS. Juniper stuff works just as well as the rest of them.