27.x firmware and 802.11ac wave 1 APs

Solved
cmr
Kind of a big deal
Kind of a big deal

27.x firmware and 802.11ac wave 1 APs

I know that the 802.11ac wave 1 APs like the MR32 and MR34 cannot run the 27.x firmware, but what happens if you upgrade a network with a mix of wave 1 and wave 2 APs?

 

I'm guessing the wave 1 APs stay on a 26.x version, but do they go to 26.8.1 if they weren't already on that version, or do they simply stay on what they were?

 

If a 26.8.2+ version comes out, will wave 1 APs in a mixed network running 27.x be upgraded or will they stay stuck at 26.8.1?

 

Are there any reliability issues running this mix or is it simply that you cannot use some of the 27.x features?

 

Thank you!

 

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
1 Accepted Solution
KarstenI
Kind of a big deal
Kind of a big deal

@cmr This network is running in this combination for at least two years.

Roaming ... Well, I never captured it in that network and I can not tell if it really roams or just disassociates and associated again. The most used SSID is PSK anyhow. I think I have to try it again with FT on my SM-enabled SSID when I am in that network again. But that will not happen in the next couple of days.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.

View solution in original post

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

Commenting for visibility 

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

This is one of my mixed networks:

KarstenI_0-1611488327349.png

The MR30H is in the process of upgrading just now. And this is one SSID without one of the 27.x features:

KarstenI_1-1611488438828.png

 

 

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
rhbirkelund
Kind of a big deal
Kind of a big deal

I can't comment for MRs because, well, I haven't tried that scenario yet.

 

But imagine Z1 teleworkers.

The Z1 is not supported on MX15.x but you can schedule an upgrade to MX15.x. What will happen is that the Z1 will "upgrade" to MX15, but since there is not support for it, the Z1 will stay on the latest MX14.x software that supports it, but still report as upgraded to MX15.x.

 

rbnielsen_0-1611488495867.png

rbnielsen_1-1611488639431.png

 

I imagine that the same applies to MRs.

LinkedIn ::: https://blog.rhbirkelund.dk/

Like what you see? - Give a Kudo ## Did it answer your question? - Mark it as a Solution 🙂

All code examples are provided as is. Responsibility for Code execution lies solely your own.
cmr
Kind of a big deal
Kind of a big deal

Thanks @KarstenI and @rhbirkelund .  With the MX/Z they are in their own networks so I'm thinking it is more simple, the MR features looks as expected, thanks for that. 

 

@KarstenI Have you been running mixed MR for a while and does roaming work properly.

 

@rhbirkelund I had a beer in Aarhus about 25 years ago and the locals thought I was Norwegian... Good times 😎

 

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
KarstenI
Kind of a big deal
Kind of a big deal

@cmr This network is running in this combination for at least two years.

Roaming ... Well, I never captured it in that network and I can not tell if it really roams or just disassociates and associated again. The most used SSID is PSK anyhow. I think I have to try it again with FT on my SM-enabled SSID when I am in that network again. But that will not happen in the next couple of days.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
KarstenI
Kind of a big deal
Kind of a big deal

I think it is important to look exactly at what is happening here. It wouldn't make any sense to upgrade a Z1 to 15x, but we are not really upgrading devices. We are just setting the intended Firmware-version for a dashboard network whatever devices are in there.

And the network can easily be configured for v15 regardless if it is a Z1 in there or a Z3. But the moment the Z1 is replaced by a Z3, the Z3 will run the configured version.

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
cmr
Kind of a big deal
Kind of a big deal

@KarstenI that's exactly one of my questions, in the MX firmware it explicitly states what version older MXs will get when 15.x is applied, but there is no statement in the MR release notes, other than to state which models won't be upgraded...

If my answer solves your problem please click Accept as Solution so others can benefit from it.
NolanHerring
Kind of a big deal

@cmr  - So the chosen solution doesn't seem to sync up with your original post questions.


Did you find out answers to them by chance?

 

I have a site on 25.13 still, and it has MR32 and MR42 and I'm looking to update the firmware but want to understand how it will function.

Nolan Herring | nolanwifi.com
TwitterLinkedIn
cmr
Kind of a big deal
Kind of a big deal

@NolanHerring after @KarstenI 's post I just upgraded all our sites and they seem to be working okay.  At the moment we have hardly any traffic so cannot be 100% sure that there aren't some issues but I'm planning to go to a mixed site next week and will do some testing to confirm that there aren't issues.

If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.