How to Stack Meraki Switches (MS120 / MS130 / MS225 / MS250 / MS390)

Building a resilient network often requires consolidating multiple access switches into a single logical unit. Cisco Meraki offers physical stacking capabilities that simplify management, improve network redundancy, and maximize bandwidth utilization. This guide covers supported switch models, cabling requirements, deployment best practices, and decision guidance for IT administrators and procurement teams.

Table of Contents:

Part 1: Supported Meraki Switch Models & Stack Limits
Part 2: Physical Deployment & Cabling
Part 3: Dashboard Configuration & Stack Management
Part 4: Deployment Scenarios & Decision Guidance
Conclusion
FAQ

Part 1: Supported Meraki Switch Models & Stack Limits

This section outlines which Meraki switch models support physical stacking and their corresponding stack bandwidth limits.

Not all Meraki switches support physical stacking. Here is a model overview:

In summary, only MS225, MS250, and MS390 support physical stacking, with up to 8 switches per stack.

Part 2: Physical Deployment & Cabling

This section details the required cabling and ring topology for physical stacking.

Stacking requires dedicated cables for proper function:

• MS225/MS250: 40 Gbps stacking cables (0.5m, 1m, 3m).
• MS390: High-speed 480 Gbps stacking cables.

Ring Topology for Redundancy:

1. Connect Switch 1 Stack Port 1 → Switch 2 Stack Port 2
2. Switch 2 Stack Port 1 → Switch 3 Stack Port 2
3. Complete the ring by connecting the last switch back to the first

Proper physical stacking ensures the stack continues functioning even if a cable fails.

Part 3: Dashboard Configuration & Stack Management

This section explains how to configure and monitor a Meraki stack through the dashboard.

1. Preparation: Add switches to the same Meraki Dashboard network, verify firmware alignment, and power off switches before cabling.
2. Power On & Provisioning: Turn on all switches; they will download configuration and firmware.
3. Dashboard Stacking: Navigate to Switching > Monitor > Switch stacks, select switches, assign a name, and create the stack.
4. Monitoring & Troubleshooting: Dashboard shows Active, Standby, and Member roles. Replace failed members using the Clone and Replace Member feature.

Summary: Dashboard provides centralized management, stack roles, and monitoring for all physical stack members.

Part 4: Deployment Scenarios & Decision Guidance

This section provides guidance on choosing the right switch model based on deployment size and performance requirements.

Partnering with Router-switch can streamline procurement, offering in-stock genuine hardware, fast quotations, flexible payments, and technical guidance for multi-brand deployments.

Conclusion

Physical stacking of Meraki switches enables simplified management, robust redundancy, and high-speed interconnect. Using MS225/MS250/MS390 models with ring topology ensures scalable, resilient networks. Firmware alignment, proper cabling, and centralized dashboard management are critical for success. Trusted suppliers like Router-switch provide genuine products, technical guidance, and global delivery assurance.

FAQ

Which Meraki switches support physical stacking?

MS225, MS250, and MS390 support physical stacking using dedicated ports. MS120/MS130 do not.

What cabling is required for stacking?

Dedicated stacking cables are needed: 40 Gbps for MS225/MS250 and 480 Gbps for MS390. Use lengths suitable for your rack (0.5m, 1m, 3m).

Can different models be stacked together?

Generally no. Exceptions: MS210 can join MS225. MS390 stacks only with MS390.

How is the stack managed in the Dashboard?

All stack members are treated as a single logical device. Navigate to Switching > Monitor > Switch stacks for monitoring and configuration.

How do you implement redundancy in a stack?

Use a ring topology, connecting the last switch back to the first, ensuring continuity even if one cable fails.

What happens if a member fails?

Dashboard allows you to replace the faulty switch using Clone and Replace Member. Active role election ensures minimal disruption.

Does firmware version affect stack stability?

Yes. New members must match the stack firmware. MS390 stack reboot affects the entire stack; smaller models reboot individually.

How to choose the right model for deployment?

Consider stacking bandwidth, number of users, redundancy requirements, and budget. MS225/MS250 for small-medium, MS390 for high-performance enterprise environments.