I have an automated task that should have rebooted 3 of our MX64 appliances last night. The API was unable to perform the reboot it seems. I didn't check the logs from my automated script, but I did go into the Dashboard to manually restart the devices. I received an error when doing so:
I've tried maybe 6 different MX64 and MX67 appliances from the dashboard, all with the same error and they do not reboot.
If you are curious why we restart the MX at all, it is because the Cellular modem in the USB port disappears from the list of interfaces. Using the API, an automated script determines the problem and if it is after-hours, reboots the MX. Upon reboot, the USB modem is visible once again. The problem with rebooting MX occurs for devices with and without a USB modem and an MX67C with the internal cell modem.
My search for "malformed request" in the community had a lot of hits because of the word "request", but I didn't come across "malformed request". So I don't know what to do.
Solved! Go to Solution.
Hi @Grumples ,
Not seen that one before. Indicates that you’ve inputted something incorrectly but we know that’s not the case. What MX firmware are they running?
have you raised this with Meraki support?
If you can't reboot the appliance and assuming you are running recent firmware, then that must be a fault. I would contact support.
It's a known issue that we're tracking and resolving currently, please open a support ticket so we can log that you're experiencing this and provide status updates via the case when we receive updates from the PM team.
@ConnorL , anything to do with this issue noted in firmware 14.50 and also a previous bug in 14.46? We’ve held back upgrading any MX68’s.
We are having the same issue. meraki support is useless by saying "development team is working on the issue". Yet they provide no timeline, no SLA, and no idea how many hours, days, weeks. This is ridiculous for a remote mgmt solution to offer next to nothing to customers as far as feedback goes.
Hi @yepper - I think useless is a tad harsh! Especially given the current working environment we find ourselves in. If the developers are aware of the issue and are working on it then what else can you/we do at the moment. One can't promise a fix at the flick of a switch!!!