Hi,   You probably need to check the attribute pairs that you are sending for the  CoA Request if it correct and supported by the MR. Here's the link to Meraki KB for more info.   https://documentation.meraki.com/MR/Encryption_and_Authentication/Change_of_Authorization_with_RADIUS_(CoA)_on_MR_Access_Points   Thanks, ... View more

Hi, Are you only having the issue when using that Mac device? Also, have you tried connecting from different sources? The client VPN uses IPsec protocol so UDP ports 500 and 4500 are used and should NOT involve other ports. You can also take a packet capture on The MX's Internet interface during the failure so you can see what is going on with the UDP traffic. Thanks, ... View more

Hi, The failure indicates that the client did not get DNS query replies. Please check and make sure the DNS server that you have configured for the clients is working or is reachable. You may try to use the same DNS server that your AP is using. Thanks, ... View more

Hi,   Check your configuration and ensure the SSID is tagged properly with the correct VLAN ID. From the AP, check and ensure the VLAN ID is allowed on your switches trunk ports all the way to the MX. Lastly from the MX's Addressing and VLANs' page, verify that the VLAN is allowed on those ports.  For the Radius authentication failures, verify from the server logs what is the error. You may also take packet captures on the wired interface of the AP while a client is connecting so you can see the packet exchanges between the AP and RADIUS server. It should tell you whether the RADIUS is sending access-reject or if the AP is not sending the access-request at all.   hope this helps. ... View more

Hi,   Try disabling your Windows firewall and see if that works. Also, check if you have any layer 3 firewall rules configured on the Wireless > Firewall and traffic shaping page.   Thanks,  ... View more

Hi, I checked the Meraki API doc on my Dashboard (help > API docs), there is no API call that can get the mesh routes so this is not supported at the moment. The API docs get updated whenever there is a new feature added so I would recommend checking it from time to time. Also, the Dashboard has a "Make a wish" button on the lower right corner of your screen which you can use to submit this as a feature request.    https://documentation.meraki.com/zGeneral_Administration/Other_Topics/Make_a_Wish   ... View more

from the client, can you ping the AP? and from the AP, can you ping the switch?  Also, kindly ensure client isolation is not enabled.   https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Wireless_Client_Isolation   If this is still not working, I would suggest looking at the packet capture on the wired interface of the MR84 while pinging to see whether the AP is actually forwarding the ICMP packets.     ... View more

@Nash  I tested on n80 and n189, both works. I just use Postman for testing. ... View more

  It is not firmware dependent. I have tested both APIs, switchPortStatuses and switchPortStatuses/packets, and I can confirm that they are working.     ... View more

Hi, Change the data encryption to use "Require encryption (disconnect if the server declines)" on the security tab of the VPN connection properties. https://documentation.meraki.com/MX/Client_VPN/Client_VPN_OS_Configuration#Windows_10 If you are still having an issue, I would recommend taking packet capture on the WAN interface of the MX to verify if your traffic is actually coming through. hope this helps! ... View more

Hi,   I would recommend checking the certificate if it is still valid and if it is installed on the Windows 10 device. If you still have an issue, then probably call the Meraki support if there is any known issue with Windows 10 connecting to SSID using sentry.   Thanks,   ... View more

Hi,   Even if you have 20Mbps per client + SpeedBurst setting, it should not cause to limit the clients' throughput to only 1 Mbps. You can check the changelogs if there any other settings have been changed. ie. on the traffic shaping page, the client tracking option on the MX, and on the port settings of the switch connecting to the MX.  If you face the issue again or if you are want to test it (putting the 20Mbps per client + SpeedBurst back), I recommend calling the Meraki support to help you with the checking as this is definitely not expected behavior.   thanks,       ... View more

Hi,   There is a hold off timer of about 25 minutes before the switches reboot when you perform an upgrade to ensure all the switches in the network have finished downloading the firmware. The reboot after 1 minute of the schedule is not an expected behavior but I would recommend calling the Meraki support to figure out why.   Thanks,     ... View more

Hi,   It could be an issue if there is a native VLAN mismatch on the trunk ports or if the VLAN is pruned. Just ensure the trunk port configuration is the same on both ends.    Thanks,     ... View more

Hi,   Is it only for this AP? Have you tested in other MR45s if you have any? If it consistent and was working prior to the firmware upgrade, then I would recommend calling the Meraki support as the behavior is not expected. You may be hitting a bug.    Thanks,       ... View more

Hi,   The Dashboard network-wide > clients page doesn't have a column or option to show the band on which the client is connected. The closest to it I would say is the channel width, any clients not connecting at 20 Mhz would be at 5Ghz.  But then depending on your radio settings, clients at 20 Mhz can still be using the 5ghz channel. Hope this helps.   ... View more

Hi,   I get a response while testing this from Postman so I can confirm your API key is correct. As mentioned, please ensure your parameter is correct. Here is the response I get.           "id": "915420",         "name": "WiteSand",         "url": "https://n66.meraki.com/o/EqEjNc/manage/organization/overview"   Please refrain from sharing your API key as it is used for authenticating your org. since it has been shared already., kindly generate a new one.   https://documentation.meraki.com/zGeneral_Administration/Other_Topics/The_Cisco_Meraki_Dashboard_API   Thanks, Denis  ... View more

Hi,   If you are using a combined network then the IP address tracking is not available. You can uncombine the network to get that option.  It is recommended to use IP address tracking if your clients are behind a layer 3 device. If you can see details from other clients on the Network maybe its gateway IP is the MX. The cloud track is recommended if your downstream layer 3 switch is also a Meraki. However, any change in the tracking option will reset your historical client usage statistics and there is no way to get around it for now.   Thanks,             ... View more

Hi,   This option is not available. The wireless capability of the Z3 or MX is limited compared with the Meraki APs where you can set SSID availability such that the AP will broadcast the SSID based on a schedule.   hope this helps. ... View more

Hi,   Based on your route table, if the destination IP matches the 192.168.X.0/24 network then the traffic should be routed to ASA. However, if it does not match and falls under the default route 0.0.0.0/0 then it will go to the Palo Alto because it has a higher priority than the default route over the WAN connection.   If you suspect that the traffic is not routing over the IPsec even if it matches the 192.168.X.0/24 destination subnet, then you may need to call Meraki support so they can check whether this is the case or not.   Hope this helps.        ... View more