Ongoing Stack Port Issue with MS-410-32 Switch

Rattanawalee
Just browsing

Ongoing Stack Port Issue with MS-410-32 Switch

We have been using MS-410-32 switches in a stack configuration since December 2025, with a direct stacking connection (port 37 to port 37). From the provisioning stage, we have consistently encountered a critical issue where customers were unable to access services, prompting us to manually reboot the devices.

Upon reviewing the logs, we consistently found the following messages:

Switch 1:
port: 37, old: 40Gfdx, new: down

Switch 2:
port: 37, old: 40Gfdx, new: down

 

Troubleshooting Steps Performed:

  1. Firmware Upgrade

    • Upgraded to Firmware MS 17.2.1 (latest stable release at the time).

  2. Meraki Support Case

    • Opened a support case via Meraki Dashboard.

  3. Stack Cable Testing

    • Used a different stack cable from another site.

    • Reconnected using cross-stack configuration (port 37 to port 38 and port 38 to port 37) as recommended by Meraki Support.

    • However, the same log (port down) appeared immediately after connecting the stack cable.

  4. Cross-Device Testing

    • Tested the same stack cable with MS-210 switches – no issues or port down logs were observed.

    • Reconnected the cable to the MS-410 stack again for further monitoring.

  5. Extended Monitoring

    • After 10 days, the same symptoms reappeared:

      • Stack ports went down.

      • Both MS-410 switches rebooted unexpectedly.

Switch 1

Port 20 STP role change disabled → designated
Port 20 status change down → 1Gfdx
Port 20 STP role change designated → disabled
Port 20 status change 1Gfdx → down (repeats several times)
Port 19 STP role change disabled → designated
Port 19 status change down → 1Gfdx
Port 19 STP role change designated → disabled
Port 19 status change 1Gfdx → down
Port 37 status change down → 40Gfdx
Port 37 status change 40Gfdx → down
Port 38 status change 40Gfdx → down

*** Logs show STP role/status changes across all ports, indicating a full topology change (not isolated to port 19/20)

 

Switch 2

port: 37, old: 40Gfdx, new: down
 
Does anyone have any ideas on how to resolve this issue? We have been experiencing this problem since January 2025 and have not been able to fix it yet. It is causing significant impact on our operations.
5 Replies 5
DarrenOC
Kind of a big deal
Kind of a big deal

Hi @Rattanawalee , might be a daft question but are the MS410’s setup as your STP Root for the network?

 

What happens if you unstack the switches and run on a single switch for a period? Would be interested to see if you have ports resetting at that point? 

Id push for an RMA on both switches if TAC can’t find an error and resolve.

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Rattanawalee
Just browsing

Hi @DarrenOC ,

 

Thank you for your response!

On MS410 we set RSTP mode via template, on the core switch catalyst 9300 set PVST modeScreenshot 2025-08-01 at 16.07.42.pngScreenshot 2025-08-01 at 16.11.03.png

 

 

We used to connect a stack cable between port 37 on switch 1 and port 37 on switch 2. Recently, we migrated all service cables to use only switch 1, and all services are currently working fine but our customer requires dual stack cables to prevent a single point of failure.

 

However, when we contacted TAC, they only told us to isolate the issue ourselves and didn’t offer to remote in or assist with troubleshooting."

RWelch
Kind of a big deal
Kind of a big deal

For what it's worth - you might consider giving MS17.2.2 a try.

I worked with Support for almost 2 weeks to resolve problems experienced with MS17.2.1 on the MS425 series.  

 

Have not had any more issues since upgrading to MS17.2.2.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Rattanawalee
Just browsing

Hi @RWelch ,

 

Thank you for your response!

 

That's a good idea. We'll coordinate with the customer first.

GIdenJoe
Kind of a big deal
Kind of a big deal

When physical stacking ports go down and your stacking cables have been tested then you simply have a crashing switch and are in need of an RMA.  That support engineer shouldn't have left you by yourself and should have helped more.

I suggest you call in about the case and friendly ask for an RMA.

Do know that MS 410's are practically no longer in supply and the chances they will give you a C9300 variant instead is possible.  That would be a C9300-48S.  In that case make sure they replace both stack units since you cannot stack a C9300 with an MS410 obviously.  And they will have to convert your licenses.

I recently had a simple issue with a MS410-16 stack and they replaced it with C9300-24S switches.  And had those issies where they only replaced one at first ;p.

Get notified when there are additional replies to this discussion.