MX 18.107.4 is out STILL can't upgrade from MX 18.107.2

[RaphaelL]

Hi ,

No idea what is going on , but can't upgrade since both ( .2 and .4 ) are stable version.

I know Ryan has suggested opening cases, but a bit discouraged that this is not fixed / supported yet.

So the best suggestion is still to contact support at the moment.

[cmr]

Same here, @RaphaelL have you actually got support to install it?

[RaphaelL]

They actually can. But I hate firmware pinning

[Ryan_Miles]

It's not pinning. Pinning means statically setting the version (which also locks it/prevents upgrades).

Rather we have the ability to select any version which bypasses the bug on the UI currently.

[jimmyt234]

Same! Updated existing support case we had for not being able to upgrade to .3 either...

[Dunky]

Same here no option to upgrade, currently on 18.107.2

[Holli69]

Same here in Germany, no possibility to upgrade to 18.107.4, currently also on 18.107.2

[Holli69]

Hopefully this bug will be fixed soon.

[vilmantasr]

same.

[SimonReach]

Does anyone actually have the option to install it?

[Ryan_Miles]

As this is a bug everyone would be affected. The resolution is being worked on. If you need to upgrade your MX(s) Support can push the upgrade for you.

From what I can tell if you're on MX 17.x you can upgrade to 18.107.2.

If you're on 18.107.1 you can upgrade to 18.107.2 or 18.107.4.

If you're on 18.107.3 you can upgrade to 18.107.4.

But, if you're on 18.107.2 there's no option to upgrade to anything.

[SimonReach]

One of our networks is on 16.16.8 and our only option for that network is 18.107.2.  All of the other networks is on 18.107.2 and there are no options for any updates.

[Ryan_Miles]

I didn't have any MX 16 networks to test, but that would match my first example of upgrading from MX 17.x.

[BuntyFanshaw]

Thanks Ryan. Opened a case and had 18.107.4 pushed to my MX in less than an hour, brilliant service.

[Ryan_Miles]

For anyone that is running into this problem please open a Support case. This will help raise prioritization of a fix. 

And mention in the case note it's the same issue as my original case 10522501

[dle378]

Hi Ryan,

Newbie here on the Meraki Community forums.

Do you (or anyone on this thread) happen to know if there are any major fixes/enhancements in this version compared to 18.107.2?

[Ryan_Miles]

We include release notes for each version on the Firmware Upgrades page. Each version includes any new features, resolved issues, and known/existing issues.

[cmr]

You can also read the posts in each section, predominantly by me (shameless plug) or find them all in the community's firmware upgrade feed here: Firmware Upgrades Feed - The Meraki Community

[Ryan_Miles]

Appears the fix has been pushed out. I can now upgrade from 18.107.2.

[RaphaelL]

Also working for me. Appears to be fixed !

[cmr]

It is only fixed for me on devices already on 18.107.2, devices on 17.x still only see 18.017.2 as an option.

[CyberDingo]

18.107.4 is a patch. If memory serves me right, usually you have to update and then patch when moving to a new version number. 

[Ryan_Miles]

Correct, Mentioned in our docs https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades...

[RaphaelL]

Does that only applies to MX ? I can upgrade MR28.7 to MR29.6.1 which is a patch..

[Ryan_Miles]

Just tested that and it worked fine for me.

[RaphaelL]

I can upgrade from MX15.44 to MX18.107.4 without going to MX18.107 : 

Support told me :  "This was previously a bug not a feature but was a bug for so long that it was added to documentation, I believe it has since been resolved and you should be upgrade to the patch version directly."

Which then I asked to rectify the documentation if the firmware barrier is no longer a thing. To be continued. 

[CptnCrnch]

Same here. Great job!