MR unable to upgrade to 28.6

jocheneffpunkt
New here

MR unable to upgrade to 28.6

Hi Guys

 

I have 4 different networks with different MR Aps

 

Network 1 mostly MR53E, few MR36 and to MR76 (all wired)

Network 2 only MR53E (one wired, 4 are using mesh)

Network 3 only MR53E (all wired)

Network 4 mostly MR53E, 4 MR46E and 2 MR76 (all wired except one MR76 and one MR53E)

All on 28.5 Firmware

 

Last Week i scheduled an update on Network 2 to 28.6 (its a little one,so perfect for testing), everything worked fin so i upgraded Network 2 an 3 to 28.6 and also everythings fine

 

But i'm unable to upgrade to 28.6 on Network 4 because i'm getting this error message

 

"Firmware Upgrade failed due to the following node_groups: Althengstett. 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...

 

Any ideas or hints what i can do?

 

on this Network 28.5 is already running so there shouldnt be block anything

 

Thank you so far

9 Replies 9
DarrenOC
Kind of a big deal
Kind of a big deal

Hi @jocheneffpunkt , have you confirmed that Network 4 isn’t being blocked on port 443?  There was a recent change by Meraki whereas this port was being used as the primary for dashboard comms

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

@jocheneffpunkt try doing an upgrade now instead of scheduling it, that has worked for me in the past

jocheneffpunkt
New here

Thank you for your replies

 

@cmr upgrade now throws the same error als an scheduled update

 

@DarrenOC

Imho we dont block any outgoing traffic but i've asked our RouterAdmin(thats not my job:) )

 

Has the 28.5 Firmware the same requirements or did they change in the 28.6? Because the Network is working fine since April 2021 an imho i already did an update in early October 2021

hi @jocheneffpunkt 

 

Please see below

 

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Meraki_Device_to_Clou...

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.
jocheneffpunkt
New here

I've talked to our Router Admin

 

"Wir blockieren ausgehend nichts. "

 

We don't block anything outgoing

ww
Kind of a big deal
Kind of a big deal

It not always working good. sometimes you have to call meraki support to force it.

PhilipDAth
Kind of a big deal
Kind of a big deal

This is almost certainly a false positive then.  As @ww says, try contacting support.  Rebooting the APs may resolve it as well.

jocheneffpunkt
New here

Good Morning

 

I've rebooted all 23 APs but i'm not able to perform or schedule the update 😕

 

I ill contact the support, maybe the have a solution for this case

 

This Customer had a similar problem https://community.meraki.com/t5/Dashboard-Administration/MX67-fail-to-upgrade/m-p/136492

IainW
Here to help

Slightly off topic but I was getting this error when trying to upgrade a series of MS switches from 14.33.1 to 15.21.  The switches were directly connected to an MX and a dirty Internet connection - i.e. everything allowed out and no filtering.

 

Meraki Support resolved this for me by pushing the upgrade from their side.

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