For the MX68CW, we wound up rolling it back to 16.16, then re-upgrading to 17.6 again. At that point, the built-in cellular started to work as expected again.   In our case with Meraki for the MX64W, it definitely does not work on 17.6, no matter how many times you roll it back and re-upgrade it to 17.6. After spending some time with support, they marked it as unexpected behavior and are sending it up to the product team. ... View more

I've had cellular connectivity problems (via USB modems and built-in modems) on several MX devices after upgrading them to MX 17.6 and created a support case, but am curious if others are experiencing similar odd cellular-related issues on MX 17.6.   Here are the details of my cellular issues, if anyone's curious:   - I upgraded a MX68CW from MX 17.5 to MX 17.6, which broke cellular functionality. The built-in cellular modem always says "connecting", but never gets to "ready" or "active". I rolled back the MX68CW to MX 17.5 and cellular functionality was restored. This device is using the built-in cellular modem.   - I upgraded a MX64W from MX 16.16 to MX 17.6, which broke cellular functionality. The USB modem is not even detected. I rolled back the MX64W to MX 16.16 and cellular functionality was still broken (the "Cellular" section on the appliance page just shows a spinner that never changes). This device is using an Inseego SKYUS DS USB modem. ... View more

We haven't deployed AnyConnect client to users, but are looking at doing so. For others reading, check out this FAQ on the Meraki documentation site for licensing information on MX.   Also to note, I believe the initial modal you're referencing indicated that AnyConnect client was not something that came with additional cost while MX's AnyConnect client support was still in beta. It is still currently in beta, per the Dashboard:     However, the point of the post isn't to dive into the licensing of AnyConnect client, but to have the links on the Dashboard updated so as to not point to an old version of AnyConnect client. Here's to hoping that happens 🤞🏻🤞🏻🤞🏻 ... View more

Thanks for the reply. I did check there beforehand, but that requires your Cisco ID to have a valid AnyConnect contract associated with it. I don't and am simply a Meraki customer with AnyConnect-capable and licensed MX devices.   Until Cisco and Meraki get the Cisco ID access to AnyConnect client downloads sorted out, Meraki should probably keep the client download links in the Dashboard updated with up-to-date client versions. ... View more