Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Become a member of the Cisco Meraki Community today
Get answers from our community of experts in record time.
Join now- About Rattanawalee
About Rattanawalee
Rattanawalee
Just browsing
Member since Jul 30, 2025
Aug 6 2025
Community Record
3
Posts
0
Kudos
0
Solutions
Aug 1 2025
2:19 AM
Hi @RWelch , Thank you for your response! That's a good idea. We'll coordinate with the customer first.
... View more
Aug 1 2025
2:18 AM
Hi @DarrenOC , Thank you for your response! On MS410 we set RSTP mode via template, on the core switch catalyst 9300 set PVST mode 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."
... View more
Jul 30 2025
1:22 AM
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: Firmware Upgrade Upgraded to Firmware MS 17.2.1 (latest stable release at the time). Meraki Support Case Opened a support case via Meraki Dashboard. 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. 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. 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.
... View more
© 2025 Cisco Systems, Inc.
