A Network Upgrade Checklist: Juniper MX, EX2200, and the Phones You Forgot About

I'm a quality and compliance manager at a networking equipment company. For the past six years—or rather, the past five and a half, if I'm being precise—I've reviewed hundreds of orders for routers, switches, firewalls, and access points. This article is the checklist I use before any network gear gets deployed. If you're an IT manager at a mid-sized company, or a consultant specifying hardware for a client, this is for you.

Here's the short version: before you sign off on any network equipment order, work through these six steps. They'll save you from the kind of mistakes I've seen others make—and a couple I've made myself.

Step 1: Map the real network boundary, not the diagram

Most people draw a box around the core router and call it a day. But the network includes every endpoint that connects to it—including those old cordless phones and the 2660 flip sitting at the reception desk. If those devices need to register to an on-premises PBX, your switch specs and PoE budget need to account for them.

It's easy to forget phones when you're planning a Juniper MX router deployment. In Q1 2024, we ordered switches without checking how many analog adapters we'd need for legacy devices. We had to scramble for external power supplies. That was a classic process gap on our side.

Step 2: Verify Juniper MX router and EX2200 specs against your actual traffic

Don't buy based on the marketing name. The Juniper EX2200 is an older access switch—fine for basic edge, but its feature set and PoE capabilities are different from the newer EX2300/EX3400 series. Similarly, when picking a Juniper MX router, understand the throughput limits for the specific model. According to Juniper's MX Series documentation, the MX204 supports up to 400 Gbps in a compact form factor—but that's chassis-level performance; your line cards and policies affect real-world numbers.

I always confirm the model's forwarding capacity and memory against projected traffic. If you're running heavy telephony or East-West traffic, you might need a bigger buffer. It's not the glamorous part of networking, but it catches allocation errors before they become outages.

Step 3: Compare against Cisco switches—but compare the right things

Every procurement conversation eventually becomes “Juniper vs Cisco switches.” I get it. Both vendors make solid hardware. The real differences are in CLI syntax, automation APIs, licensing models, and support experience. If your team already lives in Cisco IOS, switching vendors has a training cost. If you're frustrated with Cisco licensing, Juniper's approach may look more appealing.

Neither vendor is objectively better. What matters is how well the platform fits your team's skills and operational workflow. I've seen a technically superior box fail because the staff couldn't troubleshoot it in a crisis. That's not a dig at either vendor—it's an operational reality.

Step 4: Check PoE budgets and phone requirements

This is the step most people ignore. You're not just buying switches; you're buying power for every edge device.

Let's talk about cordless phones, since they're often an afterthought. If your office uses DECT 6.0 cordless phones—or a legacy handset like the 2660 flip—they may not need PoE, but their base stations often do. Check the power draw and make sure your switch's PoE budget covers all powered devices simultaneously. Many entry-level switches can't deliver full PoE on every port at once.

I assumed our EX2200 could handle a few SIP phone adapters without issue. It did, but only after I turned off PoE on some unused ports. So double-check the math. (Mental note: I need to write this into our standard RFP template.)

Step 5: Inspect the physical delivery against your contract

When equipment arrives, don't just count boxes. Check serial numbers against the purchase order, verify firmware versions match what you approved, and confirm every port type is correct. I rejected a batch where the vendor swapped a 1GbE SFP for a 10GbE SFP without telling us. They looked identical. Actually, they were identical except for the SFP module, but the config wouldn't come up until we caught it.

Create a simple verification sheet before the shipment arrives. It takes 20 minutes, and it prevents a two-week delay later—like that $22,000 redo I don't like to think about.

Step 6: Define what you won't do

Here's the mindset that's saved me the most trouble: a vendor who says “we don't recommend that on this platform” earns more trust than one who says yes to everything. Good vendors know their limits.

For example, a Juniper MX router is great at routing, switching, and security. It's not the right tool for running your entire UC stack or managing your analog phone lines. Pair it with a telephony specialist if that's outside the network team's scope. It's okay to have boundaries.

Final warnings

Three things I still remind myself on every project:

• Don't assume that “same specifications” means identical behavior. The forwarding architecture, buffers, and management plane all matter.
• Always check the firmware support matrix before choosing a model. A feature might only be available in a newer train.
• If you're integrating legacy telephony gear, verify signaling and power requirements early. It's usually more complex than the sales sheet implies.

No checklist catches everything. But this one will help you avoid the expensive mistakes I've seen—and made.