I Was Wrong About Aruba: HPE CX Switches Are Now in HPE Mist
My recent attendance at HPE Discover opened my mind to the HPE Aruba and Juniper merger. Here's what I think after observing HPE CX switches being used to operate the network at HPE Discover.
When HPE completed its acquisition of Juniper Networks, the concern from people running Aruba or Juniper gear was legitimate. HPE already owned Aruba. Juniper already had Mist. That is a lot of overlap, and in most acquisitions, overlap means a product line is eliminated.
My assumption was that Aruba Networks would get the shorter end of that deal. Mist had the momentum. The AI story with Marvis, the cloud-native architecture. Aruba felt like the legacy play but they had excellent hardware. If you had just refreshed your access layer with HPE CX switches or deployed Aruba wireless across your campus, you had reason to wonder whether you had bet on the wrong product line.
That concern is starting to look like it was wrong. I saw this firsthand at HPE Discover, where CX switches managed in HPE Mist were running the conference network.
What Is Actually Happening
HPE Networking CX switches are now supported in the HPE Mist dashboard, with the same AI operational toolset used for Mist-managed wired and wireless.
It is a strategic message. HPE is not collapsing its product lines into one. It is connecting them. The direction looks like convergence, not elimination.
The Hardware Being Supported
The initial supported CX switch lineup includes the HPE Networking CX 6400, CX 6300, and CX 5420.
The CX 6400 is a modular core switch. The CX 6300 covers distribution and access. The CX 5420 handles high-density access layer deployments. If you are running a modern HPE campus network, there is a good chance at least one of these is already in your stack.
Juniper did not start with a handful of low-end switches to check a compatibility box. They started with the platforms that matter for enterprise deployments.
More importantly, CX switch support in HPE Mist shipped faster than support for Juniper's own EX switches.
Onboarding: Same Workflow as Mist APs
One of the first practical questions is how much lift the migration into Mist actually takes. Not much.
CX switches onboard into Mist using QR claim codes, which means zero-touch provisioning. You scan the code, the switch claims into your Mist organization, and it is ready to manage. If your team already handles Mist AP deployments, they already know this workflow. There is no new process to learn.
For anyone who has spent time doing manual switch provisioning, that is a big operational win.
What You Get Once It Is Running
Feature parity with first-party hardware never comes immediately in a cross-vendor integration, so the specifics here matter.
With CX switches managed in Mist, you get telemetry feeding into the same dashboard you use for wireless visibility. Wired Service Level Experience (SLE) is included, which means Mist is measuring wired client performance against the same baseline it uses for wireless. That gives you consistent reporting and troubleshooting across both domains instead of two separate tools.
Marvis AI actions extend to the wired side. When Marvis identifies a problem, the result is actionable next steps rather than just flagging that something is wrong. That's incredibly helpful when you are trying to triage at 7am.
Dynamic PCAP is available on the wired side, so when something breaks on a CX switch port, you have packet capture without needing to manually configure a SPAN session and set up an external capture tool.
Day-Two Management Inside Mist
Getting devices onboarded is one thing. Running them at scale over months and years is the actual test.
CX switches in Mist support switch templates, which means configuration changes do not require touching each device individually. Switch roles let you define how a switch functions within the topology, and Mist applies the right policies and defaults without manual intervention every time you add a device.
Configuration management happens inside the Mist dashboard. You can actually manage the CX infrastructure from Mist. That reduces the number of interfaces your team has to maintain.
Why This Integration Moved Faster Than Expected
The CX switch integration into Mist happened faster than Juniper's own EX switch line. The CX platform was built with a native REST API from the start. Mist did not have to work around a legacy network operating system to integrate.
This is worth noting beyond the context of this specific integration. Infrastructure that is built with open, programmable interfaces gets integrated faster and gets supported by more platforms.
The Takeaway
I was wrong about Aruba being the casualty of this merger. What I saw coming out of HPE Discover suggests these two product lines are being wired together, not one being shut down.
