MS130-24/48 stop routing TCP traffic, lose manageability until rebooted

ITSDigital
Here to help

MS130-24/48 stop routing TCP traffic, lose manageability until rebooted

Over the course of the last year, since we started deploying MS130 switches into 40+ sites, we periodically find them dropping TCP traffic and losing manageability.

 

The MX stays online, and any other MS120 switches are that are directly uplinked to the MX.

 

Our environment is fairly simple:

MX with dual WANs connected to INET

MX downlinked to MS (1 or more).

MS connected to APs and Windows PCs.

 

Any ideas on what could cause this type of issue, or would it be a hardware RMA issue? 
The issue only occurs intermittently. Firmware in use: MS 17.2.1

 

Also the incident which occurred today had this in the portal:

 

ITSDigital_1-1760344244232.png

 

 

2 Replies 2
DarrenOC
Kind of a big deal
Kind of a big deal

What are Meraki support/TAC seeing and reporting on this one?

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.
PhilipDAth
Kind of a big deal
Kind of a big deal

I'm not seeing any issues, but we are running 17.2.2.

 

It says it has resolved these issues from 17.2.1:

 

General fixed issues

  • Fixed an issue that caused switch stacks to learn MAC addresses from ports in the STP blocking state, triggering MAC flap messages in the event log
  • Fixed a bug that caused an unexpected LACP discarding state when connected to third party firewalls
  • Resolved an issue that sometimes prevented communication between VLANs on switches in stack configurations
  • Resolved a bug that caused the Ping tool in the Client details page to fail to display data on Dashboard for wired clients
  • Resolved a bug that occasionally caused switches in stack configurations to crash and reboot

 

Ms130 fixed issues

  • Fixed a bug that sometimes caused switches to fail to deliver PoE, and could cause all ports to display as disconnected in Dashboard
Get notified when there are additional replies to this discussion.