Cloud Monitoring for Catalyst:
Cloud Monitoring for Catalyst Wireless FAQ
Cloud Monitoring for Catalyst Wireless Requirements
Change: Added IOS-XE 17.12.4.
MG:
Change: Added reasons when to contact Meraki support and AT&T support.
Change: Added section "Grounding and Surge Protections".
MX:
Product Firmware Version Restrictions
Change: Added note that vMX100 cannot be upgraded to MX 18.2.
Meraki MX/Z Security and SD-WAN Licensing
Change: Added "In-addition, with the launch of the Advanced Security License for the vMX, the vMX also now have to match the MX Org license tier."
Change: Added Advanced Security license tier.
MS:
MS Switch Access Policies (802.1X)
Change: Added "Critical Authentication VLAN is not currently supported in Multi Auth modes on MS Classic Switches."
Change: Added MS150.
MR:
Change: Added "In order to factory reset a CW AP using the reset button, you need to unplug the AP, hold the reset pin, power on the AP and hold the reset pin between 10 to 61 seconds, depending on the reset level you need."
IPSK with RADIUS Authentication
Change: Added section "Easy PSK".
VusionGroup Electronic Shelf Labels (ESL) Integration with MRs
Change: Added MR36; added note "Bluetooth ESL is not fully supported in MR 31.X firmware. This support is upcoming."
Change: Added health score rating.
SM:
Change: Updated section "Azure Active Directory Sign-In (Microsoft Entra ID)".
Apple Volume Purchase Program (VPP)
Change: Added "Note, the 'Revoke unknown device licenses' button requires organization administrator privilege, and is not accessible for network admins."
MV:
Change: Added "Manual App configuration still necessary. Meraki Display app does not have Managed App configs that can be used with Systems Manager."
MV Wireless Configuration Guide
Change: Added "All cameras except MV21 and MV71 support wireless configuration".
Change: Added "This data is only available via CSV export."
Meraki Vision Portal Changelog
Change: Added release notes for up to v1.23.8.
MT:
MT40 Installation Guide - Smart Power Controller
Change: Added section "General Purpose Button"; added section "Factory Reset Button".
Change: Added "Optionally, default alerts can also be disabled."
General Administration:
Trusted Access for Secure Wireless Connectivity - Setup Guide
Trusted Access for Secure Wireless Connectivity - Onboarding Guide
Change: Added "This is the expected behavior of the Windows operating system. When a wireless network is configured through a predefined networking profile, it is the profile name that shows up in the list of available wireless networks, and not the SSID. If this is the desire to have the the Trusted Access SSID to show up in the list of available networks after installing the Trusted Access profile, then the Trusted Access profile name set in Dashboard needs to be the same as the SSID."
Using the Cisco Meraki Device Local Status Page
Change: Added "By default, APs out of the box will broadcast the SSID 'meraki'. To reach MR devices, the client must be wirelessly connected to the access point (AP) using a configured service set identifier (SSID) or one of the SSIDs mentioned in the Default SSIDs section, such as "meraki-setup" SSID."
Troubleshooting local connection issues using default SSID on MR Access Points
Change: Added default SSID "meraki".
Change: Added "Tx Packet capture function on legacy Packet Capture feature is now enabled by default."
Change: Added "Please note that on the Scheduled Changes tab, if there is a batch of networks to be upgraded, the time/date on the upgrade will reflect the next/earliest upgrade in that batch."
Change: Added section "Configuring Software Only Licenses with Your Enterprise Agreement".
Meraki Firmware Release Process
Change: Updated email notification recipients: "Organization level administrators and network alert recipients".
Best Practices for Meraki Firmware
Change: Added section "Other Available Versions".
