Hi @Diego_Alcoceba, great to see you here!  ... View more

Hi @FredBeauchamp,   Do you mind confirming if your Service Now App has been created following the below developer guide? https://developer.cisco.com/meraki/build/servicenow/ Note we also have a troubleshooting section as well located below: https://developer.cisco.com/meraki/build/servicenow/support/   Also wanting to confirm your Service Graph Connector for Meraki is current - can be located below: https://store.servicenow.com/sn_appstore_store.do#!/store/application/dc27a74a80421010f8772cdfe9d5f855    Lastly, important to note that ServiceNow uses model name and manufacturer to determine if a new model record should be created, and Meraki defaults the manufacturer to "Meraki". This can lead to duplicates if there is an existing model with a differing manufacturer.    If all looks well on these above notes, please reach out via our below Support process and we'll be happy to investigate further!   https://documentation.meraki.com/General_Administration/Support/Ways_to_Contact_Meraki_Support Important information to include in the Support ticket include but are not limited to: Service Graph Connector for Meraki App Version ServiceNow application version, found by navigating to System Diagnostics > Stats > Stats Error logs after reproducing the issue (found by navigating to Debugging > Error Logs) Relevant screenshots of the configuration and errors   Thanks!  ... View more

Hi @cmr interesting results, I definitely thing this warrants a support case if you haven't already - if nothing else for added clarification on the results by an engineer that can do some deeper dive on the live data.  ... View more

Welcome back @Joel07 . ... View more

Thanks peeps, I'll give the docos some more reading and see if I can figure it out. ... View more

Ah that was the issue, to print out the QR code it needs to be about 75% a full sheet of paper for the phone to read it. Even on a screen it needs to be pretty large.  ... View more

Hi All,   I can confirm this is on our radar after doing research internally, but as always submitting feedback as @GNygren mentioned helps prioritize these types of requests in our product/development teams visibility for prioritization! Outlined below for those who are unfamiliar with the process: Although this feature is not available, we take our customer feedback seriously. We encourage you to use the Meraki dashboard to "Give your feedback" and submit a feature request. You can submit a feature request at the bottom of any dashboard page. Any wish that is made sends an email to our Product Managers and Development Teams. These wishes are taken into consideration and are used to help shape our product roadmaps. The most wished-for items are incorporated into product development. Fun fact, nearly 90% of Dashboard features have come from customer feedback requests!   https://documentation.meraki.com/General_Administration/Other_Topics/Give_your_feedback_(previously_Make_a_Wish) ... View more

Hi @Fabrizio,   Thanks for the community post :).   I tend to agree with @alemabrahao, given the inconsistent nature this likely seems best troubleshot over a live call/case review - process outlined below for contacting support: https://documentation.meraki.com/General_Administration/Support/Contacting_Support   That being said, without reviewing the existing blocked URLs list I just wanted to call out the 'logic' behind the URL filtering for reference: Whenever a client fetches a web page on this network, the requested URL is checked against the lists configured below to determine if the request will be allowed or blocked.   Pattern matching follows these steps: Check if the full requested URL is on either list. example: https://web.whatsapp.com/  Cut off the protocol and leading "www" from the URL, and check if that is on either list: web.whatsapp.com Cut off any "GET parameters" (everything following a question mark) and check that: foo.bar.com/qux/baz/lol (not relevant to your displayed configuration)  Cut off paths one by one, and check each:foo.bar.com/qux/baz, thenfoo.bar.com/qux, thenfoo.bar.com Cut off subdomains one by one and check those:bar.com, and then com Finally, check for the special catch-all wildcard,*, in either list.   If any of the above produces a match, then the request will be allowed through if it is in the allow list and blocked otherwise. (That is, the allow list takes precedence over the block list.)   If there is no match, the request is allowed, subject to the category filtering settings above. HTTPS requests can also be blocked. Because the URL in an HTTPS request is encrypted, only the domain checks will be performed (www.foo.bar.com,foo.bar.com,bar.com,com, and the special catch-all *).     In short, the preferred method of allowing all of the 'whatsapp.com' would be simply whatsapp.com and without an asterisk (this would include HTTP & HTTPS requests.) This assumes no URL redirects are causing issues in a secondary domain.     For added context please see below: https://documentation.meraki.com/MX/Content_Filtering_and_Threat_Protection/Content_Filtering#Using_the_Catch-All_Wildcard_(*)_in_URLs   Thanks and hope this helps! ... View more

Hello everyone,     The issue was solved. As @BrandonD mentioned, clients will not be visible on trunk ports. The issue with customers connected to access ports not appearing in Monitor -> Clients was caused by the CS 17.2.1 firmware. After upgrading to CS 17.2.1.1, this issue was resolved.   Thank you for your support! ... View more

We ran into same issue, same error in MX events. We have a very large Xerox press that scan to email suddenly stopped working. I added our printer as a trusted IP and allowed rule in IDP. Scan to email now works. Will continue to monitor, but it does seem like a false positive in Talos.  ... View more

In an education environment I would strongly suggest using 802.1x; are the devices school supplied or BYOD? ... View more

Hi @CN_again,   Apologies for the delay here, but I have made the proper adjustments to the 802.1X references below per your recommendation:   https://documentation.meraki.com/Access_Manager/Access_Manager_Configuration_Guides/Access_Manager_non-802.1X_Supported_IoT_or_Other_Endpoints_-_MAC_Authentication_Bypass_(MAB)_and_iPSK   Thanks for bringing this to our attention :).  ... View more

  Hi @Default118,   Happy to confirm the following API endpoints can be utilized for utilization and CPU/Memory values:   MX Appliance Utilizations: https://developer.cisco.com/meraki/api-v1/get-organization-summary-top-appliances-by-utilization/ Added context:  https://documentation.meraki.com/MX/Monitoring_and_Reporting/Device_Utilization#Reading_Device_Utilization_via_API Memory Utilization (MR/MS/MX): https://developer.cisco.com/meraki/a...y-by-interval CPU Utilization (MS): https://developer.cisco.com/meraki/a...h-by-interval/ CPU Load History (MR): https://developer.cisco.com/meraki/api-v1/get-organization-wireless-devices-system-cpu-load-history/    Hope this helps 🙂 ... View more

UPDATE: This contest has now closed. Thank you to everyone who submitted their networking memes. We got a good laugh out of reading them! Congrats to our 3 randomly selected winners: @Kamaboko, @AVL, and @vagrant 🎉 ... View more

Hi @NH_DP,   One way around this if the device is currently on and responding to pings on the local LAN would be to temporarily enable the Network-wide > General > 'Remote device status pages (through device's LAN IP)'  setting which will allow you to access the management IP of the AP via http://192.168.1.1 (as an example.) More on this topic below:   https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page#Controlling_Remote_Access_to_the_Local_Status_Page  ... View more

Welcome to the Meraki Community!  In addition to the multiple resources other members have posted, I wanted to also pass along our 'quick start' for MX and our Meraki YouTube pages which are both additional resources!   https://community.meraki.com/t5/Security-SD-WAN/New-to-the-MX-Start-here/m-p/98941#M24787 https://www.youtube.com/@MerakiMinute  ... View more

Thank you Brandon! Ultimately, what was found to be the cause of the issue? ... View more

How long ago did you try the AppleTV? It used to have a long delay but recent updates have brought that down to circa 3-4 seconds, so may be worth revisiting if that is acceptable? ... View more

 @AhamBramhasmi rising star 👏 ... View more

On the clients details page, you can check who authorized it.   https://documentation.meraki.com/MR/Encryption_and_Authentication/Sponsored_Guest#Connecting_to_the_SSID ... View more

Thank you so much. ... View more

Hi @BlakeRichardson,   Thanks for the feedback, I am going to post feedback on this document and see if we can get it updated shortly. Good catch and thanks for your patience on the feedback! EDIT: I have updated the following documentation to reflect the post, thanks again! https://documentation.meraki.com/General_Administration/Licensing/Meraki_Licensing_FAQs ... View more