Meraki

ConnorL · ‎Nov 13 2023

I'd advise to open a Support case if you haven't already, as Support should be able to take a look at the state of the PoE. Also worth trying to move the camera to a different switch port, if the issue still occurs you may wish to reach out to the manufacturer to determine if there any known compatibility issues, or PoE specifics that may be causing this issue.

ConnorL · ‎Nov 13 2023

I assume you're referring to MT30-HW Smart Automation Button, in which case indeed you need an MR Access Point or MV Security Camera as a gateway in order to use it. 3rd-party gateways are not supported. For more info, see: https://documentation.meraki.com/MT/MT_General_Articles/MT_Frequently_Asked_Questions#How_do_MT_sensors_communicate_with_the_Meraki_dashboard.3F

ConnorL · ‎Nov 13 2023

Depends on where the other MV2 is deployed, if the MV is in the same room/floor as the sensor in theory you shouldn't have any issues. MV 5.1 contains: "Improved connectivity performance for MT sensors" MV 5.2 contains: "Resolved an issue where MT connections can become unstable in dense environments"

ConnorL · ‎Nov 13 2023

You cannot define which gateway an MT will use. As per the MT Frequently Asked Questions KB, an RSSI of -85 or lower will result in the connection being rejected. So long as your MV2 is running MV 4.17+ firmware, nearby sensors should connect to it. I'd recommend running the latest stable (MV 5.3) to ensure you're not potentially hitting any resolved issues. I'd advise opening a support case (or DM'ing me the case number if you have one already open) so additional troubleshooting can be carried out.

ConnorL · ‎Nov 9 2023

It could be a number of issues, usually it's connectivity issues from the Meraki device to Dashboard, for more info see: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Alerts_and_Notifications/Dashboard_Alerts_-_Connectivity_Issues#Bad_internet_connection

ConnorL · ‎Nov 9 2023

Have you claimed the APs into a Dashboard network and applied a Radio Profile to them before you put the device into survey mode?

ConnorL · ‎Nov 9 2023

All sorted now @beks88_ - thank you again for the heads up! Should you continue to have any issues please drop me a DM.

ConnorL · ‎Nov 9 2023

Hey @BlakeRichardson , We're aware with an issue occurring sometimes when using a HTTPS URL, you may see the error message "Android Wallpaper - System wallpaper image URL is not valid: An error occurred." This is being worked on now by Engineering and should be resolved shortly. Alternatively, using a HTTP URL may result in the device using the default background. Do drop me a DM with the case # or link to your SM profile so I can take a look if you're using HTTPS and the profile has saved correctly. Cheers, Connor

ConnorL · ‎Nov 6 2023

Hmm, that's certainly one that we'd need Zebra's help with, as ADB logging should help pinpoint what's preventing the device from booting into the launcher. I'll DM you for a little more info.

ConnorL · ‎Nov 6 2023

Engineering are taking a look at this now and it should be resolved soon, as soon as I've been given the heads up I'll let you know - thanks again @beks88_ for the heads up!

ConnorL · ‎Nov 3 2023

Hey @beks88_ , During the Apple Automated Device Enrollment set-up process (i.e. when you're first setting up the device), we do not support using Azure AD and instead it'll fall back to using Meraki credentials (SM > Owners). Appreciate the different KBs make this a little confusing so I'll request some clarification is added here. Cheers, Connor

ConnorL · ‎Nov 3 2023

It completely depends if Zebra's Android implementation includes Google Play services, that's the core requirement for SM to function. What issues are you seeing (i.e. errors, specific behaviour) after you have enrolled the device into Device Owner mode? It should be noted that SM no longer supports Android 9 and below, so you may wish to check what version of Android the Zebra scanner is running.

ConnorL · ‎Nov 3 2023

Thanks for flagging @beks88_ , I see the same on my org so I'll file a bug report internally.

ConnorL · ‎Oct 20 2023

That's not something Apple allows to be configured via MDM unfortunately. Similarly, it's not something we support configuring for Android. By default most 4G devices will have VoLTE enabled by default. You cannot actually hide the Settings app on iOS and the user should still be able to enable 4/5G and VoLTE regardless of how locked down the device is (unless it's in Single App Mode of course).

ConnorL · ‎Oct 18 2023

This happens when the SM app cannot determine the system/device name during enrollment, if we cannot determine other identifiers (such as name, system name etc) we'll fall back to using the IP address. We have a bug / feature request internally for this particular issue, in the meantime, you can manually rename the device in Dashboard by clicking "Edit details"

ConnorL · ‎Oct 18 2023

We don't have any particular name for the OS it runs, Meraki devices run Meraki OS. MR runs MR firmware, MS = MS firmware etc.

ConnorL · ‎Oct 7 2023

Always happy to chime in when I can be of help! Thank you for the call-out and thank you everyone for making the community a helpful and collaborative space 🎉

ConnorL · ‎Oct 3 2023

You're describing the difference between a soft failover and a hard-failover. Soft Failover: When both the HTTP and ICMP tests have been unsuccessful for a period of time that exceeds 300 seconds, the uplink will be failed over. Therefore, it can take approximately five minutes for failover to occur in the event of a soft failure (where the physical link is still up but provides no internet access). MX <==> Modem <== dead link ==> Internet In this example, the modem is still powered on and the physical connection between the MX and modem is still up, however the internet connectivity tests fail and the 5 minute timer begins Hard Failover: When the actual WAN link itself goes fully down, i.e. it's unplugged or the modem/device upstream is removed/turned off. As we detect the link has physically gone down, an immediate fail-over occurs MX < ///// removed link ///////> Modem <==> Internet In this example, the modem in unplugged from WAN1 of the MX, as we detect the link is down, we do an immediate failover For more info, see: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover

ConnorL · ‎Sep 29 2023

It's just a terminal interface with the device, so the same commands you would execute on Command Prompt (Windows) or Terminal (macOS). We (Meraki & Meraki Community) cannot really help further than this, but if the program developer has provided instructions that you need to execute via CMD/Terminal, you should be able to use the Command Line tool to run there. Commands are run as root (so you shouldn't need sudo) for macOS and as Administrator for Windows.

ConnorL · ‎Sep 29 2023

If you have multiple profiles scoped to a device each contains a Restrictions payload, the more "limiting" setting will take precedence, e.g. if you allow a service/setting in Profile A, but disallow it in Profile B and both profiles are installed on the device, the disallow from Profile B will take priority. You'll need to use tags to properly scope the payload to the required devices.

ConnorL · ‎Sep 29 2023

Hey @MichaelZopes, The Command Line live tool is essentially what it says on the tin, it'll execute commands on the device that you enter. As the tool says: On Windows, commands run as Administrator in C:\WINDOWS\System32\ (in most cases) and every command is prefixed by "cmd.exe /C". In Mac OS X, commands run as root in / If you're having issues, you can use the Agent logs tool (which shows on the new version of the page) to check if the command you executed is listed there, e.g. here's the log of when I ran the ifconfig command: 2023-09-29 12:15:52.324431 [0x16ff83000]: TunClient::handle_request /run_command/1? [[ifconfig]] response: [[HTTP/1.1 200 OK Content-Type: text/plain Content-Length: 5074 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP> ...

ConnorL · ‎Sep 26 2023

Hey @Lourdes , When you use the SDB tool, it'll automatically download the file to your computer - this may take 10-60 seconds to complete depending on the state the device is in. The file is generated on-demand when you use the tool, so if you're experiencing an issue and Support asks you for an OOB/SDB (Out of band / Support Data Bundle) file, make sure you do this before rebooting the device, else a lot of the logs that are helpful to support may be lost or no longer relevant. Cheers, Connor

ConnorL · ‎Sep 26 2023

Hey @HarmonyGuru , "curl error 60" usually shows up when there's SSL inspection between the client and Dashboard, might be worth checking if your Anti-Virus/Firewall is doing any sort of inspection or filtering. If you disable your Anti-Virus/firewall temporarily, does the device contact Dashboard again? Also, if you have a case number, please drop me a DM as I'm curious to take a peek. Cheers, Connor

ConnorL · ‎Sep 26 2023

And just like that... https://meraki.cisco.com/blog/2023/09/powering-new-customer-experience-possibilities/ 👀

ConnorL · ‎Sep 26 2023

https://documentation.meraki.com/MS/MS_Overview_and_Specifications/MS130_Datasheet

About ConnorL

ConnorL

Connor Loughlin

Community Record

Badges