MX 18.107.2 firmware killing or disabling USB port on MX65's
We've recently had 117 Meraki MX65's receive MX 18.107.2 (upgrading from MX 16.16.9), and now the USB LTE dongles plugged into their USB ports for a failover link no longer show in the dashboard on the networks. The cellular line in the network connectivity graph ends on the date these upgraded.
We've tried rebooting devices, no change.
We've tried failing over to the cellular to see if it kicked in, nothing.
I've tried 3 separate LTE dongles (several generations of the same "supported" device), all act as though they are dead.
The LED's on the dongles that show power and connectivity no longer light up either (but do if plugged into a computer). It's as thought MX 18.107.2 either turned off or killed the USB port.
Has anyone else seen or experienced this?
And reading other comments, it sounds like we should step right back to MX 16.16.9 for complete reliability, especially as there is RADIUS involved... Is this a fair comment?
(Yes, I have logged a case with Meraki Support. I'm curious to see if anyone else has experienced this - as MX 18.107.2 has been out for at least 6 weeks.
Just noticing this with my MX65's after upgrading late last month. I've got two MX65's with the exact same issue that were working fine before 18.107.2. Tried upgrading to 18.107.4 and still see the problem. I have an alternate MX67 at another site where it's working fine.
Were you able to find a resolution to the issue? I just opened a support case to see what they say. And I understand they are pushing us off of USB modems, but the modem is on the supported list and works fine on alternate hardware.
A quick update here - so the root issue for the USB dropping from the MX65's under MX 18.x firmware was that some bad coding meant that the MX65's were not providing enough power over the USB for device to run - such as USB LTE dongles. So this has been resolved in firmware version MX 18.107.5 . This might be the only version it is resolved for, we wait to see.
I've done a huge amount of testing upgrading the firmware to MX 18.107.5 under various scenarios and I can confirm that this firmware version does 100% fix the issue.