Juniper Hardware Compatibility Tool: What to Check Before You Buy or Upgrade an MX80
Let me save you a few clicks. If you came here looking for a 2780 blood pressure monitor, this article isn't that. If you were hoping for a landscaping comparison of cypress vs juniper trees, I can't help you there either. But if you're trying to figure out whether a Juniper MX80 will support the optics, power supplies, or modules you need, you're in the right place.
I'm a quality and brand compliance manager at a network infrastructure company. Part of my job is reviewing hardware compatibility before anything gets ordered or put into production. I've rejected more than a few purchase requests because the part number wasn't on the compatibility report. The mistake I see most often? Someone skips the Juniper Hardware Compatibility Tool, assumes a part will work because it has the right connector, and then has to explain to leadership why the maintenance window failed.
Here's the thing: there is no universal answer to 'is this hardware compatible?' It depends on your scenario. So let me walk you through the three situations I see most often.
Scenario A: You're buying new hardware
When I first started reviewing hardware specs, I thought the compatibility tool was mostly for people designing a new network from scratch. That's true, but the important detail is that you have to run it with the right Junos version. Not the version you're currently using—the version you plan to run after the deployment.
According to Juniper's official HCT documentation on the support portal, compatibility is always platform-specific, release-specific, and hardware-specific. That means 'will this work?' has to be asked as three questions: Will it work on an MX80? Will it work on the Junos release I'm going to run? Is the exact part number listed as supported? If you can't answer all three, you haven't checked compatibility.
Most procurement people ask 'is this Juniper MX80 supported?' The better question is 'is this exact optic or power supply supported on the MX80 with Junos 22.2R1?' Those are not the same question.
Before you approve a purchase order, do this:
- Open the official Juniper HCT on Juniper's support portal.
- Select the MX80 platform.
- Select your target Junos release.
- Add every transceiver, power supply, and module you plan to buy.
- Save the compatibility report and attach it to the PO.
The report output looks dry, but it's your best audit trail. If you ever need to explain why you chose a specific optic, you can point to the date-stamped HCT output. That matters in a procurement review, especially when someone else is trying to approve a cheaper part that isn't listed.
One thing I've learned: don't rely on a screenshot from a colleague. The HCT changes as Junos releases and hardware qualifications change. Always run it yourself, on the date you're making the decision.
If a part number isn't in the HCT output, don't buy it for a production network. That's not me being cautious; it's me being practical. An unsupported optic might work in a lab for a week, but you don't want to be the one testing it during a live upgrade.
Scenario B: You're upgrading an existing MX80
This is where the conventional wisdom gets dangerous. Most people assume that if a part is already installed and running, it's compatible. My experience says otherwise.
In early 2024, I watched a customer run an MX80 for over a year with a third-party SFP+ optic. It worked on the version they had deployed. Then they planned a maintenance window to upgrade Junos. When they ran the HCT for the target version, that same optic didn't appear on the supported list. The hardware hadn't changed. The Junos version changed, and with it, the compatibility matrix changed.
I don't remember the exact release number without checking my notes, but the pattern was clear. If they had checked the HCT before ordering, they would have known two weeks earlier. Instead, they had to scramble for a supported optic and reschedule the maintenance window.
So if you're upgrading an existing device, run the HCT before you schedule the maintenance window. Look at the report for the target release, not the current release. Pay attention to transceivers first, then power supplies. Those are the items that quietly disappear from supported lists.
It's not only optics. I've seen power supplies and fan modules get dropped from support lists too. A router can boot with an unsupported power supply, but you won't always get predictable behavior under load.
Also check whether the hardware is end-of-life or listed as 'will not be supported' in the next major release. The HCT often shows that before your normal support notice arrives. I've seen teams plan a refresh one quarter late because they didn't check this until after the upgrade.
I know that feels counterintuitive. You've been running this network for two years and nothing has failed. That's exactly why a compatibility check matters more after an upgrade: the risk isn't what you've already seen fail. It's what you haven't tested yet.
Scenario C: You're troubleshooting a production issue
The most frustrating part of my job is seeing a perfectly reasonable-looking config blamed for an intermittent issue that is actually caused by unsupported hardware. A vendor can say 'we tested it in our lab' and still be telling the truth. That doesn't mean the part is on Juniper's supported hardware list for your specific platform and Junos version.
If you have an MX80 throwing odd link flaps, high error counts, or unstable behavior, and the config looks clean, stop before you make the problem worse. Run the HCT with your actual platform and Junos version. Look up every part number. If something in your device isn't listed, you've found a very likely root cause.
The tricky part is that an unsupported part can still work for months. So when it finally fails, everyone assumes the config changed or the cable went bad. Running the HCT early saves you from two weeks of late-night triage.
Your first reaction might be to call your vendor. That's fine, but you'll have a better conversation if you bring the HCT output. It shows whether the part is even supported before you start arguing about who is responsible.
This is not about blaming the hardware vendor. It's about giving your network team a defensible answer. When you can point to an official compatibility report and say 'this part is not supported for this combination,' you've moved the conversation from opinion to verification.
How do you know which scenario you're in?
If you're not sure, ask yourself these three questions:
- Am I buying hardware in the next month? → That's Scenario A.
- Am I changing the Junos release on an MX80 that already exists? → That's Scenario B.
- Am I troubleshooting an unexplained issue on a network that's already live? → That's Scenario C.
You can be in more than one. A common situation is buying new optics for an existing router that's also due for a Junos upgrade. In that case, run the HCT twice: once for the current release, and once for the target release.
What if the tool says a part is compatible, but you're still having issues? Then start looking at configuration, cabling, or signal strength. The compatibility report is a gate, not a guarantee. It doesn't replace field testing. It just tells you that the combination is officially supported.
I'm not saying you should never use third-party hardware. In some non-production environments, it's a reasonable tradeoff. Just know what you're signing up for. If the part isn't in the HCT for your platform and release, treat it as a lab experiment, not a production dependency.
I'd rather spend ten minutes in the HCT with you now than explain later why a $300 optic caused a $15,000 maintenance event. An informed customer asks better questions, and better questions produce faster decisions. So before you sign the PO or schedule the upgrade, get the report. At least, that's been my experience with MX80 deployments that come through our quality review. The report won't tell you what to do, but it will tell you what's actually supported—and that's where every decision should start.
