Product identity

Manufacturer SKU, MPN, and model information

Use the manufacturer’s SKU, MPN, model identifier, or configuration code to match the exact equipment and variant.

Cisco Meraki MS390 Series

Manufacturer identifier
MS390-24
Variant
Cisco Meraki MS390 Series
Region
U.S. procurement scope; verify orderability
Verified
Official product page

The selected model does not supply multi-gigabit access

MS390-24-HW provides 24 Gigabit copper interfaces without PoE. The UX and U variants have different access-speed or powered-device capabilities. The standard 24-port model's appeal lies in its modular uplinks, stack architecture and operating features, not in the faster powered edge advertised elsewhere in the family.

This matters when evaluating an installed switch for a new role. Keeping the chassis does not eliminate the need for a power solution or faster endpoint connections. A software upgrade can change supported functions, but it cannot turn the selected physical ports into another hardware variant.

Early operator reports identify a real support burden

Several MS390 owners described difficult early deployments involving dashboard connectivity, configuration delivery and long stack recovery. One reported replacing ten units with MS355 equipment after an extended series of support cases. Another, operating 20 MS390 switches, reported improvement after newer software while still encountering configuration-download problems.

The combined evidence is more useful than a simple positive or negative score. It shows both a history of costly incidents and improvement across releases. Cartennas would ask which incidents still occur on the actual installed version, how long recovery takes and whether support has identified their causes. Historical complaints should shape the test plan without becoming an unsupported claim about every current installation.

The software path has changed materially

Cisco now lists MS390 among platforms supported for cloud-managed IOS XE from 17.15 onward. The documented transition requires a suitable CS17 starting point, and later releases add capabilities such as BGP and VRF under their stated platform and licensing conditions. Older articles that describe the original MS software model as permanent are incomplete.

That is a migration project, not a reason to push an arbitrary version during a short maintenance window. Review changes in spanning tree, management connectivity and supported features against the network's actual configuration. Then stage the path on representative equipment and measure recovery. The ability to upgrade is valuable when it resolves a requirement or a verified problem, with a known return plan.

Modular uplinks and stacking still need a complete configuration

Uplink modules are separate parts of the design. The advertised 480Gb stacking figure is aggregate capacity, while StackPower is a distinct power-sharing arrangement. One does not configure or validate the other. Count installed modules, cable roles and available power before treating a stack as complete.

For an existing stack, record the application interruption during a member or uplink failure and during restoration. The early operating reports make this particularly important: a stack that eventually returns can still exceed the site's maintenance window. The acceptance target should be an observable service outcome, not only a dashboard status change.

Licensing and support frame the retention decision

MS390 has Enterprise and Advanced feature tiers. Adaptive Policy is among the features that require the appropriate tier, and co-term organizations have edition-consistency requirements. An existing license mix therefore can affect a proposed change beyond the price of one switch. Confirm the organization's actual licensing model and target features together.

The MS390 series sales milestone was March 28, 2025, while the listed support endpoint for MS390-24 is March 28, 2032. That is a longer runway than several classic MS families. Retention can be reasonable when the current deployment is stable and the supported software path addresses future needs. Replacement is stronger when unresolved incidents and recovery work continue to outweigh the hardware's remaining service value.

Onsite installation support

Need help installing or replacing the Cisco Meraki MS390 Series?

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

Judge an installed MS390-24 on its current incidents, recovery behavior and supported software path. Retain it when those meet the operating requirement; replace it when ongoing support cost and disruption exceed the benefit of the remaining March 2032 runway.

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.