MX68 - Software Panic/Device Reboot

AlexG
Getting noticed

MX68 - Software Panic/Device Reboot

Greetings!

I have been getting nowhere with both support and my account rep, so I'm hoping I can get some help from the community. We are currently rolling out MX68's to replace our aging MX60's. We're swapping these at a rate of about 20/week all remote sites. I have started seeing an increase in the number of devices experiencing this 'bug' that causes the MX to reboot. There's seemingly no rhyme or reason to the timing. Sometimes we can go 6 hours, other times it's only 15 minutes. The common event log messages are 'Ethernet port carrier change' for each port we currently have plugged in:

AlexG_0-1655303725054.png

I have our devices running the latest 16.16.3 patch, I also have a few of them running 16.16, I have one in my lab that my work computer is connected to running the latest RC 17.8, all still having the same issue. I worked with support who claims that the dev team has identified the issue and provided support with a 'backend fix' to help fix the issue. That device is running 16.16.3 and still is experiencing random reboots with the 'fix' applied. I'm at wits end here because it's causing an issue with our POS environment that's hyper sensitive to routing delays or failures, which happen when the device reboots.

 

Has anyone else been experiencing these issues? Have you heard anything else from support or the dev team?

2 Replies 2
rhbirkelund
Kind of a big deal
Kind of a big deal

Are you by any chance using the same subnet on both WAN side and LAN side?

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
AlexG
Getting noticed

We do have some WAN connections NAT'ing through the provider gateways (Comcast modems, Cradlepoints, etc.), however those subnets are not ones in use on the LAN side of our networks so I don't believe that to be the issue.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels