The quote came in on a Tuesday afternoon. $186,000 for 140 Extreme Networks switches and 12 Extreme Networks routers, replacing the aging Cisco hardware we'd been running for six years. The comparable Cisco quote: $220,000. My CFO looked at both numbers, then at me, and didn't have to say anything. The spreadsheet had already made the case.
I signed the purchase order on Friday.
Four months later, I understood something that no spec sheet will tell you: hardware is the cheapest part of a network migration. The project ran $32,400 over the number I put in front of my CFO. The difference between the Extreme Networks and Cisco quotes was $34,000. That's right. The savings evaporated.
I'm a network engineer who's been handling infrastructure upgrade projects for 7 years. I've personally made (and documented) 9 significant mistakes, totaling roughly $54,000 in wasted budget. The one I'm about to walk you through was the most expensive. Now I maintain our team's migration checklist so nobody else has to repeat it.
What I Actually Compared (And What I Missed)
Everything I'd read about network vendor comparisons said the same thing: compare the specs. Compare the price per port. Compare the warranty. So that's what we did. Extreme Networks switches vs Cisco switches, line by line, and Extreme won on paper. The hardware was solid. The problem was that I treated an equipment purchase like a project plan.
Here's the thing: when a vendor quotes you switches, they quote you switches. They don't quote you the design review that catches the flaws in your VLAN architecture. They don't quote you the training your engineers need before they can operate a different operating system with confidence. They don't quote you the physical layer problems that have been sitting in your IDFs for years, waiting for someone to put a multimeter on the UPS output and check what's actually happening under load.
When I compared the initial quote and the final invoice side by side, I finally understood why "the cheapest option" is almost never the cheapest option. The difference wasn't in the hardware line items. It was in everything I never asked about.
Design Services: The $14,200 Line Item I Never Questioned
The vendor's engineers spent three days on site before deployment. They reviewed our floor plans, VLAN architecture, PoE requirements, and uplink capacity. They found two things we'd gotten wrong and one thing that would have caused an outage if we hadn't fixed it first.
That work was billed as design services. $14,200.
Was it worth it? Honestly, yes. It caught a spanning-tree loop risk that would have taken down the entire campus. But I'd assumed a six-figure hardware order included basic design support. It didn't. And nobody mentioned it until the invoice arrived.
That's the pattern I now recognize everywhere: the quoted price covers the equipment. The project is billed separately. If you don't ask, you find out on the invoice.
The Training Gap: $8,500 and Three Engineers Offline
My team knew Cisco. I mean really knew it—the CLI quirks, the show commands, the little timing issues that only surface after years of production experience. Extreme Networks uses its own operating system. Some concepts transfer. The muscle memory doesn't.
We scheduled a one-week cutover. We did not schedule the fact that three senior engineers would need to learn basic operational tasks in the new environment. We sent them to training: $8,500. And they were offline for the week before the migration, which meant the rest of us were covering their tickets on top of preparing for cutover.
The "it's just a CLI" mindset costs more than almost any hardware mistake I've made. A different vendor means a different operational rhythm, and you can't shortcut that with documentation.
The Avaya Blind Spot: When "Seamless" Really Means "Sort Of"
"Extreme networks avaya" was a search term I never expected to type. But there we were, with 23 legacy Avaya switches in a satellite office that needed to connect to the new Extreme core.
Extreme Networks acquired Avaya's networking business in 2017, and the official messaging said the platforms integrate cleanly. Seamless migration, they called it. Our experience was less seamless. The legacy switches didn't appear in the new management platform until we updated firmware, and the update path wasn't straightforward because our gear was older than the integration documentation. Configuration translation? The tools exist, but they interpret, they don't translate. We spent six weeks on firmware, support tickets, and manual configuration work that no compatibility matrix accounted for.
$6,300 in integration costs, two weeks of schedule slip, and a queasy feeling every time someone said the word "seamless." The acquisition made the products compatible on paper. Your actual network is another story.
The Physical Layer: Where the Multimeter Earned Its Keep
The most expensive mistake wasn't in the network design. It was in a wiring closet, at 11 pm, with a multimeter in my hand.
It was September 2022. We'd installed 46 access switches across three IDFs before anyone noticed the UPS units in two of those closets didn't have enough capacity for the new Power over Ethernet load. The switches came up. Then we connected the security cameras, and 18 of them refused to power.
I turned to the multimeter. The output at the PDU under load read 104 volts instead of 120. Voltage droop from an undersized UPS—a problem that existed before we touched anything, but only became visible when the new gear made the demand. Then I ran a voltage drop calculation on the longest cable runs, because PoE devices at 90 meters need the power to actually arrive. The calculator confirmed what I didn't want to believe: about 30% of the camera runs were marginal. The switches were fine. The cable plant wasn't.
The fix cost $2,000 in cabling remediation, plus a week of contractor time, plus the optics of an open IDF during business hours while we re-ran cable. All because nobody had verified the physical layer before buying hardware. A $50 multimeter and a free voltage drop calculator would have caught it.
The Real Tally
Let me put the numbers in one place.
- Design services: $14,200
- Training: $8,500
- Avaya integration: $6,300
- Cabling remediation: $2,000
- Expedited shipping (because the design phase pushed the schedule): $1,400
Total unbudgeted: $32,400. That's 95% of the $34,000 difference between the two quotes. The "savings" barely survived contact with reality.
Why does this matter? Because if you're reading this while comparing network vendors right now, you're probably staring at the same kind of spreadsheet I was. And I'm telling you: the spreadsheet is lying. Not because anyone is deliberately deceiving you—though that happens—but because a quote represents equipment, not outcomes.
What I'd Do Differently
Looking back, I should have asked "what's NOT included?" before asking "what's the price?" At the time, I assumed the quote represented the cost of the project. It represented the cost of the equipment. Two different numbers.
If you're making this decision now, whether it's Extreme Networks vs Cisco or any other migration, here's my checklist:
- Ask for the total project cost, not the equipment cost. Design, deployment, cabling, UPS capacity, training, maintenance, integration. If the vendor won't itemize it, that's an answer in itself.
- Verify the physical layer before you order anything. Put a multimeter on the UPS output under load. Run voltage drop calculations on your longest PoE runs. These checks cost nothing. Skipping them costs project budget.
- Budget for integration work if you have legacy Avaya or Nortel gear. The label says Extreme Networks owns the product line now. The compatibility matrix says it should work. The reality sits somewhere in between, and "somewhere in between" is a budget line item.
- Schedule training before the migration, not during it. A different operating system means your team's shortcuts don't transfer. That cost is real, and it's predictable.
The broader lesson isn't specific to Extreme Networks. It's about how the networking industry prices projects. Per FTC guidelines, advertising claims must be truthful, not misleading, and substantiated with evidence (ftc.gov). But a quote is not a marketing claim. It is a narrow statement about what you're buying. The omissions are not technically lies. But they're not the whole truth, either.
That's why I now ask every vendor the same question: "Show me every fee, including the ones you'd rather I not see." The vendors who list everything upfront—even when the total looks higher—usually cost less in the end. The ones who don't? I've got the invoice history to prove it.