No problem @Uberseehandel, glad that we could be of assistance. As @PhilipDAth has stated above, if you believe keeping VLAN 1 as the default Native VLAN as being insecure/vulnerable, change it to another unused VLAN number in your design, just ensure that you change the Native VLAN on all other links to reflect it. ... View more

Double tagging is the issue here. As @PhilipDAth has stated, the Native VLAN is 11 and the AP is using VLAN 11 for it's DHCP requests when the Native VLAN is already VLAN 11.   As @PhilipDAth has mentioned, change the Native VLAN back to 1 and this will resolve the issue.  ... View more

Hey @Nick_Barron, some great feature requests ideas there.I too also would love the ability for the MV cameras to send push alerts when motion is detected within a certain area.    My recommendation would be to "Make a wish" Within dashboard for these features and also reach out to your local Meraki sales Rep if these features requirement are pending a sales deal.   In regards to the Camera wall on IPAD, have you tried just using the native google chrome browser and logging into dashboard this way to see the camera wall?   ... View more

Can this not be achieved by using Group Policies within dashboard with traffic shaping rules, using custom expressions and assigning these directly to the clients.    For this to work though, the clients would have to be connected via an MR access point if not transversing via an MX.   Have a read of this document which outlines group policies and the requirements in more detail -  https://documentation.meraki.com/MX-Z/Group_Policies_and_Blacklisting/Creating_and_Applying_Group_Policies ... View more

My assumptions are that the error message is for the AP not the phone. How's the AP configured, is it configured to receive an IP address via DHCP? Make sure there is no VLAN tagging set on the AP's DHCP configuration as I assume it's already being tagged at the Switch port? (Double tagging could cause this error message) ... View more

The .pem file relays to a certificate which allows the Apple Push notification server to communicate with SM. The certificate is then installed silently on enrolled SM devices to allow for management. Without it, SM cannot communicate with Apple devices.   Apple imposes the 365-day renewal, not Meraki.   Have a read of this article which describes the Apple Push Certificate requirement and steps in more detail - https://documentation.meraki.com/SM/Device_Enrollment/Apple_MDM_Push_Certificate   ... View more

@PhilipDAth Keep us updated 🙂 ... View more

That is rather strange, was aggregation created before physical connection? The only thing that springs to mind would be to check the local status page of that Switch.   I assume the speed negotiation should be shown and ports in use. I wonder if this has anything to do with the bring up of the aggregation. ... View more

Have a look at this video. After aggregating the ports together, click on details of the aggregated link. Once in the aggregated link page you'll be able to see the ports in the aggregated group and the ones which are up and in use. - https://www.youtube.com/watch?time_continue=31&v=ddaY1p1VcNE   In regards to email alerts, I don't think there's the ability to specifically set alerts on aggregated ports. However, if you set standard switch port email alerts, this would apply to the aggregated ports. ... View more

If you're still having issues with the account, just delete it and re-create. ... View more

The only way I can see this currently possible would be to take advantage of the Alerting within Dashboard. That's if you're not going to proactively monitor the state via SNMP.   Using the alerts, The primary uplink status changes and Cellular connection state change alerts can be fed into your ticketing tool. Assuming that two alerts would be generated, one for when failover occurs and one when service is restored this would indicate a normal restoration. Any Ticket which only has the one alert generated after 60 minutes of creation would indicate the device is still operating on the Cellular interface.   My recommendation if this is still too ADHOC would be to "make a wish" requesting for time thresholds for the primary up-link and cellular connection state alerts. ... View more

Thanks, @CarolineS for the shout out and all the things that you do on the back end. It's great to be apart of a new thriving community which will only get bigger in 2018 🙂 ... View more

Have you looked at 802.1x? In your example, you could look at doing MAB (MAC authentication bypass) - https://documentation.meraki.com/MS/Access_Control/MS_Switch_Access_Policies_(802.1X) ... View more

I assume you're using LDAP for authentication, not Radius? I know with Radius that the splash page frequency is governed by session-timeout attribute (https://documentation.meraki.com/MR/Splash_Page/Splash_page_frequency) with LDAP, however, I am not 100% sure.   My guess is that it would be governed by the splash page frequency attribute within the Wireless>Splash page. The reason that you had some clients present the splash page after changing this attribute was that they still had the old lease time configured. Therefore now after forcing a re-authentication of the client, they have the new attribute time. ... View more

Hey @Steph, I'm not 100% sure on what you're asking from your question. Are you asking if Meraki plan to allow for other vendor cameras to be integrated into the Meraki cloud controller/storage platform?   If this is correct, I don't think Meraki have this on the roadmap and don't intend on offering the ability for other vendors to tap into their controller/storage platform. ... View more

Unfortunately, you're correct. RRM requires Cloud (Internet) connectivity. However, Meraki (MX) devices do offer quite a few options for internet connectivity to allow for extra Internet redundancy in case of a single ISP failure.   ... View more

Makes sense, that was my assumptions. Did you have any physical devices or other Meraki licenses in the organization? You definitely shouldn't have been able to delete the org without un-claiming the devices first. ... View more

@jared_f Keep us posted on what support say. I'd be really interested to what they come back with. ... View more

System Manager licenses RRP is around $40 USD per year. A great and highly recommended addition if you already have a Meraki network. ... View more

+1 for Ekahau.  ... View more

Check out this article for OSX Split tunnel configuration - https://documentation.meraki.com/MX-Z/Client_VPN/Configuring_Split-tunnel_Client_VPN   ... View more

Hey @MerakiMoll, I'd recommend reaching out to your Microsoft sales rep who will be able to advise you on the best architecture steps to overcome this. IMO worst comes to worst, you could just have these in different accounts with a VPN peering between the two VNETS/Accounts.     ... View more

Isn't this the whole point of 802.1x? I.e If a client doesn't authenticate it doesn't get an IP/Connection? Therefore devices which can't authenticate via a wired connection regardless if it's a printer/laptop/pc won't get internet connection   Have a read of this knowledge base article, it also gives you examples of how to configure - https://documentation.meraki.com/MX-Z/Access_Control_and_Splash_Page/MX_Access_Policies_(802.1X)  ... View more