MR 29.2 and 28.7 Out

Mloraditch
Getting noticed

MR 29.2 and 28.7 Out

The below releases appear to bring 28.x and 29.x to fix parity with one exception as 28.7 still has: 

  • AP performance may degrade over time (Wi-Fi 6 APs)

Otherwise just 3 known issues

 

29.2

Important note

  • Meraki APs use UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications when running MR 27 and older firmware. When running MR 28+ firmware, Meraki APs will now use TCP port 443 as the primary means for cloud connectivity. In order to maintain connectivity to the Meraki cloud on MR 28+ ensure that TCP port 443 is allowed to communicate with 209.206.48.0/20 on firewalls that are deployed upstream of your Meraki APs. (Wi-Fi 6 and Wi-Fi 6E APs)

Legacy product notice

  • When configured for this version MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3.

Bug fixes

  • General stability and performance improvements
  • AP performance may degrade over time (Wi-Fi 6 APs)
  • AP may stop broadcasting beacons on WPA2 configured SSID (MR53E)
  • AP may lose Cloud connectivity for an interval of time (Wi-Fi 6 APs)
  • SES-imagotag ESL status may display as gray even when ESL is functioning normally (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)

Known issues

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
  • No DHCP response error is seen after a client performs a successful L3 roam (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
  • SES-imagotag ESL functionality may not work (MR30H, MR33)

 

28.7

 

Important note

  • Meraki APs use UDP port 7351 for cloud communication and TCP ports 80 and 443 for backup communications when running MR 27 and older firmware. When running MR 28+ firmware, Meraki APs will now use TCP port 443 as the primary means for cloud connectivity. In order to maintain connectivity to the Meraki cloud on MR 28+ ensure that TCP port 443 is allowed to communicate with 209.206.48.0/20 on firewalls that are deployed upstream of your Meraki APs. (Wi-Fi 6 and Wi-Fi 6E APs)

Legacy product notice

  • When configured for this version MR12, MR16, MR18, MR24, MR26, MR32, MR34, MR62, MR66, and MR72 will run MR 26.8.3.

New

  • U-NII 1, 2, 2E channel support in Qatar regulatory domain (Wi-Fi 5 Wave 2 APs)

Bug fixes

  • General stability and performance improvements (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs)
  • AP may stop broadcasting beacons on WPA2 configured SSID (MR53E)
  • AP may lose Cloud connectivity for an interval of time (Wi-Fi 6 and Wi-Fi 6E APs)
  • Wireless timeline and wireless latency client metrics may be missing (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs)
  • Multicast traffic received on the wired is periodically not forwarded to clients on LAN (MR30H)
  • Channel 100 utilizing 40 or 80 MHz channel widths may show high channel utilization with no client connected (MR53)
  • When an Apple client enters an incorrect PSK the AP responds with a disassociation response instead of deauthentication response, resulting in multiple failed connection attempts from the client (Wi-Fi 5 Wave 2 APs)
  • AP may stop publishing MQTT updates until rebooted (Wi-Fi 5 Wave 2 APs)
  • AP may reboot when detecting a very high number of DFS events (Wi-Fi 6 APs)
  • AP may not sync PMKs on WPA3 Enterprise SSIDs configured with OKC (Wi-Fi 5 Wave 2, Wi-Fi 6, and Wi-Fi 6E APs)
  • Enabling FIPS may cause issues with RADIUS authentication (Wi-Fi 6 APs)
  • AP intermittently stops redirecting HTTP Traffic to the Splash page prior to Splash page login (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)

Known issues

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
  • No DHCP response error is seen after a client performs a successful L3 roam (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)
  • AP performance may degrade over time (Wi-Fi 6 APs)
  • SES-imagotag ESL status may display as gray even when ESL is functioning normally (Wi-Fi 5 Wave 2 and Wi-Fi 6 APs)

 

10 REPLIES 10
RaphaelL
Kind of a big deal

@cmr  you lost the race to the changelogs 😋

cmr
Kind of a big deal
Kind of a big deal

@RaphaelL, you have to give people a chance sometimes 😉

Macguy
Getting noticed

RaphaelL
Kind of a big deal

Please let the community know ! Feedback about new firmware is always a great help to others !

Macguy
Getting noticed

I tested a PC with a realtek adapter just now and connectivity remained solid for over 30 minutes!  Didn't have the hundreds of roaming events like before.  Looks promising, need to test with more devices. 

TimHughSmith
Getting noticed

Hey all, Anyone running 29.2 in high density? or medium density?

We are on 28.6 right now. (MR56, MR30H, MR42 mainly).

cmr
Kind of a big deal
Kind of a big deal

One of our sites is running it (and was running 29.1 before).  It does get to medium density sometimes and we haven't had any issues so far.  Site has 11x MR42s and 4x MR32s (running 26.8.3).  The busiest AP handled up to 32 clients at a time and a couple of others handled over 20.  Not too busy, but not dead quiet either.

Macguy
Getting noticed

Also found this interesting....  Bug - AP performance may degrade over time (Wi-Fi 6 APs) is a "known issue" in Firmware 28.7 but "fixed" in 29.2.  Guess those with wifi 6 environments should jump to the beta.  I'm going to upgrade 201 AP's this evening from 28.6 to 28.7.  The majority of the AP's are MR53's.  We have only a handful of MR46E at the location.  I've also seen that bug with channel 100 utilization specific to MR53. 

Logan_Keith
New here

How long until 28.7 is released to stable?

TimHughSmith
Getting noticed

Hi everyone!


It was hectic, did not get a chance to say thanks for sharing info and experiences here!

We upgraded to 29.2 beta, and we made a few other small adjustments over a period of time.
It's a dynamic high density co-working space, so it's hard to gage completely, but I think it contributed to a better user experience all round, and we had no new big issues arise.

 

Cheers,

 

Tim

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