- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Error performing MX firmware upgrade from 15.44 to `16.15
Hi,
I am trying to do an MX firmware upgrade from 15.44 to 16.15 under a template but it would not let me do it.
Receiving the error below:
There were errors in saving this configuration:
- Firmware Upgrade failed due to the following node_groups: Test_Network - appliance. Firmware Versions MR 28 and MX 16 require nodes to be able to contact Meraki's Device to Cloud Connectivity service over TCP port 443. One or more of your Meraki devices are unable to communicate with these new servers. For more information about this upcoming change and how to resolve the connectivity issue, please go to https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Device_to_Clou....
Created FW rules to connect to any-any. But the issue is still the same.
Advance thanks for your response.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So one of the devices connected to the template cant connect to meraki on port 443.
But sometimes you get this error even if communication is possible. Best to call meraki support or create a meraki case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So one of the devices connected to the template cant connect to meraki on port 443.
But sometimes you get this error even if communication is possible. Best to call meraki support or create a meraki case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the response.
I' raised a Meraki case and after a few hours it was fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a pesky error that often clears up on its own after some time. But, if you need the network/template upgraded now as ww mentioned open a Support case. Or, you can send me (in DM) your org URL and I can do it for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found that this error often happens when scheduling an upgrade, but if you say upgrade now then it works... 🤦♂️
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am running into this also, but if I tell it to do it now, it still gives the error. It could very well be a template thing, but our MX64's don't get the message, but the Z3's do.
