New MR 28.4 beta firmware - plenty of Wi-Fi 6 AP fixes including the offline reboot

cmr
Kind of a big deal
Kind of a big deal

New MR 28.4 beta firmware - plenty of Wi-Fi 6 AP fixes including the offline reboot

Wireless firmware versions MR 28.4 changelog

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 MRs)

Legacy product notice

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

Bug fixes

  • General stability and performance improvements (Wi-Fi 5 Wave 2 and Wi-Fi 6 MRs)
  • Client association status is not accurately reflected when viewing the Client Details page (Wi-Fi 6 MRs)
  • MR reboots every 15-20 minutes when connection to Meraki Dashboard is unavailable (Wi-Fi 6 MRs)
  • Some client events are excluded from the Dashboard timeline (Wi-Fi 5 Wave 2 and Wi-Fi 6 MRs)
  • AP in repeater mode fails to get DHCP address after the wired connection is changed from access to trunk mode (Wi-Fi 5 Wave 2 and Wi-Fi 6 MRs)
  • Bluetooth API name field returns blank result (Wi-Fi 5 Wave 2 and Wi-Fi 6 MRs)
  • MR LED light blinks indefinitely after the “Blink LEDs” button is pushed on Dashboard (Wi-Fi 5 Wave 2 MRs)

Known issues

  • Sporadic packet loss & instability on Layer 3 roaming & Teleworker VPN SSID's (Wi-Fi 5 Wave 2 MRs/Wi-Fi 6 MRs)
  • UNII-2e channels not available for indoor MRs in Israel IL regulatory domain (Wi-Fi 6 MRs)
3 REPLIES 3
WB
Getting noticed

This could be a one off but this was a bit of a disaster for me, pushed it to our MR46s running 28.3 and straight away all of them started a weird cycle of being offline/uncontactable for 2 hours in Dashboard, then online for 2 hours, off for 2 hours, etc...

 

Dashboard was showing an error for every AP talking about them being plugged in to a different device for LLDP and from the switch level (Cisco Cataylst) I was seeing down/up flaps on the MR interfaces in line with the 2 hour cycles + duplicate CDP neighbour entries, one would show Port ID 0 and the other Port ID 1.

 

Had to roll back to 28.3 and they're stable again, won't get a chance to get a unit in the lab until Tuesday to recreate and get in touch with support.

cmr
Kind of a big deal
Kind of a big deal

It will be interesting to see what support find, were running 28.4 on the below AP models without seeing that behaviour:

 

MR33 x1

MR42 x~30

MR55 x1

MR56 x1

cmr
Kind of a big deal
Kind of a big deal

I've just upgraded a couple of MR36s to see how they behave.

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.