Meraki

ConnorL · ‎May 8 2024

Hi @JGill , looks like n755 had indeed scheduled maintenance during this time. I'll forward your feedback to the team regarding the notification piece. With regards to status.meraki.net: This page is designed to communicate incidents that impact many customers, an entire service, device type, or region. It does not reflect scheduled maintenance or service outages that fall below the threshold mentioned above.

ConnorL · ‎May 7 2024

Hi All, This issue has now been resolved, you should be able to enrol again via enroll.meraki.com, if you get an error, clear cache/cookies and try again. Thank you for your patience! Cheers, Connor.

ConnorL · ‎May 7 2024

A Factory Reset using a paperclip or pin in the reset button will clear the device contents and reset it back to factory settings.

ConnorL · ‎May 7 2024

Which shard are you on @JGill ? E.g. n146.meraki.com, you can find this by browsing Dashboard and grabbing it from the URL. There was some scheduled maintenance this morning on select few so may have been due to this.

ConnorL · ‎May 7 2024

Hey @SergioHB , We've traced this down to a new issue that we have sent over to Engineering, they are in the process of resolving this now. I will keep this thread updated with the progress.

ConnorL · ‎May 7 2024

Mind dropping me a DM with a link to the Dashboard network you're trying to enrol into?

ConnorL · ‎May 1 2024

Personally, I would advise against using this feature from purely a network security perspective, the applet requires Java and as per the KB: Clients running Windows XP, 7 or Vista will be scanned for supported anti-virus software. Non-Windows clients are not scanned. If you have Windows XP, Vista or 7 computers connecting to your network, there are bigger concerns than just Anti-Virus.

ConnorL · ‎Apr 30 2024

A quick Google shows this typically occurs during a BitLocker encryption failure, which you may have configured as part of the profile. Can you provide some additional context?

ConnorL · ‎Apr 17 2024

The MT15 uses Ethernet for PoE, it doesn't establish a data link. On my home switch for example I see it drawing power but the link doesn't come up. It uses BLE to connect to MR/MV.

ConnorL · ‎Apr 5 2024

With WhatsApp being owned by Facebook, it's likely the "Social Web & Photo sharing" rule that's causing the issue as one of the services in that group is Facebook. Try removing it.

ConnorL · ‎Apr 3 2024

@ekour1 and I spoke off-thread. It was due to a new APNS token being applied to Dashboard rather than the existing one being renewed, once this has been reverted and the correct token renewed, MDM communications should start working again without requiring a re-enrollment.

ConnorL · ‎Apr 3 2024

Cloud Archive supported resolutions can be found on the KB: https://documentation.meraki.com/MV/Initial_Configuration/MV_Cloud_Archive#Archive_Specifications

ConnorL · ‎Apr 2 2024

Mind dropping me a DM with a link to the specific device? There can be several reasons as to why this is happening: APNS is expired/invalid Profile isn't valid for the device (e.g. it's a BYOD device and the profile requires supervision) The device simply isn't syncing with Dashboard due to it being offline or connected to a network performing SSL inspection or content filtering iOS issue, try a reboot etc

ConnorL · ‎Apr 2 2024

Hey @h4dmeraki , Have you got any additional information about the devices you're trying to enrol? Such as: Manufacturer(s) and Model Number(s) The version of Android they're running Number of SM Licenses you have remaining How you're enrolling the device, either BYOD or Device Owner A screenshot of the error would be handy Cheers in advance, Connor

ConnorL · ‎Mar 26 2024

https://documentation.meraki.com/MX/Site-to-site_VPN/Tag-Based_IPsec_VPN_Failover

ConnorL · ‎Mar 25 2024

You can use a 3/4G USB modem, however, your mileage may vary and the support for these is now "best effort" as explained here: https://documentation.meraki.com/MX/Cellular/3G%2F%2F4G_Cellular_Failover_with_USB_Modems USB modems with MX/Z series devices running firmware MX 18 or newer will be limited to best effort support and will not be receiving any future firmware fixes or improvements. As @PhilipDAth, you're better off using an MG or other cellular gateway (Ethernet) plugged into the secondary WAN.

ConnorL · ‎Mar 21 2024

Sorry looks like the end bracket wasn't included in the URL, try this: Bluetooth Low Energy (BLE). Regarding your use case, this isn't something supported. Meraki does not sell a motion sensor (except for the MT20 which is a door sensor) and Meraki APs do not support Docker/containers.

ConnorL · ‎Mar 19 2024

You cannot pair devices over Bluetooth to Meraki APs. The BLE Radio is used for scanning & beaconing in addition to Meraki MT sensor communications. For more info, see: https://documentation.meraki.com/MR/Bluetooth/Bluetooth_Low_Energy_(BLE)

ConnorL · ‎Mar 18 2024

First thing to check is licensing, ensure you have enough SM seats remaining (Organisation > Licensing). Free 100 & Legacy are now depreciated and will block new enrollments, for more see: https://documentation.meraki.com/SM/Other_Topics/Meraki_SM_Legacy_and_Free_100_Retirement_FAQ

ConnorL · ‎Mar 18 2024

FYI it's more effective to use the PII API to remove client data: https://developer.cisco.com/meraki/api/create-network-pii-request/ Using the "Forget" button can lead to some unexpected consequences such as: https://community.meraki.com/t5/Dashboard-Administration/Issues-allowing-clients-back-on-network-after-selecting-Forget/m-p/79350

ConnorL · ‎Mar 12 2024

Most settings should copy across just fine if you follow the Cold Swap documentation https://documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Different_MX Only thing to double-check is static WAN IPs, re-enabling Site to Site VPN and remapping the LAN ports.

ConnorL · ‎Mar 11 2024

Looks like the unit is in routed mode, which is the new default. > All new vMXs deployed post October, 31, 2022 will be deployed in Routed/NAT Mode by default, existing vMX deployments will not be effected. If you wish to use the vMX in passthrough mode, please change the deployment settings to Passthrough or VPN Concentrator mode from the Security & SD-WAN > Configure > Addressing & VLANs page https://documentation.meraki.com/MX/Other_Topics/vMX_NAT_Mode_Use_Cases_and_FAQ

ConnorL · ‎Mar 8 2024

Hey @Duijv023 , this has been resolved now 🙂

ConnorL · ‎Mar 8 2024

Hey @Luke, Mind dropping me a DM with the case number (if you have one)? I'm curious to review this one. If this is impacting day-to-day operations too, you can request an escalation for bug prioritisation (subject to review). Cheers, Connor

ConnorL · ‎Mar 4 2024

The functionality of the radio is the same between models 😊 should you face any issues I'd recommend reaching out to Support.

About ConnorL

ConnorL

Connor Loughlin

Community Record

Badges