Meraki MS390 vs Catalyst 9300: The Software Path Now Matters More Than the Old Labels

The old comparison no longer describes the current choices

An MS390-versus-Catalyst comparison that assumes the former cannot run the current IOS XE cloud platform is out of date. Cisco's cloud-configuration support table includes MS390 and C9300-24T from IOS XE 17.15 onward. That does not make every software release, feature and configuration path identical. It changes the first buying question from a brand label to the specific management mode the organization intends to operate.

Use MS390-24-HW and C9300-24T as equivalent unpowered 24-port Gigabit access examples. Both use modular uplink options and support a 480Gbps-class data stack. Neither selected model powers endpoints. When evaluating quotes, identify the uplink module, optics, power supplies, stacking cables and license entitlements rather than comparing a complete configured unit with a bare chassis.

Separate the hardware from its configuration authority

Catalyst hardware may be operated through a device-configuration workflow or a supported cloud-configuration workflow. The available commands, features and management experience depend on that choice. A feature advertised in a general IOS XE guide is not automatically exposed in cloud configuration, and a cloud release feature requires the listed software and license prerequisites.

This matters when the campus relies on particular routing, spanning-tree or troubleshooting functions. Cisco's release documentation describes feature additions and remaining exclusions by release. Write the required behavior down first, including how the support team observes it, then validate it on the intended mode. Choosing the most familiar chassis cannot compensate for a missing function in the selected configuration path.

Selected configurations and purchasing implications
Decision	MS390-24-HW	C9300-24T
Selected access hardware	24 Gigabit ports, no PoE	24 Gigabit ports, no PoE
Uplinks	Specify the installed module	Specify the installed module
Cloud IOS XE support	Listed from 17.15; conversion prerequisites apply	Listed from 17.15; management mode and entitlement apply
Purchase decision	Assess the installed fleet and upgrade path	Evaluate a current configured procurement option

Treat the MS390 transition as a controlled change

Existing MS390 installations need their documented upgrade prerequisites checked before moving to cloud-managed IOS XE. The documented CS17 starting requirement and the conversion sequence are part of that process. An upgrade proposal should show the starting version, intermediate requirements, expected interruption and recovery procedure for each stack, not just the destination release number.

Historic owner reports explain why this deserves care. Some MS390 operators reported repeated replacement or configuration problems; others described improved operation on later software. Those accounts concern particular fleets and earlier releases. They are useful evidence of what to test, but they do not establish the failure rate of today's software. Similarly, Catalyst 9300 owners have reported faults involving stack connections and individual hardware, so changing labels is not a substitute for a tested deployment.

Power stacking does not duplicate the campus path

The data stack and power-sharing arrangement are separate designs. A power stack can help use available supplies, but it cannot preserve traffic through a failed chassis or restore an upstream connection that exists only on that member. Calculate the remaining power and uplinks after each intended failure, then distribute essential endpoints and links accordingly.

For a replacement exercise, verify stack identity, configuration recovery and uplink reachability before moving user connections. Confirm that the monitoring system identifies the correct device and port after the change. A functioning stack with confusing inventory can still lengthen the next outage because the remote engineer cannot reliably direct onsite work.

Our recommendation

Cisco lists March 28, 2032 as the support end date for the MS390-24 model considered here. An installed fleet therefore deserves a current software and requirements assessment before a blanket replacement decision. For a new purchase, favor the current supported Catalyst configuration that matches the intended operating model, rather than acquiring retired MS390 stock on the assumption that it is the only Dashboard-compatible route.

Cartennas would retain an MS390 installation that passes its required workflow and upgrade tests, while planning its lifecycle deliberately. Select Catalyst 9300 when its available configuration modes, hardware options and procurement path better fit the next standard. The decisive evidence is the behavior of the exact software and topology the team will run.

Onsite installation support

Need help deploying the technology you select?

Cartennas provides onsite installation, replacement, rack mounting, cabling, and Smart Hands support for business network equipment across the United States.

Request Installation Support

Cartennas assessment

Cartennas recommends comparing the intended configuration mode and release first. Keep a proven MS390 fleet where it meets the requirement, and use the current Catalyst purchasing path for a new standard after verifying the necessary cloud or local capabilities.

Cartennas analysis of manufacturer specifications, applicable technical documentation and available firsthand operating evidence. Review methodology. Cartennas provides product procurement and onsite services. Product review terms.

Official manufacturer information

Confirm the exact model, specifications, licensing, warranty, and support terms directly with the manufacturer.

Product information was checked on September 5, 2026. Specifications, licensing, warranty, availability, and pricing can change.