It would be helpful if you gave a little more context with a use case. This document might be helpful: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Blocking_and_Allowing_Clients Along with this one: https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Clients_Usage_Page_Overview#Adding_a_Client ... View more

I would do a screen share with support and show them exactly what you were clicking. However it sounds to me as you were under the network-wide>general page to schedule the upgrade and then changing to ignore. I would recommend using the organization>firmware page to manage firmware. Under the network-wide>general page when you set it to ignore this is just ignoring any future firmware releases for this network, it wont cancel any already pending firmware upgrades. It tells dashboard when firmware is released in the future I dont want you to auto schedule this network to upgrade.   https://documentation.meraki.com/General_Administration/Firmware_Upgrades/Managing_Firmware_Upgrades#Scheduling_Firmware_Upgrades ... View more

https://documentation.meraki.com/MI/MI_WAN_Health/MI_WAN_Health_Overview#Offline What do your pings to 8.8.8.8 / other configured monitoring Ip's look like? ... View more

Is there an underlying concern here? If you get a 201 back you know its successful and the account was created. ... View more

you would get a 429 response if you hit a rate limit ... View more

I would first start by following the prompt message...does the device in question have a solid internet connection? ... View more

This documentation should help: https://documentation.meraki.com/MR/Deployment_Guides/Mesh_Deployment_Guide#Point_to_multi-point_.2F_Multi-point_to_multi-point ... View more

Using the default route option in Auto VPN will send all traffic over to the hub if the source subnet/vlan is set to be included in VPN. This can be seen here: https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings#Default_Route. If the default route option is selected you can use vpn breakout which breaks out traffic from the default route auto vpn based on destination. *SD-WAN rules will not override this default route. So breaking out traffic from the default route based on source is not possible at this time, if that vlan is participating in VPN. You would first need to uncheck the default route option and then you can steer traffic based on source. ... View more

I would recommend reaching to Service Now support and Meraki support and maybe get both parties on a bridge call to troubleshoot this. From the Meraki point of view if the key is working in postman but not this application they are going to have you work with that applications support. Possibly grabbing the authorization header on the get call that service now is sending over. ... View more

I would recommend running an API call in Postman, or something similar, using the same key to that same API end point and see what response you get ... View more

Im not following the question....If WAN 1 and WAN 2 are down how would a VPN tunnel still be up? ... View more

Hello, Yes this is expected behavior. It is recommended to make changes to the Non Meraki peer settings during a change window ... View more

VRRP's will be communicated on both Vlan's. Warm spare is explained in this KB article and also gives sample topologies: https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Failure_Detection_2 ... View more

@Roey1984  The MX will auto failover to the secondary WAN link when the primary link goes down. This is explained in detail in this KB article: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover ... View more

Hello,   You can tag Non Meraki VPN configurations so only certain MX's or vMX's get the tunnel configuration: https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings#Peer_Availability In terms of the other questions I'm not really following the design, it might be beneficial to get a network diagram drawn up and make a support case and share the diagram with them and what your hoping to accomplish. ... View more

Hello, If its a managed device and you can install apps silently on it clicking the update button will tell the device to go update this app. If it is a non managed device the user would get prompted to update the app. If the app fails to update for any reason whether the device doesn't have connection to SM, the user declined the prompt, etc if it fails for any reason the update button will remain there. You can get more information around the update status on the device details page under the activity section. https://documentation.meraki.com/SM/Apps_and_Software/Updating_Managed_iOS_Apps ... View more

One thing to try is manually setting the 2.4 channel on both access points to the same either 1,6, or 11 channels. If you can bring up the repeater AP temporarily on an ethernet cable or walk it closer to the gateway AP to get a connection then make the change in dashboard to the channel and make sure it does a config fetch then go install. ... View more

If it's a WAN connection it needs to go in one of the designated WAN connections. Unfortunately, MA-SFP-TX-0003, is not a Cisco branded SFP therefor support will not be able to assist past some basic troubleshooting. You can try connecting it to WAN port on MX and connect the other side of the connection to another device like a switch and see if you get link lights or not ... View more

I'd suggest first figuring out what the devices public IP is when it hits the internet, whatmyips.com etc can help with that. Once you have that IP I would take a packet capture on the WAN interface of the MX and see if the traffic is actually reaching the MX. Here is the anyconnect troubleshooting guide: https://documentation.meraki.com/MX/Client_VPN/AnyConnect_on_the_MX_Appliance/AnyConnect_Troubleshooting_Guide Here is the l2tp troubleshooting guide: https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting Packet capture for client vpn guide: https://documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting/Troubleshooting_Client_VPN_with_Packet_Captures ... View more

Theres really not much information here to be helpful other than providing the onboarding documentation and try going through onboarding again https://documentation.meraki.com/Cloud_Monitoring_for_Catalyst/Onboarding/Cloud_Monitoring_for_Catalyst_Onboarding_Guide ... View more

Meraki only officially supports Meraki or Cisco branded SFP's. If the physical cable and speed type matches the switch you can test to see if it works but still, if you have issues or anything TAC cannot assist as they only support Cisco branded SFP's ... View more

Hello, Under Security&SD-WAN>Content Filtering you can type in the name of a URL and see what category it would fall under and configure that category as blocked. This does require an advanced security license. Otherwise you would have to manually enter FQDN's into your layer 3 rules. ... View more

You can start with running this in postman itself without the script. Run the API that changes SSID password and manually enter a value yourself and run it. You can verify if theres anything wrong on the Meraki side of things. As long as that works you can narrow it down to something in the script.  I would also say add a line to print exactly what your sending to the API and make sure that looks good too ... View more