I’d rather a vendor tell me ‘we don’t do that’—what I’ve learned managing network quality at Juniper

Vendors who claim they can do everything are usually lying—about something

Let me say this up front: if a vendor tells you they handle every piece of your network infrastructure—switching, routing, security, wireless, SD-WAN, AI ops—and they nail all of it equally well, I’d be skeptical. I've been in quality roles at networking companies for over four years, reviewing hundreds of product lines (switches like the EX and QFX series, firewalls like the SRX, and access points and AI-driven operations like Mist), and I’ve seen the gap between a promise and a deliverable far too many times.

At Juniper, we're known for high-performance routing (the MX and PTX are staples at major service providers) and AI-driven network operations via Mist. We do those things really, really well. But I'd never say we're the best at everything in networking. And honestly? That's exactly why you should trust a vendor—when they know where their edge stops.

Why I’m wary of the 'one throat to choke' pitch

I've heard this from plenty of procurement teams: “We want a single vendor for everything—it’s easier, fewer contracts, less finger-pointing.” In theory, sure. But in practice, I've seen what happens when a vendor is forced to cover a gap they aren't built for.

I still kick myself for an incident in Q1 2024. We were evaluating a partner for a managed security overlay—something that was meant to sit on top of our SRX firewalls. The partner said they could do it all: the firewall configuration, the IDS/IPS tuning, the log aggregation. They showed a slide deck that looked rock-solid. We didn't peer into their actual operations. A month in, we found they were manually configuring 30% of our policies because their automation tool literally couldn't parse Juniper's commit scripts. That quality issue cost us about a $22,000 redo and delayed a service launch for weeks. We should have asked them: “What's the one thing you don’t do well with our gear?” Because if they’d said “automation around commit scripts,” we could have planned for it.

The lesson: A vendor who tells you “this isn't really our strength, but here's someone who does it better” earns more trust for everything else they do. I'd rather work with a specialist who knows their limits than a generalist who overpromises on a white paper.

How specialization shows up in real networking gear

This isn't just about sales pitches—it's about the hardware itself. Take the Juniper EX2300-C as an example. I've seen buyers assume it's a “downsized” version of the EX3400, just cheaper and smaller. That's a dangerous assumption. The EX2300-C is designed for compact deployments like branch offices or retail, where you need low port density and low power draw. It's not built for an aggregation closet with heavy MLAG traffic. Meanwhile, the QFX series is built for data center spine-leaf deployments. If you take a QFX spec sheet and try to cram it into a branch budget, you're going to either overspend or underperform.

I ran a blind test with our engineering team last year: same campus design, two scenarios—one using a full QFX-based fabric, one using a “simpler” all-in-one switch stack from an HPE-Aruba approach (no offense to HPE, it's just the most common alternative I see). The result? The QFX fabric handled 40% more east-west traffic bursts before hitting buffer limits. But it also cost about 30% more upfront. That's not a “good vs. bad” story—it's a “right tool for the job” story. A vendor that claims their one box solves both the branch and the data center equally well? I’m suspicious. In my experience, specialization within a product line isn't a flaw—it's a sign the engineering team actually had a use case in mind.

What “Juniper reviews” and “what is networks” really tell me

If you’re searching for “Juniper reviews” or “what is networks,” you’re likely at the beginning of your evaluation. And I love that. But I’d ask you to flip your question: instead of “who can do everything?” ask “what do our networks actually need?”

I know our Mist AI engine is fantastic at proactively fixing Wi-Fi issues. I know our SRX firewalls are trusted for deep security inspection. I know the MX routers are mission-critical for providers pushing hundreds of gigabits. But if you came to me and said “we need a budget wireless solution for a coffee shop,” I’d say “Mist is probably over-engineered for that—look at a well-regarded SMB vendor or a used AP on the gray market.” That might sound like I’m losing a sale. But honestly? It builds a relationship for when you do need a high-performance core.

The third time a buyer called me saying “we bought an all-in-one platform and now our VoIP traffic is jittery when we turn on the IDS” (note to self: document that exact scenario—it keeps happening), I stopped assuming “comprehensive” meant “better.”

I expect pushback—because “versatile” sounds safe

I’ve had plenty of procurement people tell me: “I want a versatile solution so I’m not locked into a niche.” I get it. The risk of specialized vendor lock-in is real. But I'd argue that a vendor that hides its boundaries is a bigger risk.

In my experience, the most practical solutions come from vendors who can say: “This thing? Yeah, we don't do that. Here's what we do instead, and here's what to look for in a partner for that other piece.” It’s not a sign of weakness—it’s a sign of maturity. A vendor that tries to be everything to everyone usually ends up disappointing everyone on something.

My bottom line: know your edge, or get caught on it

The cost of a vendor overpromising and underdelivering isn't just financial—it's the lost time, the compromised network performance, the trust broken with your own users. I've seen a $50,000 switch deployment lose cred because a vendor said “we handle AI ops end-to-end” but couldn't actually integrate with the existing monitoring stack. The customer's network team spent 6 months patching the gap.

So here's my view: if you're a network buyer, ask vendors point-blank: “What's one thing you'd absolutely send to someone else?” If they hem and haw, that's a red flag. If they give you a confident, specific answer—like “we don't do low-end wireless, but for that, look at a specialized SMB provider”—that's a vendor I'd trust with my core infrastructure.

Because honestly? Knowing where you stop is half the battle in making a reliable network. I’d rather a vendor tell me “we don't do that” up front than let me discover it in a post-install review.