Hi, This is strange. Could you try upgrading the firmware to Latest Stable? If already not.   ... View more

Hi, Could you try changing the list size to "Full List". ... View more

Hi, Hope you have referred the following url. https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair   Excerpts from the above url. Underlying Concepts and Technologies VRRP Heartbeats Failure detection for an MX Warm Spare pair uses VRRP heartbeat packets. These heartbeat packets are sent from the Primary MX to the Secondary MX on all configured VLANs in order to indicate that the Primary is online and functioning properly. As long as the Secondary is receiving these heartbeat packets, it functions in the spare state. If the Secondary stops receiving these heartbeat packets, it will assume that the Primary is offline and will transition into the master state. When the MX is in NAT mode, VRRP heartbeats are not sent over the WAN; there is no guarantee that the WAN interfaces can communicate with each other. Instead, we use a mechanism called "connection monitor" to determine the WAN state of the device. For more in-depth information regarding the VRRP Mechanics on the MX, please see the NAT HA Failover Behavior   documentation. Connection Monitor Connection monitor is an uplink monitoring engine built into every MX Security Appliance. The mechanics of the engine are described in   this article. When all uplinks of a Primary MX are marked as failed by connection monitor, that MX will stop sending VRRP heartbeat packets, which will initiate a Warm Spare failover. Once at least one uplink on the Primary returns to a working state, the Primary resumes sending heartbeat packets and the Secondary relinquishes the Active role back to the Primary. ... View more

Hi, Following is my understanding. I believe MS350 supports only "Physical Stacking". This means we need to use the Stacking Ports at the Back of the Switches. To Use these Port we need to buy "Stacking Cables".   Kindly check the below url displaying the compatible accessories. https://meraki.cisco.com/products/switches/accessories   The Twinax cable can only be used in SFP+ ports to interconnect switches as "Uplinks" and also for  "Flexible Stacking".   You may refer to the following page (If you have not). This has answers to most of your questions. https://documentation.meraki.com/MS/Stacking/Switch_Stacks   ... View more

Hi, The Group Policy in Meraki can be applied at various Levels ie. MAC, IP, VLAN, AD Groups. Please check the following Url for the "order of priority" of the policies if applied at Multiple Levels.   https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Troubleshooting_Group_Policies#What_is_the_order_of_priority_for_Group_Policies.3F   Also make sure to select "Full List" under Security & SD WAN -> Content Filtering -> URL category list size.   ... View more

Hi, I understand MX do not offer DNS Services Adding MX Local IP in  DHCP NS List shall not be of any help. Hope your AD DNS server is working good to resolve domains.    You may follow @PhilipDAth instructions on this.   Also consider  verifying L3  L7 Content Filtering Traffic Shaping rules and Firmware version. ... View more

Hi, I have not faced  "Whitelisting Policy" not working with Meraki Wireless. I did faced Group Policy issues in Meraki Wireless + Appliance network which was shorted out later.   I never got an opportunity to Manage 1000+ WiFi user base though. If not ISE / MS you may consider FreeRadius / MikroTik.   You may start with http://www.freeradius.net/. Install it on a Windows Machine and check if a Radius solves the issue. However Lets wait for some more suggestion from Community Members.     ... View more

Hi, For a basic level of "users on boarding process" Meraki Radius seems to be fine. Any how you need to manually type in the MAC Address in either of the solutions.   In-case of Meraki you can specify the desired policy on the device while adding them on to the Dashboard. Screenshot attached for reference.     For a better functionality you may consider Cisco ISE. ... View more

Hi, I understand authentication in MXes works in a different way as they are Gateway devices. You may apply this on VLANs not on SSIDs.   Screenshot attached for reference.   Note : I have never tried configuring Facebook Login with MXes. ... View more

Hi, I have not seen this error. Seems there is an issue while querying LDAP. Could you try changing the username? Also try connecting with UPN Format ie. UserNam @ Example.Microsoft .com. ... View more

Hi Marc Thought for some time but couldn't get any ideas. I am not aware of any option to deactivate network. I believe you may have to leave it as it is. May be you can rename the network with a meaningful text like "Under Maintenance" or something better.  ... View more

Hi Rajinder This is not a good sign.  Few quick questions 1 Is the device live on the dashboard? 2 What firmware version do we have? 3 On which interfere have you connected the point to point link?    ... View more

Hi Stu, To upgrade the Firmware one should have "Organization Wide" admin Rights.   You will see "Firmware Upgrades" option under "Organization".   Screenshot attached for reference.     ... View more

Hi Are you sure? They should be in the same range but need to be different. Is your VPN working meaning are you able access resources from your office network? ... View more

Hi,   This is what I understand.   You are trying to connect to MX84 as client VPN from  remote location. The Client VPN connection is successful. However when you do a "ipconfig" on your pc. The IP Address and Gateway IP Address is same?   Is my understanding correct? ... View more

Hi,   I am not sure as have not tested but considering the MX routing behaviour I believe NAT/PAT shall be over-ridden by the VPN Default route.   https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior Route Priority Each type of route configured on the MX has a specific priority in comparison with other types of routes. The priority is as follows: Directly Connected Client VPN Static Routes AutoVPN Routes Non-Meraki VPN Peers NAT* However may be we shall wait for inputs from other community members. ... View more

Hi Paul,   I understand this shall not be a challenge.   Kindly check the following Url. https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Settings#Non-Meraki_VPN_peers   Following section is an excerpt from the above Url Non-Meraki VPN peers You can create Site-to-site VPN tunnels between the MX appliance and a Non-Meraki VPN endpoint device under the   Non-Meraki VPN peers   section on the Security & SD-WAN > Configure > Site-to-site VPN   page. Simply click "Add a peer" and enter the following information: A name for the remote device or VPN tunnel. The public IP address of the remote device. The subnets behind the third-party device that you wish to connect to over the VPN. 0.0.0.0/0 can also be specified to define a default route to this peer. The IPsec policy to use. The preshared secret key (PSK). Availability settings to determine which appliances in your Dashboard Organization will connect to the peer. Note that if an MX is configured with a default route (0.0.0.0/0) to a Non-Meraki VPN peer, traffic will not fail over to the WAN, even if the connection goes down. ... View more